Protocol Maturity
protocol-maturity.md
Boundary
This route preserves legacy markdown access inside the Next.js surface. The raw repository file remains authoritative.
Open raw fileProtocol Maturity
| Layer | Status | Notes | | --- | --- | --- | | Lifecycle Safety | Hardened | Commit, reveal, finalize, execute gating is documented and test-backed. | | Replay Safety | Hardened | Duplicate commit/reveal/finalize/execute reasoning and coverage exist. | | Treasury Safety | Hardened | SOL and token execution paths have miswiring rejection coverage. | | Delegation Safety | Hardened | Self-delegation, non-delegatee misuse, and cross-proposal misuse are covered. | | Timing Safety | Hardened | Boundary-condition coverage exists for commit, reveal, finalize, and execute. | | Account Binding | Hardened | DAO, proposal, voter record, delegation, and treasury bindings are documented and tested. | | Atomicity | Hardened | Failed finalize and execute paths are documented as preserving critical state. | | Formal Specification | Present | Protocol behavior is now described in `docs/protocol-spec.md`. | | Threat Model | Present | Formal threat framing exists in `docs/threat-model.md`. | | Replay Analysis | Present | Deterministic replay reasoning exists in `docs/replay-analysis.md`. | | Failure Simulation | Present | Misuse scenarios are documented in `docs/failure-modes.md`. | | Independent Verification | Present | External verifier path exists in `docs/independent-verification.md`. | | Attack Simulation Index | Present | Quick misuse log exists in `docs/attack-simulation-log.md`. | | Mainnet Readiness Gate | Present | Operational readiness gate exists, but not a mainnet audit claim. | | Android Runtime Verification | Partial | Native app exists, but runtime verification requires Android SDK/device environment. | | External Audit | Pending | No external audit is claimed by the repository. |