What Is Snapshot: Complete DAO Governance Voting Guide (2026)

If you have ever held a governance token like UNI, AAVE, or ENS and wondered how voting actually works, the answer is almost always the same: it happens on snapshot. Snapshot is the off-chain voting platform that powers governance for more than 35,000 decentralized communities, including most of the largest DAOs in crypto. If you have ever voted on a Uniswap fee switch, signed an ENS constitutional proposal, or delegated your AAVE voting power, you have used Snapshot, even if you did not know its name.

What makes Snapshot special is that voting is completely free. There is no gas fee, no transaction confirmation wait, and no need to spend ETH to make your voice heard. Instead of writing votes to the Ethereum blockchain, Snapshot uses cryptographically signed messages stored on IPFS. Your wallet signs a payload that proves you support a proposal, and that signature is just as binding as an on-chain transaction for governance purposes. This single design choice unlocked DAO participation for millions of token holders who would otherwise be priced out by gas fees.

In this guide you will learn exactly what Snapshot is, how its signature-based voting mechanic works, why every major DAO uses it, what a snapshot block is and why it stops vote-buying via flash loans, the full catalog of voting strategies (ERC-20, NFT, multichain, ve-token, quadratic), how SafeSnap turns off-chain votes into on-chain execution, and how Snapshot compares to Tally, Aragon, Boardroom, and Agora. By the end, you will be able to create your own proposal from scratch.

What Is Snapshot?

Snapshot is a decentralized, off-chain governance platform that allows DAOs and token communities to create proposals, run polls, and collect votes without paying any gas fees. It was originally launched as snapshot.page by the Balancer Labs team in August 2020, and later rebranded to snapshot.org as it grew into the de facto standard for DAO voting. Today it is maintained by Snapshot Labs, an independent entity that builds open-source governance infrastructure.

At its core, Snapshot is built on a simple but powerful idea: voting does not need to be on-chain to be legitimate. When you vote on Snapshot, your wallet produces a digital signature using the EIP-712 typed-data standard. That signature contains the proposal ID, your wallet address, your chosen option, and a timestamp. Snapshot's backend verifies the signature against your wallet's public key, calculates your voting power based on the strategy defined by the DAO, and stores the result on IPFS. The vote is now permanent, verifiable, and provably yours, but it never touched a blockchain transaction.

This means voting on Snapshot is functionally identical to a notarized statement: cryptographically signed, publicly auditable, and impossible to forge. The only thing missing is on-chain execution, which is solved separately by tools like SafeSnap and Reality.eth that we will cover later. For the vast majority of DAO decisions, off-chain consensus is enough. Multisig signers, core team members, or community delegates execute the result on-chain after the vote concludes.

Why Off-Chain Voting Matters

To understand why Snapshot became so dominant so fast, you need to appreciate what voting on-chain looked like before it existed. Compound was one of the first major DAOs and ran governance entirely on-chain using its Governor Bravo contract. Every single vote required an Ethereum transaction. During peak gas-fee periods in 2021, casting one vote could cost between $30 and $200 in gas. For small token holders, this was completely prohibitive. Why spend $50 to vote when your voting power was worth $20?

The result was that on-chain governance was dominated by whales. Anyone with significant token holdings could afford gas, but retail holders effectively had no voice. Even worse, low participation made it easier for a small group of large holders to push through controversial proposals because quorum requirements were rarely met. Governance was theoretically decentralized but practically captured by a handful of wallets.

Snapshot solved three problems simultaneously. First, gas-free voting opens participation to anyone holding a single token. A holder with $5 of UNI can vote with the same legitimacy as a fund with $5 million of UNI. Second, the user experience is dramatically simpler. You connect a wallet, click an option, sign a message, and you are done. No transaction confirmation, no waiting for blocks, no failed transactions because of gas estimation errors. Third, off-chain voting is environmentally friendlier because no block space is consumed for routine governance decisions.

The combination of these three benefits made Snapshot adoption explosive. Within twelve months of launch, it became the default tool for new DAOs. By 2026, calling something "DAO governance" implicitly means Snapshot governance unless otherwise specified.

The Voting Flow: From Proposal to Result

Snapshot voting follows a predictable five-step flow. Every proposal moves through the same pipeline regardless of which DAO is running it. Understanding this flow is essential because each step has its own security and game-theory implications.

Step one is proposal creation. Any wallet that meets the DAO's submission threshold (often holding a minimum amount of governance tokens) can write a proposal. The author signs the proposal payload with their wallet, and it appears on the DAO's Snapshot space as a draft. Step two is the snapshot block. At the moment the proposal goes live, Snapshot records a specific block number on the relevant chain. Voting power is calculated from token balances at that exact block, frozen forever. Step three is voting. During the active window (often 3 to 7 days), any wallet that held governance tokens at the snapshot block can sign their vote. Step four is IPFS persistence. All signatures are pinned to IPFS so the proposal, votes, and results remain accessible even if Snapshot's frontend goes offline. Step five is execution, which only happens for proposals that need to trigger on-chain actions like treasury transfers, contract upgrades, or parameter changes.

The Snapshot Block: Preventing Flash Loan Vote-Buying

The single most important security feature of Snapshot is the snapshot block. When a proposal is created, Snapshot records the exact block number of the underlying chain at that moment. Voting power is then calculated based on token balances at that historical block, never the current balance. This sounds like a small detail, but it neutralizes an entire class of governance attack.

Before snapshot-based voting was standard, governance attackers could simply borrow a massive amount of governance tokens using a flash loan, vote on a proposal, and return the tokens within the same transaction. This is how the Beanstalk attack in April 2022 drained $182 million from the protocol. The attacker used a flash loan to acquire enough governance tokens to pass a malicious proposal that transferred the treasury to their own address. The attack worked because Beanstalk's governance contract checked the attacker's current balance at vote time, not at a frozen historical block.

Snapshot's snapshot block mechanism makes this attack mathematically impossible. If the proposal was created at block 18,500,000, then voting power is calculated from balances at block 18,500,000. An attacker who borrows tokens through a flash loan at block 18,500,400 has zero voting power because they did not hold those tokens at the snapshot block. They can sign all the votes they want, but Snapshot's strategy resolver will return zero voting power for every one of them.

This is why every modern DAO uses Snapshot or a snapshot-style mechanism. Any governance system that lets you vote with tokens borrowed in the current block is fundamentally broken and will eventually be drained.

Voting Strategies: The Catalog

One of the most underrated features of Snapshot is its strategy system. A strategy is a function that defines how voting power is calculated for a DAO. Snapshot supports more than 500 different strategies out of the box, and DAOs can combine multiple strategies in a single space. This flexibility is why Snapshot works for everything from a simple ERC-20 token vote to a complex multi-chain DAO with NFT membership and vested escrow tokens.

The strategy is set per Snapshot space, and DAOs can layer multiple strategies. For example, a DAO might combine an ERC-20 balance strategy with a staking contract strategy and an LP-token strategy, so that holders get voting power for tokens in their wallet, tokens they have staked, and tokens they have deposited as liquidity. This composability is impossible in pure on-chain governance because the gas cost of looking up balances across so many contracts would be prohibitive.

ERC-20 Balance Strategy: The Workhorse

The ERC-20 balance strategy is by far the most common and the simplest to understand. The strategy parameters include the token address, the chain ID, and any minimum balance threshold. When voters cast their ballot, Snapshot queries the historical balance of their wallet at the snapshot block via an archive node, applies any decimals adjustment, and assigns voting power proportional to the balance. One token equals one vote.

This strategy is used by Uniswap (UNI), Aave (AAVE), Curve (CRV when held directly), Balancer (BAL), 1inch (1INCH), Sushi (SUSHI), Yearn (YFI), Compound (COMP), and dozens of other top DAOs. It works well for tokens with broad distribution and clear governance utility. If you want a refresher on how these tokens work technically, our guide to the ERC-20 token standard covers everything from transfer semantics to allowance approvals.

The main weakness of pure ERC-20 voting is whale dominance. If one wallet holds 30% of the supply, that wallet can effectively force any proposal it wants because participation rarely exceeds 20% of supply. This is why many DAOs combine ERC-20 voting with delegation, where smaller holders delegate their voting power to a trusted community delegate who is more likely to actually show up and vote. Delegation is functionally a representative democracy layered on top of direct democracy, and it has become one of the defining features of mature DAO governance.

NFT-Based Voting: ENS, Nouns, and Punks

Not every DAO uses fungible tokens. Many of the most prominent NFT communities run governance through NFT-based voting strategies. The ENS DAO is one of the largest examples, although ENS technically uses the ERC-20 ENS token for voting rather than the underlying NFT domains. Nouns DAO, however, is a pure NFT governance system. Each Noun NFT (one minted per day, forever) represents exactly one vote. The voting weight cannot be diluted because no new wallets can acquire voting power without buying a Noun.

NFT voting has some interesting properties. Because each NFT is unique and indivisible, voting power is naturally discrete. You cannot split a Noun into 0.3 votes the way you might split an ERC-20 balance. This makes participation easier to reason about and harder to manipulate via small balance changes. On the other hand, NFTs are often illiquid, which means a hostile actor cannot easily accumulate voting power on the open market. The flip side is that NFT DAOs tend to have very small voter pools (often fewer than 100 active voters), which makes them vulnerable to coordination attacks if a few major holders align.

Snapshot supports several NFT strategies: simple ERC-721 ownership, ERC-1155 with quantity, NFT-with-multiplier strategies that give certain rare NFTs more weight, and NFT-staking strategies that count only NFTs staked in a specific contract. For communities like Crypto Punks, an ERC-721 ownership strategy means every Punk is one vote, regardless of rarity or floor price.

Multichain Strategy: Voting Across Networks

As DeFi spread from Ethereum mainnet to Layer 2s and alternative chains, governance tokens started existing in many places at once. AAVE exists on Ethereum, Polygon, Avalanche, Arbitrum, Optimism, and Base. SUSHI is even more spread out. A holder might have 100 tokens on mainnet and 200 on Arbitrum and 50 on Polygon, and intuitively those 350 tokens should all count toward their voting power.

Snapshot's multichain strategy solves this. It is configured with a list of (chain ID, token address) pairs and queries balances on every listed chain at the equivalent snapshot block for each chain. The results are summed and treated as a single voting power. Multichain strategies are slightly more complex because each chain has its own block time and its own snapshot block, but Snapshot's strategy resolver handles all of this transparently. From the voter's perspective, they simply connect their wallet and Snapshot calculates the right number.

Multichain voting was the killer feature that locked in Snapshot's dominance for cross-chain DAOs. The only realistic alternative was to deploy a separate governance contract on each chain and manually aggregate results, which is brittle and expensive. With Snapshot, a DAO that lives on five chains can run governance as if it lived on one.

Quadratic and Conviction Voting: Advanced Strategies

Plain token-weighted voting has a fundamental problem: it treats one wallet with a million tokens identically to ten thousand wallets with one hundred tokens each. In most cases, the broad community would prefer the latter to have more influence, but linear voting power makes this impossible. Quadratic voting was designed to fix this.

In a quadratic voting strategy, your voting power equals the square root of your token balance. A holder with 100 tokens has 10 votes. A holder with 10,000 tokens has 100 votes. A holder with 1,000,000 tokens has only 1,000 votes. The math means that doubling your tokens only multiplies your voting power by 1.41, not 2. This makes vote-buying dramatically more expensive at scale because acquiring 100x more votes requires 10,000x more tokens. Gitcoin pioneered quadratic voting for its public goods funding rounds, and several mid-sized DAOs use quadratic strategies for high-stakes decisions.

The catch is that quadratic voting is vulnerable to Sybil attacks. If a single attacker can split their tokens across many wallets, they get the square-root bonus on every wallet. To prevent this, quadratic voting only works when combined with proof-of-personhood mechanisms like Gitcoin Passport, BrightID, or World ID. Pure quadratic voting with no Sybil defense is actually worse than linear voting because attackers can easily split their stack into 1,000 wallets and get a massive boost.

Conviction voting is another advanced strategy where voting power increases the longer you hold a position on a proposal. The longer you stake your support, the more weight your vote carries. This rewards long-term commitment and reduces the impact of last-minute swing votes. 1Hive's Gardens framework popularized conviction voting, and Snapshot supports it via custom strategies for DAOs that want to experiment with this approach.

SafeSnap: From Off-Chain Vote to On-Chain Execution

Snapshot's biggest limitation is also its biggest strength: votes never touch the blockchain. This is great for gas efficiency but creates a problem when the DAO needs to actually execute something, like transferring 1 million USDC from the treasury to a grant recipient or upgrading a smart contract. Off-chain votes cannot directly trigger on-chain actions because there is no on-chain proof of consensus that smart contracts can verify.

The traditional solution is the multisig wallet. A DAO maintains a Gnosis Safe (or equivalent multisig) controlled by trusted community members. After a Snapshot vote passes, the multisig signers execute the result on-chain. This is fast and flexible but introduces a trust assumption: the signers could theoretically refuse to execute a passed proposal, or worse, execute something the community did not approve.

SafeSnap is the solution to this trust problem. Developed by Gnosis Guild (the team behind Zodiac), SafeSnap is a smart contract module installed on a Gnosis Safe that lets it execute transactions only if a corresponding Snapshot proposal has passed. The flow works like this: a Snapshot proposal includes an array of SafeSnap transactions encoded in the proposal body. When the proposal passes, anyone can submit those transactions to a Reality.eth oracle, which verifies the Snapshot result and posts it on-chain. After a challenge period (usually 24 to 48 hours, during which anyone can dispute the result by posting a bond), the transactions become executable through the Safe.

This architecture combines the gas efficiency of off-chain voting with the trustlessness of on-chain execution. The DAO never relies on multisig signers to honor results, because the smart contract enforces execution automatically. SafeSnap is used by ENS DAO, GnosisDAO, and several other large DAOs that want zero-trust execution. For DAOs that are comfortable with multisig execution, SafeSnap remains an optional upgrade rather than a requirement.

Top 10 DAOs Using Snapshot

Almost every DAO you have heard of uses Snapshot for either primary governance or signaling votes that feed into on-chain execution. Here are ten of the most important examples, each running thousands of proposals and millions of votes through Snapshot.

The breadth of this list shows why Snapshot is effectively governance infrastructure. From DEX aggregators to lending protocols to stablecoin issuers like MakerDAO, every major project that has ever tokenized its decision-making process eventually ends up running its day-to-day governance on Snapshot, even when on-chain Governor contracts handle final execution.

Governance Platform Comparison

Snapshot is not the only governance platform in crypto. The space has matured to support multiple frameworks, each with different tradeoffs around trust, gas costs, and feature depth. Here is how the five most common platforms compare.

Snapshot vs Tally: The Main Comparison

The most common question new DAO founders ask is: should we use Snapshot or Tally? They are often treated as competitors but they actually solve different problems and many DAOs use both.

Tally is a user interface for OpenZeppelin's Governor contracts. It is fully on-chain, meaning every vote is an Ethereum transaction. The benefit is that votes directly trigger execution without any trust assumptions or multisigs. The cost is gas: voting through Tally requires paying for the transaction, which depending on network conditions ranges from a few cents on Layer 2 to tens of dollars on mainnet. Tally is the right choice when execution must be trustless and the cost of voting is not a deterrent.

Snapshot is off-chain. Voting is free and instantaneous. But execution requires a separate mechanism, either a multisig or SafeSnap. Snapshot is the right choice when you want broad participation (because gas costs would suppress turnout) or when most of your decisions are signaling rather than direct execution. In practice, many large DAOs like Uniswap and Aave use Snapshot for early-stage temperature checks (a "temp check" or signaling vote) and then move to Tally or their on-chain Governor for the binding execution vote.

This two-stage flow is now considered best practice. It uses Snapshot's gas efficiency to get broad community feedback, then uses on-chain governance for binding decisions where the cost is justified by the magnitude of the action. For example, a $50 million treasury allocation would warrant the gas cost of on-chain voting because the stakes are too high to rely on multisig execution. A small grants approval can stay entirely on Snapshot because the community-elected grants committee can execute it via multisig.

Hands-On: How to Create a Proposal Step-by-Step

Creating a proposal on Snapshot is surprisingly easy. Here is the exact flow you would follow today. You need a wallet that holds enough governance tokens to meet the DAO's proposal threshold (varies by DAO; Uniswap requires 2.5 million UNI delegated to the proposer, while smaller DAOs might require just 1 token).

Step 1: Connect your wallet at snapshot.org. Visit snapshot.org, click "Connect wallet" in the top right, and approve the connection from your wallet of choice (MetaMask, Rabby, Frame, WalletConnect, etc.). You do not need any ETH for gas because nothing is going on-chain.

Step 2: Find your DAO's space. Each DAO has a "space" on Snapshot, like uniswap.eth, ens.eth, or aave.eth. Search for the DAO by name. If the DAO does not have a space yet and you are the founder, you can create one by registering an ENS domain and pointing it to a Snapshot space configuration.

Step 3: Click "New proposal." The proposal editor opens. You will need to fill in the title, the body (in markdown), the choices (yes/no, multiple choice, or weighted), the voting system (single-choice, approval, ranked-choice, quadratic, weighted), the start and end dates, and the snapshot block.

Step 4: Write the proposal body. Good proposals follow a standard structure: a Summary section, a Motivation explaining why this is needed, a Specification describing exactly what should happen, and a Voting Options section explaining the choices. Most successful DAO proposals follow this template, and many DAOs require it.

Step 5: Set the snapshot block. Most DAOs let Snapshot automatically pick the snapshot block as the current block at proposal creation time. You can override this if you want a slightly earlier block (sometimes done to give the community advance notice). The snapshot block is the moment that determines voting power, so picking it carefully matters.

Step 6: Sign and submit. Once everything is filled in, click "Publish." Your wallet will pop up asking you to sign a message (not send a transaction). Sign it and your proposal goes live immediately on the DAO's Snapshot page. From this moment, anyone who held qualifying tokens at the snapshot block can vote until the end date.

Famous Governance Attacks in DAO History

Governance is only as secure as its weakest link. Snapshot's snapshot-block mechanic prevents flash loan attacks, but governance is still vulnerable to vote-buying, low-turnout exploits, and outright treasury captures. Studying past attacks is the best way to understand the risks.

Beanstalk (April 2022). The classic flash-loan governance attack. The attacker borrowed $1 billion in various stablecoins from Aave and other lenders, used the borrowed assets to deposit into Beanstalk and acquire enough Stalk and Seeds (Beanstalk's governance tokens) to pass an "emergency governance" proposal that transferred the entire $182 million treasury to the attacker's address. Beanstalk used current-block balance checking instead of a snapshot block, which allowed the entire attack to happen in one transaction. This single event is the textbook reason every DAO since uses Snapshot or a snapshot-style mechanism.

Build Finance DAO (February 2022). A governance takeover that did not require any technical exploit. The DAO had low participation and the attacker simply accumulated enough governance tokens on the open market to pass a proposal that handed them total control. They then minted unlimited new tokens, drained the treasury, and dumped everything on Uniswap. Loss: about $470,000. The takeaway here is that low-quorum DAOs are vulnerable even without flash loans, simply because there are not enough engaged voters to block hostile proposals.

Mango Markets (October 2022). An attacker used $5 million to manipulate the price of MNGO tokens, used the inflated value as collateral to drain $114 million from Mango Markets' pools, then used the stolen MNGO governance tokens to vote on a "no-prosecution" proposal that would have let them keep $47 million in exchange for returning the rest. The proposal passed because the attacker held the majority of MNGO. This was not a smart contract bug. It was a governance failure where the attacker literally voted to forgive their own crime.

Tornado Cash (May 2023). An attacker tricked governance into upgrading a malicious proposal disguised as a routine change. The proposal contained hidden code that gave the attacker control of the governance contract itself. They then withdrew 482,000 TORN tokens from the lockup contract and dumped them. The attacker eventually returned the funds, but the precedent was alarming: malicious code can hide inside proposal payloads, and most voters do not actually read the smart contract bytecode they are approving.

Risks: Vote Buying, Low Quorum, Dictator Threshold

Even with Snapshot's strong technical defenses, DAO governance has structural risks that no platform can solve on its own. Understanding these risks is essential before participating in or building a DAO.

Vote buying. Platforms like Hidden Hand and Votium let users sell their voting power to the highest bidder. This is most pronounced in Curve and Balancer ecosystems where gauge votes determine token emissions. While vote-buying markets are technically transparent and consensual, they shift governance from "who cares about the protocol" to "who can pay the most this week." The long-term consequences of this dynamic are still being debated, and some DAOs have explicitly banned vote-buying markets in their constitution.

Low quorum. Most DAOs require a minimum percentage of token supply to participate for a vote to be valid. This is called quorum. Many DAOs set quorum at 4-10% of supply, which sounds reasonable but in practice is often barely met. When quorum is barely met, a coordinated small group of holders can sway any vote because they make up most of the actual participants. Worse, very low quorum means tiny groups can pass proposals that the broader community would reject if they were paying attention.

Dictator threshold. Many DAOs have a single wallet (often a Foundation, dev team, or VC investor) that holds enough tokens to single-handedly pass or block any proposal. This is sometimes a feature (the team wants to retain emergency control during early stages) and sometimes a bug (the token launch left a single entity with too much power). Either way, it means governance is theatrical. A DAO with a dictator threshold is not really decentralized, regardless of how it markets itself.

Voter apathy. The deepest risk is simply that most token holders do not vote. Across the top 50 DAOs, average voter participation is typically below 10% of circulating supply. The remaining 90% either delegate to someone else, hold tokens without engaging, or have lost access to the wallets they used during token launch. This concentrates real governance power in a tiny minority of engaged participants, who in turn often coordinate informally outside of Snapshot in Discord, Telegram, or governance forums.

The Future: ZK Voting, AI-Assisted Governance

Snapshot is not standing still. Several major upgrades are either live or in development that will shape DAO governance over the next few years.

Private voting with zero-knowledge proofs. Snapshot has integrated with Shutter Network to support sealed-bid voting where individual ballots are encrypted until the voting period ends. This prevents last-minute swing voting where a whale waits to see the tally and then casts a decisive vote in the closing minutes. With ZK voting, no one (not even Snapshot) can see how a wallet voted until the period closes, which encourages voters to commit to their actual preference instead of strategically gaming the order. ZK voting is gradually rolling out to more spaces and could become the default for high-stakes votes by 2027.

AI-assisted governance. Several DAOs are experimenting with AI agents that summarize proposals, simulate execution outcomes, and flag potentially malicious code in proposal payloads. The idea is to combat voter fatigue and the "I do not actually read the code I am approving" problem that led to the Tornado Cash attack. AI summaries can also translate technical proposals into language that non-developer token holders can actually evaluate. Some DAOs are even building autonomous delegates that vote according to a published policy without human intervention.

Cross-DAO coordination. Snapshot is building infrastructure for DAOs to interact with each other, including cross-DAO proposals where multiple DAOs vote together on shared decisions. This matters for ecosystem-wide coordination, like aligning gauge weights across Curve and Balancer, or coordinating treasury swaps between aligned DAOs.

Better delegation markets. Tools like Karma, Boardroom, and Tally already track delegate performance, but the next generation will let token holders algorithmically delegate to whichever delegate's voting history best matches their preferences. This is similar to how Curve gauge voting markets emerged, but applied to general-purpose DAO governance.

Pros and Cons of Snapshot

Frequently Asked Questions

Is Snapshot voting legally binding?

Legally, no. Snapshot votes are not contracts in the traditional legal sense. However, they are cryptographically binding in that the result is publicly verifiable and trusted by the community. Many DAOs have wrapped their Snapshot governance in legal entities (BVI foundations, Cayman foundations, Swiss associations) so that the off-chain consensus carries real-world legal weight. The Snapshot vote itself is informal; the legal framework around it is what makes execution enforceable.

Can someone hack a Snapshot vote?

The signature mechanism itself is cryptographically secure. To forge a vote, an attacker would need the private key of the voting wallet, which is the same as having access to the actual funds. Snapshot's infrastructure could in theory be compromised at the IPFS layer or the frontend layer, but the signatures are independently verifiable on-chain by anyone with the proposal data. The bigger risk is governance attacks (vote buying, low quorum exploits) rather than the voting mechanism itself.

Do I need to hold tokens at the snapshot block or now?

At the snapshot block. This is the critical detail. Even if you buy 1 million UNI tokens today, you cannot vote on a proposal whose snapshot block was last week because you did not hold tokens then. Conversely, if you held tokens at the snapshot block but sold them before voting, you still have voting power because your historical balance is what counts. This is also why some users practice "snapshot sniping" by buying tokens just before a known proposal goes live.

What happens if I lose my wallet between voting and execution?

Nothing changes for the vote itself. Your signed vote is already permanent on IPFS and cannot be revoked. The only impact is that you would not be able to participate in future votes. If you held tokens at the snapshot block for an active proposal and then lost wallet access, your existing vote remains valid. This is one of the small but important advantages of signature-based voting over transaction-based voting.

Can I delegate my voting power on Snapshot?

Yes. Snapshot supports delegation through a dedicated delegate registry contract. You sign a message (gas-free) that delegates your voting power to another address. From that point forward, the delegate's votes count for both their tokens and yours. You can revoke delegation at any time with another signed message. Many DAOs publish curated lists of active delegates with their voting history, so passive holders can choose someone whose views align with theirs.

Is Snapshot fully decentralized?

Mostly, but not entirely. The smart contract pieces (delegation registry, SafeSnap) are fully decentralized. The Snapshot frontend, indexer, and IPFS pinning service are operated by Snapshot Labs and could theoretically be censored or shut down. However, the underlying signatures and IPFS data would survive even if Snapshot.org went offline tomorrow. Anyone could spin up a replacement frontend and the votes would still be verifiable. So Snapshot is decentralized in the sense that matters (vote authenticity and persistence) but not in the sense that no single entity could disable the service.

Conclusion

Snapshot transformed DAO governance from a wealthy-only activity into something any token holder can participate in. By moving voting off-chain to signed messages stored on IPFS, it removed the gas-fee barrier that had silenced most retail holders during the on-chain governance era. By introducing the snapshot block, it shut down flash-loan vote-buying as a viable attack vector. By supporting 500+ voting strategies including quadratic, conviction, ve-token, NFT, and multichain, it became the universal governance layer for almost every meaningful DAO in crypto.

The platform is not perfect. Off-chain voting still requires either trusted multisig execution or SafeSnap to bridge into on-chain actions. Governance attacks beyond flash loans (vote buying, low quorum, dictator thresholds, voter apathy) remain unsolved structural problems that no platform alone can fix. And the Snapshot frontend, while open source and forkable, is still operated by a single team that could theoretically be pressured or compromised.

Despite these limitations, Snapshot is the closest thing crypto has to a universal voting standard. If you hold any governance token, you should know your way around Snapshot, find your DAO's space, understand its voting strategy, and actually cast your votes. If you are building a DAO, Snapshot is almost certainly your first stop for governance infrastructure. And as ZK voting, AI-assisted summaries, and cross-DAO coordination roll out over the next few years, the platform will keep expanding what is possible in decentralized decision-making. For more context on the tokens powering all of this, our guides to tokenomics and Aave's governance model are good next reads.

Related Guides

• How Do DAOs Work? Governance, Treasury and Voting Explained (2026)
• Governance Quorum vs Whale Voting: How DAO Control Risk Affects Tokenholders
• TRON Super Representatives: How Voting and Governance Work (2026)
• What Is Vana Protocol Data Sovereignty Dao Token Guide 2026
• What Is a DAO: Complete Guide to Decentralized Autonomous Organizations (2026)