EVM bridge activation 1/7 (sovr-1): deny-all routing ISM, 4-of-6 verifier multisig ISM, noop hook
Sovren proposal #18: First of seven governance proposals that activate the SOVR to Base bridge. It creates three Hyperlane instances owned by the governance...
Yes
100%
No
0%
Abstain
0%
Veto
0%
If passed
Some execution details could not be interpreted. Review the source JSON before voting.
1. Uninterpreted operation
This message type is not supported by the interpreter. Its effects are unknown.
2. Uninterpreted operation
This message type is not supported by the interpreter. Its effects are unknown.
3. Uninterpreted operation
This message type is not supported by the interpreter. Its effects are unknown.
Original Proposal Text
First of seven governance proposals that activate the SOVR to Base bridge. It creates three Hyperlane instances owned by the governance authority. None of them can move value: no mailbox, token, router enrollment or bridge route exists until later proposals. (1) An empty RoutingISM. Every verification against it fails with no-route-found; it becomes the mailbox default ISM in stage 2, so any path that is not explicitly configured denies. (2) A MessageIdMultisigISM over 6 verifier addresses with threshold 4. These are the Base-origin signing keys of the launch verifier set; once the x/evmbridge policy ISM wraps this instance in stage 2 it is what verifies Base to SOVR messages. Every seat is operated by Sovren and Parler staff at launch, each pair of keys generated on its own seat host; the metadata document lists the addresses and states this and the other launch disclosures. The instance is immutable: changing a verifier means a new instance and one to three further proposals, depending on how many later stages have run. (3) A noop post-dispatch hook, the mailbox default hook from stage 4; there is no interchain gas paymaster at launch. These three messages have no inputs that depend on an earlier instance, so they share one proposal. Stage 2 needs the ids this stage creates and is submitted only after this one executes. The metadata document gives the checks to run before voting and after execution. More details: https://gist.githubusercontent.com/sovr-team/71fdca6e629cab5c9532bbd1ca7eb42a/raw/8ae6808442e8876e33409442f135b09600058629/bridge-activation.mainnet.metadata.md