History – Wormhole (W)
Back1 block modified
- Modified – Text at Block 8
How Caper approaches this A …et carrying its votes. So the
honestuseful comparison is not feature-for-feature– Caper simply, since Caper does not do what Wormhole does. Theusefulcontrast is about who sits bet…vote cast on a spoke chain isonlyfinal only once a supermajority of Guard…ssage carrying it to the hub.In aA caperthere ihas no such layer: a member's v…ng/voting-and-delegation) iscomputed on-ledger from balancesworked out on Radix from what they already hold. T, the contract combines governance tokens held with earned, non-transferable vote tokens – verified in compute_vote_weight (contracts/common/src/lib.rs), where the held balance enters as a multiplieraper's tokens together with the votes they have earned by casting ballots, so alargebig bag alone canno't capture controlwithout earned votes. And an outvoted member is not stuck arguing with the majority: exit (contracts/logic/src/lib.rs) lets them withdraw a treasury share equal to that same canonical vote weight, redeem. An outvoted member can exit any time (/wiki/dao-governance/concepts/membership/rage-quit-and-exit-rights) for their fair share of the treasury instead of arguingbowith their vote and governance tokensmajority. Nothing has to be relayed or…attested for either to settle.
1 block modified
- Modified – Text at Block 9
References - Wormhole Docs
—– MultiGov overview (https://wo…overview/) - Wormhole Docs—– MultiGov hub-and-spoke archit… Wormhole / Tally / ScopeLift—– announcing MultiGov (https://…ver-multichain) - Wormhole—– the W airdrop explained (allo…drop-explained) - Wormhole—– W token, one year on (https:/…t-present-and) - The Block—– Wormhole replenishes bridge a…million-exploit) - Halborn—– explaining the February 2022 …e-wormhole-hack-february-2022)
6 blocks modified
- Modified – Text at Block 1 → Block 1
What it is A generic cross-ch…ocol (https://wormhole.com/)
—– a layer that carries verified…-w-tokens-past-present-and) )—– staked and delegated for gove…sals from any supported chain—– no single hub to bridge into …ded by the Wormhole Foundation - Modified – Text at Block 2
Overview Most DAOs in this di…er primitives in this section
—– UMA (/wiki/daos/infrastructu…s/infrastructure/aragon-dao)—– as infrastructure other prot…/fundamentals/types-of-daos) . - Modified – Text at Block 4
The February 2022 exploit Wha…not in the Guardians' honesty
—– it was in a contract that let… trust question underneath it. - Modified – Text at Block 6
MultiGov: governing from any c…ature is not its distribution
—– it is where you can vote with…n generalises beyond Wormhole—– MultiGov is offered as reusab…the message layer carrying it. - Modified – Text at Block 7
What the DAO governs The Worm…ype it fills here is specific
—– a DAO whose subject spans eve… single-registry scope of ENS. - Modified – Text at Block 8
How Caper approaches this A …on is not feature-for-feature
—– Caper simply does not do what… non-transferable vote tokens—– verified in compute_vote_weig…attested for either to settle.
4 blocks modified
- Modified – Text at Block 1 → Block 1
What it is A generic cross-ch…astructure/guardians/) of 19
validnode operators observes and attests events;a two-thirds signature quorum forms the verified message every chain truststhe docs put the threshold exactly – “a quorum of 13 signatures is required to produce a valid VAA” – and that VAA is the credential every destination chain trusts (read 20 September 2026) Scale 45+ blockchains connected and $68bn of all-time transfer volume enabled (https://wormhole.com/) , per the protocol's own homepage, read 20 September 2026 Incubated by Jump Crypto (20…ded by the Wormhole Foundation - Modified – Text at Block 2
Overview Most DAOs in this di…bitrary contract calls across
more than 30 connected networksthe 45+ networks it connects (https://wormhole.com/) as of September 2026. The protocol was incubated b…/fundamentals/types-of-daos) . - Modified – Text at Block 3
The Guardian network Wormhole…ixed set of validators called Guardians
(https://wormhole.com/docs/protocol/infrastructure/guardians/) —– currently 19 established node…emitted message and signs it.WThen two-thirds of them sign, the signatures bundle into a Verified Action Approval (documentation puts the threshold exactly: “A quorum of 13 signatures is required to produce a valid VAA)” (https://wormhole.com/docs/protocol/infrastructure/vaaguardians/)—– the credential that any desti…tem is only as trustworthy as 13 of those 19 signers. Wormhole's roadmap has pushed toward hardening that assumption — a larger and more diverse Guardian set, staking, and light-client verification for some routes —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” (https://wormhole.com/docs/protocol/infrastructure/guardians/) , 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 (https://wormhole.com/blog/stake-for-governance-is-now-live-for-w-token-holders) , butaitits core the network still asks users to trust that a supermajority of Guardians will not collude or be compromisedbuys 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 (/wiki/daos/staking/rocket-pool) page records on the validator side. - Modified – Text at Block 5
The W token W launched on 3 April 2024
(https://wormhole.com/blog/connecting-the-internet-economy-wormhole-and-the-w-tokens-past-present-and)as a natively multichain token…rom one home. Total supply is capped at 10 billion(https://decrypt.co/216450/wormhole-airdrop-w-tokenomics-unlock-schedule-eligibility), with about 1.8 billion circu…r-year release schedule. The genesis allocation(https://wormhole.com/blog/w-airdrop-explained)splits the supply across commu… 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 (https://www.coingecko.com/en/coins/wormhole) . 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.
1 block modified
- Modified – Text at Block 8
How Caper approaches this A …ompute_vote_weight (contracts/
logiccommon/src/lib.rs), where the held b…attested for either to settle.
9 blocks added
- Added – Text at Block 1 → Block 1
What it is A generic cross-chain messaging protocol (https://wormhole.com/) — a layer that carries verified messages between blockchains, so an app on one chain can act on events from another. The well-known token bridge is one application built on top of it. Category Interoperability · cross-chain messaging · oracle Token W (ERC-20, natively multichain (https://wormhole.com/blog/connecting-the-internet-economy-wormhole-and-the-w-tokens-past-present-and) ) — staked and delegated for governance across Ethereum, Base, Solana, Arbitrum, and Optimism Governance archetype The cross-chain-native DAO: via MultiGov (https://wormhole.com/docs/products/multigov/overview/) , W holders create, vote on, and execute proposals from any supported chain — no single hub to bridge into Security model A Guardian network (https://wormhole.com/docs/protocol/infrastructure/guardians/) of 19 validators observes and attests events; a two-thirds signature quorum forms the verified message every chain trusts Incubated by Jump Crypto (2021); now stewarded by the Wormhole Foundation
- Added – Text at Block 2
Overview Most DAOs in this directory govern a protocol that lives on one chain. ENS (/wiki/daos/infrastructure/ens-dao) is Ethereum. Optimism (/wiki/daos/networks/optimism-collective) 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 (https://wormhole.com/) . 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 more than 30 connected networks. 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 (/wiki/daos/infrastructure/uma) , Safe (/wiki/dao-governance/tooling/treasury/safe) , Aragon (/wiki/daos/infrastructure/aragon-dao) — as infrastructure other protocols build on (/wiki/dao-governance/concepts/fundamentals/types-of-daos) .
- Added – Text at Block 3
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 (https://wormhole.com/docs/protocol/infrastructure/guardians/) — currently 19 established node operators. Each Guardian independently observes an emitted message and signs it. When two-thirds of them sign, the signatures bundle into a Verified Action Approval (VAA) (https://wormhole.com/docs/protocol/infrastructure/vaas/) — 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 those 19 signers. Wormhole's roadmap has pushed toward hardening that assumption — a larger and more diverse Guardian set, staking, and light-client verification for some routes — but at its core the network still asks users to trust that a supermajority of Guardians will not collude or be compromised.
- Added – Text at Block 4
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 (https://www.halborn.com/blog/post/explained-the-wormhole-hack-february-2022) on the Solana–Ethereum token bridge to forge the appearance of a valid deposit, minting 120,000 wrapped ETH (~$325M) (https://www.theblock.co/post/132909/wormhole-replenishes-its-blockchain-bridge-after-325-million-exploit) 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 (https://www.theblock.co/post/132909/wormhole-replenishes-its-blockchain-bridge-after-325-million-exploit) to keep the bridge solvent, and in February 2023 recovered roughly $225M from the attacker in a counter-exploit (https://blockworks.com/news/jump-crypto-wormhole-hack-recovery) . The episode is a standing entry in the catalogue of how these systems fail (/wiki/dao-governance/concepts/analysis/how-daos-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.
- Added – Text at Block 5
The W token W launched on 3 April 2024 (https://wormhole.com/blog/connecting-the-internet-economy-wormhole-and-the-w-tokens-past-present-and) as a natively multichain token, minted directly on several chains rather than bridged from one home. Total supply is capped at 10 billion (https://decrypt.co/216450/wormhole-airdrop-w-tokenomics-unlock-schedule-eligibility) , with about 1.8 billion circulating at genesis and roughly 82% initially locked on a four-year release schedule. The genesis allocation (https://wormhole.com/blog/w-airdrop-explained) 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.
- Added – Text at Block 6
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 (https://wormhole.com/blog/wormhole-tally-and-scopelift-announce-multigov-the-first-ever-multichain) , billed as the first multichain governance system, and the Wormhole DAO became its first adopter. MultiGov uses a hub-and-spoke design (https://wormhole.com/docs/products/multigov/concepts/architecture/) . One chain is the hub, where a HubGovernor contract creates proposals, tallies votes, and executes outcomes through a timelock (/wiki/dao-governance/concepts/voting/governance-timelocks) . 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 (/wiki/dao-governance/concepts/fundamentals/on-chain-vs-off-chain-governance) stretched across chains instead of pinned to one. The pattern generalises beyond Wormhole — MultiGov is offered as reusable governance tooling (/wiki/dao-governance/tooling/dao-tooling-overview) for any multichain DAO, in the same family as the single-chain frameworks spl-governance (/wiki/dao-governance/tooling/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 (/wiki/dao-governance/concepts/voting/voting-and-delegation) logic is only as final as the message layer carrying it.
- Added – Text at Block 7
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 (/wiki/dao-governance/concepts/membership/subdaos-and-working-groups) , 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 (/wiki/dao-governance/tooling/voting/kleros) or the single-registry scope of ENS.
- Added – Text at Block 8
How Caper approaches this A caper (/wiki/foundations/what-is-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 honest comparison is not feature-for-feature — Caper simply does not do what Wormhole does. The useful contrast is about who sits between a member and their vote. In MultiGov, a vote cast on a spoke chain is only final once a supermajority of Guardians attests the message carrying it to the hub. In a caper there is no such layer: a member's vote weight (/wiki/dao-governance/concepts/voting/voting-and-delegation) is computed on-ledger from balances they already hold. The contract combines governance tokens held with earned, non-transferable vote tokens — verified in compute_vote_weight (contracts/logic/src/lib.rs), where the held balance enters as a multiplier, so a large bag alone cannot capture control without earned votes. And an outvoted member is not stuck arguing with the majority: exit (contracts/logic/src/lib.rs) lets them withdraw a treasury share equal to that same canonical vote weight, redeeming both their vote and governance tokens. Nothing has to be relayed or attested for either to settle.
- Added – Text at Block 9
References - Wormhole Docs — MultiGov overview (https://wormhole.com/docs/products/multigov/overview/) - Wormhole Docs — MultiGov hub-and-spoke architecture (https://wormhole.com/docs/products/multigov/concepts/architecture/) - Wormhole / Tally / ScopeLift — announcing MultiGov (https://wormhole.com/blog/wormhole-tally-and-scopelift-announce-multigov-the-first-ever-multichain) - Wormhole — the W airdrop explained (allocation) (https://wormhole.com/blog/w-airdrop-explained) - Wormhole — W token, one year on (https://wormhole.com/blog/connecting-the-internet-economy-wormhole-and-the-w-tokens-past-present-and) - The Block — Wormhole replenishes bridge after $325M exploit (https://www.theblock.co/post/132909/wormhole-replenishes-its-blockchain-bridge-after-325-million-exploit) - Halborn — explaining the February 2022 Wormhole hack (https://www.halborn.com/blog/post/explained-the-wormhole-hack-february-2022)