EVM bridge activation 3/7 (sovr-1): merkle tree hook, usovr collateral token
Sovren proposal #20: Third of seven governance proposals that activate the SOVR to Base bridge. It creates two instances on the stage 2 mailbox, both owned b...
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.
Original Proposal Text
Third of seven governance proposals that activate the SOVR to Base bridge. It creates two instances on the stage 2 mailbox, both owned by the governance authority, and cannot move value. (1) The merkle tree hook. Outbound messages are added to this tree and the verifiers sign its checkpoints; stage 4 makes it the mailbox required hook. (2) The collateral token for usovr, the canonical bridge token: bridging out will lock usovr in the warp escrow and bridging back will release it. It is created with no ISM of its own, so until stage 4 it is verified by the mailbox default ISM, which rejects every message. It has no enrolled remote router and no bridge route exists, so nothing can be sent or released through it. Both messages need only the mailbox id that stage 2 created, so they share one proposal. The renderer filled that id from chain state, selecting the mailbox by its owner and domain and never by a predicted id. The metadata document gives the checks to run before voting and after execution. Stage 4 needs the ids this stage creates and is submitted only after this one executes. More details: https://gist.githubusercontent.com/sovr-team/71fdca6e629cab5c9532bbd1ca7eb42a/raw/2dd85ab426a82d0045276e46b7c05b5cc777f42c/bridge-activation.mainnet.metadata.md