VKey hash provenance
Locked
This runbook is retired.
It described the boot-time provenance gate for the bridge SP1 verifying-key hash (sp1_helios_vkey_hash), which the chain enforced when the sp1-bridge-verifier feature was built into a release. The in-tree bridge stack has been removed: there is no bridge precompile, no bridge zk light-client, and no sp1-bridge-verifier build feature, so the sp1_helios_vkey_hash boot gate no longer exists. Cross-chain interop is now an external provider integration, not an on-chain module with a pinned circuit.
There is nothing operator-facing to configure here today. A vkey-hash provenance procedure for any future zkML/agent verifier surface will be documented if and when that verifier approaches activation.
Cross-links
Section titled “Cross-links”- Bridges and interop — the external-provider interop model
- Native module catalog — activation-gated module posture
- P2P handshake / chain bind — chain-bind provenance for operator keys