Seven EVM chains · 28 queued Safe proposals
Review and confirm the production upgrade
Only the server-released phase can be confirmed. Signing does not execute a transaction or interrupt service.
Phase 0 creates the on-chain V1 send cutoff
Phase 0 is released
Bridge maintenance only
Maintenance runbook
The console accepts one advance confirmation for each future transaction. It withholds the final confirmation until phase release is independently verified.
Prepared transactions
Phase 0: block new V1 sends while preserving V1 inbound delivery.
Phase A: upgrade and initialize Endpoint V2 with every peer still closed.
Phase B: pin MessageLibs, executor, 4-of-4 DVNs, and receive gas.
Phase C: set six peers and open V2 pathways only after verification.
Phase 0 abort and V1 send restore
These seven proposals deliberately use the Phase A nonce. Review them before the window, but sign them only if the migration is formally aborted after Phase 0 and before Phase A.