If you are ready to execute deployment, use Deploy Assertions with the Platform. If you need background on how the system works, start with the Architecture Overview.
Adoption Workflow
Teams follow the same underlying steps. The CLI is used to author and store assertions, while the platform is used to manage deployments and monitoring.- CLI authoring: write assertions locally and store bytecode
- Platform management: link contracts, stage or deploy, and monitor incidents
End-to-End Flow
What You Control
- Which assertions protect which contracts
- Staging vs production deployments
- Incident notification routing and monitoring
Deployment Modes
- Staging: test and iterate on assertions without impacting production users
- Production: enforce assertions at the network level for real transactions
What Users Can Verify
- Which assertions are active for a protocol
- On-chain registry entries and transparency views
- Incident history for protected contracts
What Successful Rollout Looks Like
- Assertions cover critical protocol invariants and admin operations
- Staging assertions are validated before moving to production
- Teams review incidents and iterate on coverage over time
Next Steps
Deploy Assertions
Step-by-step deployment guide
Assertions Overview
Learn how assertions work and how to write them
Platform Overview
Understand how the platform is used by teams and users