What We Guarantee
- Deterministic enforcement: given the same on-chain state and assertion code, enforcement results are deterministic
- Pre-execution protection: transactions that violate deployed assertions are excluded from blocks by networks running the enforcer
- Transparent rules: assertions are public Solidity code and can be audited by anyone
What We Do Not Guarantee
- Assertion correctness: teams are responsible for writing accurate assertions
- Complete coverage: only behaviors covered by assertions are enforced
- Off-chain security: custodial, UI, or off-chain service risks are out of scope
Operational Assumptions
- The network runs the Assertion Enforcer during block building
- The enforcer can access registry data (from on-chain events) and assertion bytecode
- The network follows its normal transaction validity rules alongside enforcement
Failure Modes (High Level)
- Enforcer unavailable: the network continues normal operation without enforcement until the enforcer is restored
- Registry misconfiguration: assertions may not apply to intended contracts
- DA connectivity issues: new assertions may be delayed until bytecode is reachable
Next Steps
Architecture Overview
Understand the system components and flows
Assertion Enforcer
Enforcement details and validation process
FAQ
Common questions about the Credible Layer