Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
What Is a Guardian Set in Crypto?
The 19-entity network that signs every Wormhole cross-chain message — and what trusting them actually means for your funds.
A guardian set is Wormhole’s network of 19 independent validator companies. They observe, sign, and verify every cross-chain message the protocol carries. At least 13 must sign before any message counts as valid.
One quick note on the name. The Wormhole Guardian Set is specific cross-chain bridge infrastructure. The phrase “guardian set crypto” also pulls up the GUARD token, Theta Network guardian nodes, and even an Elden Ring armor set. None of those are covered here. This page is about Wormhole’s 13-of-19 validator quorum, and nothing else.
Wormhole is more than a token bridge. It is a cross-chain messaging protocol that connects more than 30 blockchain networks. The Guardian Set sits at the centre of it as the trust engine.
So the Guardian Set stands between your transaction and the destination chain. That is true every time you move assets through a Wormhole-powered bridge, swap cross-chain via a Wormhole dApp, or touch a protocol that pulls Wormhole data feeds. Know what those 19 companies can and cannot do, and you know exactly what you are trusting with your funds.
Key Takeaways
- The Wormhole Guardian Set is a fixed group of 19 validator companies that sign every cross-chain message using a 13-of-19 supermajority — no single entity can approve or block a transfer alone.
- Guardians use a Proof-of-Authority model rather than Proof-of-Stake: each entity holds exactly one vote regardless of size, and there is no automatic slashing for misbehaviour.
- The worst case is 13-guardian collusion or compromise, which could produce fraudulent VAAs. The 2022 Wormhole hack was a smart contract bug instead, and the guardians functioned correctly.
What a Guardian Set Is in Wormhole
Wormhole passes arbitrary data between blockchains. Token transfers are just one use case. Protocols also use it to relay price feeds, governance votes, and NFT metadata across chains. The Guardian Set makes all of that possible by validating those messages before they reach their destination.
Each guardian is an independent validator company. Think professional node operators, crypto infrastructure providers, and institutional entities with a publicly known identity. There are 19 of them.
They run on a Proof-of-Authority (PoA) model. So a new guardian gets in through governance approval by the existing set, not by staking the most tokens. Identity and reputation are the admission criteria here. Economic bonding comes second.
Thirteen is the number to remember. Any cross-chain message needs at least 13 of the 19 guardians to sign it before it counts. Each of those 13 must independently see the source-chain event and sign the message hash. That threshold is a two-thirds supermajority, hardcoded into the protocol.
The table below maps the core guardian set properties to what they mean in plain terms.
| Guardian Set Property | What It Means |
|---|---|
| 19 total guardians | 19 independent entities, so any single one failing does not stop the network |
| 13-of-19 signing quorum | Two-thirds supermajority required, which a minority cannot manipulate |
| Proof-of-Authority model | Guardians are permissioned and known, with no open validator entry via staking |
| Equal weight per guardian | Each entity holds exactly 1 vote, so Google Cloud and a small validator shop carry the same weight |
| No stake-weighted voting | Size of assets under management does not change signing power |
People often assume 19 validators means a centralized system. It is not that simple. No single entity controls the outcome, and 13 have to agree on their own.
But the set is small and permissioned rather than open. So the trust model is narrower than a 1,000-node Proof-of-Stake chain. Wormhole trades trustless breadth for speed and reliability. Whether that trade is worth it depends on what you want from a cross-chain protocol.
How the Guardian Set Verifies Cross-Chain Messages
Send a message through Wormhole and the Guardian Set runs it through six stages. Only then does the destination chain accept it. Here is the full path a message takes.
- A transaction lands on the source chain and emits a Wormhole message event from the core contract.
- All 19 guardians watch their own full node for that source chain and detect the event.
- Each guardian signs the message hash using t-Schnorr multisig. It then broadcasts that signature to the Wormhole gossip network, the peer-to-peer layer connecting all guardian nodes.
- Once 13 signatures pile up, they aggregate into a VAA, a Verifiable Action Approval. The VAA is the cryptographic packet that proves a quorum agreed on the message contents.
- A relayer, automated or user-run, picks up the VAA and submits it to the destination chain.
- The destination chain’s Wormhole core contract checks the VAA’s signatures against the guardian set stored for the index in the VAA header. If they check out, the message is accepted and executed.
The guardian set index earns its own note. Every VAA header carries a sequential integer that points to the exact version of the guardian set that signed it. When the set updates, the index climbs by one. Destination contracts store the current and recent guardian public keys at each index. So they can verify both fresh and recently signed VAAs without confusion.
Not every chain gets watched by all 19 guardians. On major chains like Ethereum and Solana, all 19 run full nodes and observe on their own. On smaller chains, Wormhole uses delegated observation instead. A subset of guardians acts as delegates and watches the chain for the canonical set, which waits for a delegate quorum before signing. So a small chain’s looser setup cannot drag down the security threshold on the big ones.
Cross-chain verification only became a problem once one message had to move across many networks. For the wider picture behind that challenge, the omnichain model explains why protocols reach for designs like this.
Who the Wormhole Guardians Are
The 19 guardian companies are public. No anonymous node operators, no pseudonyms. That open identity is central to the security model, because reputation does the deterrent work when there is no automatic slashing.
Known guardians include Jump Crypto, one of the original and most prominent participants, and Certus One, a founding-era validator. The list also runs through Figment, Chorus One, P2P Validator, Forbole, Chainstack, and Google Cloud, which joined in 2024. The full live list sits on the Wormhole Dashboard and updates whenever the set changes.
| Guardian | Entity Type |
|---|---|
| Jump Crypto | Crypto trading and infrastructure firm |
| Certus One | Validator company (founding-era participant) |
| Figment | Institutional staking and validator provider |
| Chorus One | Validator operator and research firm |
| P2P Validator | Validator infrastructure provider |
| Forbole | Validator and blockchain explorer operator |
| Chainstack | Managed blockchain node infrastructure |
| Google Cloud | Cloud and infrastructure provider (joined 2024) |
The equal-weight model does real work. Google Cloud, with its global infrastructure, holds the same 1 vote as a mid-size validator shop. No guardian earns more influence by being bigger. That is deliberate, and it keeps the signing quorum from tilting toward the largest players.
Guardian rotation is not a token-holder vote either. A two-thirds supermajority of current guardians must sign a governance VAA to authorise any change. The Wormhole DAO handles broader protocol governance, but guardian membership stays with the guardians. New members join only when the existing set approves them together.
The Guardian Set Trust Model — What You Are Actually Trusting
Use any Wormhole-powered product and you are trusting 19 named companies to behave. Three risks deserve to be named plainly.
The first is censorship. Any seven or more guardians acting together can block a specific message forever. They still cannot forge a VAA or steal funds, because that takes 13. But seven guardians agreeing to ignore an address or transaction can effectively freeze it. That is a censorship threshold rather than a security threshold. Your funds never reach an attacker. They just may not move at all.
The second is the missing slashing. On a standard Proof-of-Stake network, a validator that misbehaves loses bonded tokens automatically. Guardians have no such switch. A bad guardian faces governance removal and a wrecked reputation, which stings for a company with clients and brand equity. But there is no automatic on-chain fund seizure. So the economic deterrent runs softer than in PoS.
The third is the catastrophic one. Picture 13 or more guardians colluding or getting compromised at the same time. At that point, they can produce fraudulent VAAs and tell destination chains to release assets with no matching source-chain deposit. This is the worst case, and it has never happened. The reasons it holds up are real. All 19 entities are large, identifiable, and regulated or monitored where they operate. No single attacker can quietly own 13 of them. And no one-time exploit pays enough to justify torching every company involved.
The 2022 Wormhole hack is worth a close look, because the guardians did not fail. The February 2022 exploit, covered in Wormhole’s post-mortem, caused a $320 million loss through a smart contract flaw. An attacker abused how the Solana-side Wormhole contract validated a system account. That let them skip the signature check and mint 120,000 wrapped ETH with no backing. The guardians signed nothing fraudulent. The bug lived in the on-chain verification code, well away from the signing infrastructure.
There is another way to verify cross-chain state that skips trusted committees entirely. Weigh the tradeoffs and zero-knowledge proofs make a sharp contrast with the guardian set’s multisig model.
Guardians now stake W tokens too, but that is a governance stake, not a yield play. If staking is new to you, liquid staking is a useful reference, since guardian staking works nothing like a yield-generating LST position.
How the Guardian Set Changes — Updates, Rotation, and Governance
Guardian sets are versioned. The current one is not the first, and it will not be the last. Each version is tracked through the guardian set index, a sequential integer stored in every chain’s Wormhole core contract and stamped into every VAA header.
A change happens when a guardian is added, removed, or replaced. The process is tight. The existing guardians sign a governance VAA with a two-thirds supermajority. That VAA goes on-chain, and each chain’s core contract executes it. The contract writes the new set and gives it an index exactly one higher than the current one. Skip an index or assign an out-of-order number, and the upgrade fails on-chain. That is what blocks forged upgrades.
The table below breaks down each update step and what it means for you.
| Update Step | What It Means |
|---|---|
| Guardians reach two-thirds supermajority agreement | 13 of 19 must sign the governance VAA — the same threshold as message signing |
| Governance VAA is submitted on-chain | Each destination chain’s core contract receives and executes the upgrade independently |
| New guardian set index is assigned (+1) | Old VAAs stay valid under the previous index, while new VAAs must use the new index |
| Old set remains accepted for a grace period | In-flight VAAs signed before the upgrade are not invalidated immediately |
Since 2024, the set is no longer purely reputation-gated. Guardians now have to stake W tokens, the Wormhole protocol’s native governance and utility token, to keep their seat. That ties each guardian’s money to the protocol far more directly than reputation alone. A guardian that acts up now risks both its name and its stake.
Google Cloud’s 2024 addition shows the upgrade process working as designed. Google Cloud passed guardian approval. The existing guardians signed the governance VAA. The new set propagated across every supported chain. The index climbed by one, and no cross-chain messages were interrupted along the way.
Curious how a token like W carries both governance and staking roles? The mechanics of token issuance explain the underlying model that gives W its job in the guardian set.
FAQ
How many guardians are in the Wormhole guardian set?
There are 19 guardians in the current Wormhole Guardian Set. For a cross-chain message to be validated, at least 13 of the 19 must sign it — a supermajority of roughly two-thirds. Below that threshold, no VAA is produced and the message is not relayed.
What is a VAA and how does the guardian set produce one?
A VAA (Verifiable Action Approval) is the cryptographic packet that proves the guardian set observed and agreed on a cross-chain message. Once 13 guardians sign a message’s hash using t-Schnorr multisig, the signatures aggregate into a VAA. The header carries the guardian set index, each guardian’s signature, and the message payload. That index is the on-chain pointer to the exact guardian version that signed it.
Is the Wormhole guardian set decentralized?
It depends on how you define decentralized. The guardian set uses 19 publicly known, independently operated entities under a Proof-of-Authority model. That beats a single custodian by a mile. It still falls short of a 1,000-node PoS chain. No single entity controls the outcome, since 13 must agree, but the set is small and permission-based rather than open. Wormhole’s design favours speed and reliability over trustless-validator breadth.
Can the guardian set be changed, and what happens during an update?
Yes. A two-thirds supermajority of the existing guardians can sign a governance VAA to update the set. The new set gets a sequential guardian set index (always the current index plus one). Destination contracts on every supported chain then accept signatures from the new index going forward. Existing signed VAAs remain valid against the index they were signed under.
Was the 2022 Wormhole hack caused by a guardian set failure?
No. The February 2022 exploit ($320 million) was a smart contract bug in the on-chain signature verification code, not a guardian compromise. An attacker spoofed a system account to bypass signature checks and mint 120,000 wETH without backing. The guardians signed no malicious messages — the flaw was in how the destination contract validated the guardian inputs, not in the guardians’ own signing behaviour.
How is the guardian set different from LayerZero validators or Axelar validators?
Wormhole’s guardian set uses a fixed group of 19 PoA entities. LayerZero uses a permissioned-but-configurable Decentralised Validator Network (DVN) model where each dApp can choose its own verifiers. Axelar uses a PoS validator set where validators stake AXL tokens and face slashing. Each model trades decentralisation breadth, speed, and economic security differently. Wormhole’s model optimises for speed and operational reliability with a smaller, reputation-backed set.
