Execution
Cross-chain governance execution
Protocols deploy everywhere, but governance usually lives on one chain. The vote must travel to where the contracts are.
The message-passing model
A vote on the home chain authorises a message; a bridge or messaging layer relays it; a remote executor applies it to the local deployment.
Failure modes to design for
Messages that land out of order, relays that stall mid-flight, and remote executors whose permissions drift from the home governor.
Confirm on every chain
Execution is only complete when each target chain reports a hash. Partial rollouts leave the protocol in two different states at once.
One decision, several destinations
A protocol deployed on five chains still wants one answer to a question. The vote usually happens on a home chain, and the result then has to be carried to each deployment as a separate transaction with its own gas, its own confirmation and its own chance of failing.
The dangerous state is partial application, where the change lands on three chains and silently misses two. Users then face different rules depending on where they interact, and the discrepancy is often discovered only when something breaks.
Designing for partial failure
Treat each destination as an independent execution with its own status, receipt and retry path. A dashboard showing four confirmations and one pending is far more useful than a single success flag that hides the gap.
Decide in advance whether the change should be reverted everywhere if one chain fails, or held until the last chain catches up. Making that call under time pressure rarely produces a good answer.
Keep the execution path connected: this guide pairs well with dao governance metrics, dao compliance reporting and dao software, which cover the neighbouring steps between an approved vote and a settled onchain transaction.
Key concepts explained
New to this topic? These are the core terms you will meet again and again in governance work. Understanding them makes every proposal easier to read.
- Cross-chain message
- A verified instruction sent from the governance chain to a satellite chain, carrying the payload to execute there. Bridges and messaging protocols deliver it.
- Hub-and-spoke governance
- A model where one chain hosts voting and all other chains receive execution instructions. It keeps one source of truth while the protocol lives everywhere.
- Message finality
- The point where a cross-chain message can no longer be reverted. Execution should wait for finality on both sides before being marked complete.
- Execution record
- The pairing of the origin vote hash with the destination transaction hash. Without it, a DAO cannot prove a remote chain executed what was approved.
Frequently asked questions
- How does cross-chain governance work?
- A vote is held on one chain, and the approved instruction is relayed to contracts on other chains through a messaging bridge or by authorised executors submitting the equivalent transaction on each network.
- What is the main risk in cross-chain execution?
- Inconsistent state. If a change applies on some chains and not others, the protocol behaves differently by network until the missing executions are completed.
- Do you need a bridge for cross-chain governance?
- Not always. Some teams use a trusted executor set on each chain instead of a messaging bridge, trading bridge risk for signer trust.