Wormhole (W)

Overview

Most DAOs in this directory govern a protocol that lives on one chain. ENS is Ethereum. Optimism is one rollup. Wormhole is the exception: it is the plumbing between chains, and it is governed by a DAO whose voting is itself spread across chains. That makes it the clearest example of the cross-chain-native governance archetype.

Wormhole is a generic message-passing protocol. An application emits a message on a source chain; Wormhole's validators attest to it; a contract on the destination chain accepts the attested message and acts on it. Token transfers are the most visible use, but the same rails carry governance votes, oracle prices, and arbitrary contract calls across the 45+ networks it connects as of September 2026. The protocol was incubated by Jump Crypto in 2021 and is now stewarded by the Wormhole Foundation.

Because the value it moves is other protocols' value, Wormhole belongs alongside the other primitives in this section – UMA, Safe, Aragon – as infrastructure other protocols build on.

The Guardian network

Wormhole does not verify messages with a light client or a fraud proof. It verifies them with a fixed set of validators called Guardians – currently 19 established node operators. Each Guardian independently observes an emitted message and signs it. The documentation puts the threshold exactly: “A quorum of 13 signatures is required to produce a valid VAA” – the credential that any destination chain accepts as proof the event really happened.

This is a deliberately simple trust model, and its honesty is a design choice worth being clear about: the whole system is only as trustworthy as 13 of those 19 signers. Wormhole says so itself, and frames the design as transitional rather than permanent – “Once ZKPs become widely viable, the network can evolve into a fully trustless system”, and the set “can expand” as threshold signatures gain broader support. Read on 20 September 2026, both remain conditional: the documentation describes no shipped zero-knowledge verification path and no expansion beyond 19.

One thing that has shipped is easy to mistake for a hardening of this assumption and is not. Staking W went live on 6 June 2024, but it buys governance voting power – “By staking your W tokens, you delegate your voting power” – and carries no slashing and no role in attesting messages. Nothing a W holder stakes is at risk if a Guardian misbehaves, and nothing they stake makes a Guardian less able to. Securing the message layer and governing the protocol are separate purchases here, which is the same split the Rocket Pool page records on the validator side.

The February 2022 exploit

What happens when the verification layer fails is not hypothetical. On 2 February 2022, an attacker exploited a deprecated signature-verification function on the Solana–Ethereum token bridge to forge the appearance of a valid deposit, minting 120,000 wrapped ETH (~$325M) out of nothing. The bug was not in the Guardians' honesty – it was in a contract that let the attacker bypass their check entirely.

Jump Crypto, which incubated the protocol, replaced the 120,000 ETH within about a day to keep the bridge solvent, and in February 2023 recovered roughly $225M from the attacker in a counter-exploit. The episode is a standing entry in the catalogue of how these systems fail: a cross-chain protocol's real attack surface is the message-verification layer, not the token contract, and a well-capitalised backstop can paper over a loss but not the trust question underneath it.

The W token

W launched on 3 April 2024 as a natively multichain token, minted directly on several chains rather than bridged from one home. Total supply is capped at 10 billion, with about 1.8 billion circulating at genesis and roughly 82% initially locked on a four-year release schedule.

The genesis allocation splits the supply across community (17%), the ecosystem and growth fund (31%), the foundation treasury (23.3%), core contributors (12%), strategic network partners (11.6%), and Guardian node operators (5.1%). The launch airdrop distributed 6.75% (about 674.8M W) to more than 400,000 wallets, weighted toward addresses that had actually used Wormhole-connected apps.

Two and a half years in, the unlock is running ahead of its own calendar. Read on 20 September 2026, circulating supply is 6,516,776,558 W against the 10 billion cap – 65.2% of supply, at $0.01157, a $75.4m market capitalisation and a $115.6m fully diluted valuation. A four-year schedule that began in April 2024 is about 42% through its calendar and has released 65% of its tokens, so the remaining float is back-loaded less steeply than a reader of the genesis figure would assume. The figure that matters for governance is the same one: vote weight tracks circulating W, and it has grown 3.6× since launch, so a stake that carried a given share of the vote at genesis carries under a third of it now without anyone selling a token.

MultiGov: governing from any chain

W's defining feature is not its distribution – it is where you can vote with it. In late 2024 Wormhole, Tally, and ScopeLift shipped MultiGov, billed as the first multichain governance system, and the Wormhole DAO became its first adopter.

MultiGov uses a hub-and-spoke design. One chain is the hub, where a HubGovernor contract creates proposals, tallies votes, and executes outcomes through a timelock. Every other supported chain is a spoke: a SpokeVoteAggregator collects local votes and forwards them to the hub over Wormhole messaging, where a HubVotePool folds them into the tally. A holder on Solana or Base votes with tokens that never leave their chain, and the outcome propagates back out to spoke executors. It is on-chain governance stretched across chains instead of pinned to one.

The pattern generalises beyond Wormhole – MultiGov is offered as reusable governance tooling for any multichain DAO, in the same family as the single-chain frameworks spl-governance and Aragon. It also inherits their hard question: the votes themselves now ride the Guardian-attested rails, so the delegation and vote-counting logic is only as final as the message layer carrying it.

What the DAO governs

The Wormhole DAO steers the protocol's parameters, treasury, and the direction of its cross-chain standards, while day-to-day operation of the Guardian network and core development sit with node operators and the foundation. As with most infrastructure DAOs, the elected surface is narrower than the protocol's full footprint: token holders set policy, but they do not personally re-sign every VAA. The archetype it fills here is specific – a DAO whose subject spans every connected chain and whose voting does too, distinct from the single-chain adjudication of Kleros or the single-registry scope of ENS.

How Caper approaches this

A caper is single-ledger by construction: it lives entirely on Radix, with no cross-chain messaging and no external validator set carrying its votes. So the useful comparison is not feature for feature, since Caper does not do what Wormhole does. The contrast is about who sits between a member and their vote.

In MultiGov, a vote cast on a spoke chain is final only once a supermajority of Guardians attests the message carrying it to the hub. A caper has no such layer: a member's vote weight is worked out on Radix from what they already hold, the caper's tokens together with the votes they have earned by casting ballots, so a big bag alone can't capture control. An outvoted member can exit any time for their fair share of the treasury instead of arguing with the majority. Nothing has to be relayed or attested for either to settle.

References

• Wormhole Docs – MultiGov overview
• Wormhole Docs – MultiGov hub-and-spoke architecture
• Wormhole / Tally / ScopeLift – announcing MultiGov
• Wormhole – the W airdrop explained (allocation)
• Wormhole – W token, one year on
• The Block – Wormhole replenishes bridge after $325M exploit
• Halborn – explaining the February 2022 Wormhole hack