Security Model
ComputeNet operates under specific security assumptions. Understanding these assumptions and potential threats is essential for building secure applications.
Trust Assumptions
- Cryptographic primitives are secure (hash functions, signatures)
- At least 2/3 of validators are honest
- Network eventually delivers messages
- Proof systems are sound and complete
Threat Categories
Validator Collusion
If more than 1/3 of validators collude, they could produce invalid receipts. Mitigated by economic incentives and slashing.
Denial of Service
Attackers may attempt to overwhelm the network. Mitigated by rate limiting and resource pricing.
Data Availability Attacks
Withholding receipt data could prevent verification. Mitigated by data availability sampling.