This page summarizes the Credible Layer trust model in plain language.Documentation Index
Fetch the complete documentation index at: https://docs.phylax.systems/llms.txt
Use this file to discover all available pages before exploring further.
Core Guarantees
- 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
Scope of Guarantees
- Assertion-defined coverage: enforcement applies to the behaviors captured by active assertions
- Protocol-authored rules: protocol teams define and maintain the rules that protect their contracts
- Integrated environments: enforcement applies on networks and environments where the enforcer is integrated and the assertion is active
- On-chain coordination: the State Oracle contracts remain the source of truth for assertion lifecycle state and timelocks
Operational Model
- 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
- Production assertions are admitted with bounded triggers and resource limits before they become part of the active execution set
- Network integrations define continuity behavior for maintenance windows and degraded components
Assurance Practices
Teams build confidence by validating assertions locally, backtesting against historical transactions, running assertions in staging, and promoting to production only after sufficient review. See How to Plan Assertion Testing for the recommended workflow.Next Steps
Architecture Overview
Understand the system components and flows
Assertion Enforcer
Enforcement details and validation process
FAQ
Common questions about the Credible Layer