If you need concrete implementation details, continue to the Linea / Besu integration or OP Stack implementation. If you need background first, read the Architecture Overview.
Who This Is For
- L2 networks and sequencers evaluating integration
- Infrastructure teams operating block builders or validators
- Security teams defining network-level enforcement goals
High-Level Flow
Integration Surfaces
Networks provide the following integration surfaces:- Block-building hook: the block builder queries the Assertion Enforcer before including a transaction
- Registry access: the enforcer consumes registry data (indexed from on-chain events) to discover which assertions apply
- Assertion data access: the enforcer fetches assertion bytecode from Assertion DA
- Operational monitoring: incidents and status are surfaced via the Phylax platform
Operational Expectations
- The enforcer runs alongside the block builder and does not change consensus rules
- Enforcement is deterministic and only depends on on-chain state and assertion code
- Protocol teams choose whether assertions are staged or enforced; networks honor the registry status during validation
Integration Checklist (High Level)
- Identify the block-building hook for transaction validation
- Configure access to registry data and assertion bytecode
- Ensure the enforcer respects staged vs enforced assertions as set by protocol teams
- Set up monitoring and incident review workflows
Integration Requirements (Public)
- Block-building hook that can query the enforcer before inclusion
- Registry access for assertion discovery (on-chain events indexed locally)
- DA access for assertion bytecode retrieval
- Incident visibility through the Phylax platform
Next Steps
Architecture Overview
Detailed system architecture and transaction flow
Linea / Besu Integration
Plugin-based integration pattern for Besu
Assertion Enforcer
Sidecar validation flow and enforcement role
OP Stack Implementation
OP Stack integration notes