DAO Platform

Snapshot Review

snapshot.org8.7/10February 24, 2026

Gasless, off-chain DAO voting review of Snapshot.org, covering features, ENS setup, IPFS-based auditability, fees, security model, and alternatives.

Snapshot screenshot
Snapshot screenshot

Background and history

Snapshot (snapshot.org) is an open-source governance voting platform designed for DAOs and other tokenized communities. Its central premise is straightforward: let communities create proposals and vote without requiring every voter to submit an on-chain transaction and pay gas. Snapshot describes itself as an off-chain, gasless governance client whose results are designed to be “easy to verify and hard to contest,” using signed messages as the voting primitive. [1]

The IPFS case study provides a clear origin story. Snapshot was originally built by Fabien, identified as Founder and CEO of Snapshot Labs, while working at Balancer. The initial goal was to support flexible governance for BAL held inside Balancer pools, where on-chain computation was too heavy. Moving voting off-chain, and persisting the resulting data on IPFS, provided the flexibility needed. In this telling, gasless voting was not the initial target but became a beneficial side-effect of the architecture. The implementation was then generalized and open-sourced, and it saw early adoption by DeFi projects including Yam and Yearn. [2]

Snapshot’s adoption is also visible from its own interface and ecosystem usage. The v1 directory page presents Snapshot as “where decisions get made,” and shows a very large list of governance “spaces,” which are community-specific hubs for proposals and voting. At the time of the captured interface, the directory displayed 72K spaces. [3]

A more operationally grounded endorsement comes from Harmony’s public decision to migrate from a self-hosted fork to Snapshot.org. Harmony states it originally forked Snapshot at the beginning of 2021 because Harmony was not yet implemented as a network option on Snapshot.org. Over time, maintaining a fork became burdensome. The fork became “extremely outdated,” lacked admin features, and Harmony experienced downtimes and bugs. Harmony ultimately sunset its forked instance on February 28, 2022, disabled new spaces and proposals from March 1, 2022, and kept the old spaces archived until May 1, 2022. [4]

Key features and services

Spaces, proposals, and votes

Snapshot’s product model is organized around three core objects: spaces, proposals, and votes. A space is effectively an organization’s governance homepage, proposals are items to be voted on, and votes are user-submitted responses under the rules defined by the space. Snapshot’s documentation emphasizes configurability, which is the primary reason it is often chosen as a governance “front end” across DeFi, NFT communities, and broader DAOs. [1]

Gasless, off-chain voting via signed messages

Snapshot’s most important feature is the off-chain voting flow. Instead of broadcasting an on-chain transaction to register a vote, a user signs a message with their wallet. This keeps the voting experience lightweight and avoids gas fees for voters, while aiming to preserve verifiability through cryptographic signatures. Snapshot’s documentation highlights signed messages as “easily verifiable,” and the IPFS case study explains that votes are persisted to IPFS rather than being stored on-chain. [1] [2]

Voting strategies and validations

A core reason Snapshot is widely used is the strategy system. Spaces can compute voting power using single or combined strategies, supporting designs based on ERC-20 balances, NFTs such as ERC-721 and ERC-1155, and other contract-driven approaches. Snapshot also supports proposal and voting validation rules, which can define who is allowed to create proposals and who is allowed to vote, such as requiring a minimum token balance. [1]
The IPFS case study provides concrete examples of how these rules can be applied in practice. It mentions an ENS-related governance configuration where users must hold the ENS token to vote and must hold at least 10k ENS tokens to create proposals. It also describes a Decrypt Media space where NFT holders vote and voting power depends on the number of NFTs held at a specified block number (example block: 12,811,388). [2]

Multiple voting systems

Snapshot supports multiple voting systems, which allows communities to tailor decision-making to their governance culture. Snapshot documentation explicitly mentions single choice, approval voting, quadratic voting, and more. The IPFS case study also lists weighted voting among supported types. This flexibility is one reason Snapshot is often used across different community sizes and governance maturity levels. [1] [2]

ENS-based space creation and IPFS-hosted configuration

Snapshot’s approach to identity and configuration is a defining design choice. Both Snapshot’s docs and the IPFS case study state that an ENS domain is the requirement to create a space. The IPFS case study goes deeper: a space is created by adding an ENS text record with the key snapshot that points to an IPFS CID containing the space’s JSON configuration. The case study cites GnosisDAO as an example of this mechanism in practice. [1] [2]

This architecture is frequently seen as a governance-positive tradeoff. It makes space configuration portable and content-addressed, but it also introduces a practical onboarding step. Communities that do not yet have an ENS name must acquire one first.

Plugins, custom domains, and admin ergonomics

From an operator’s perspective, Snapshot is not only about vote casting. Administration, configuration, and extensibility often determine whether governance tooling is sustainable.

Harmony’s migration post provides useful, experience-based color here. Harmony describes Snapshot.org as a “reliable product” and highlights that space owners get full control to edit spaces when they want, without requiring pull requests. It also calls out support for predefined and custom strategies, custom domains, and plugins. [4]

Security and trust

Verifiability via signatures, and auditability via IPFS

Snapshot’s security story is anchored in verifiability rather than on-chain enforcement. Votes are signed messages, and Snapshot positions results as easy to verify because the signatures can be checked independently. [1]
The IPFS case study adds an additional trust component: transparency and auditability through content addressing. Snapshot uses IPFS as its main storage layer for proposals and votes, and the case study notes that votes (as signatures) are persisted to IPFS rather than on-chain. This enables third parties to view, audit, and replicate the content identified by specific CIDs. The case study includes a statement attributed to Fabien that frames IPFS as a standard for verifiable and transparent data storage for auditable governance systems. [2]

Snapshot block numbers and balance integrity

A common challenge in token-based governance is last-minute balance shifting. Snapshot addresses this through a proposal-level snapshot block number, which serves as the balance reference for voting power. The IPFS case study explicitly describes this as a mechanism intended to prevent manipulation such as temporarily acquiring tokens after a proposal is created to influence the outcome. [2]

Important limitation: off-chain voting is typically non-binding

Snapshot is best understood as a “signal voting” layer. While results can be verifiable and auditable, they generally do not execute on-chain state changes by themselves. This can be a strength because it keeps participation friction low, but it also means governance processes often require an additional execution step, whether on-chain governance modules, multisig execution, or social coordination.

The provided sources frame Snapshot as a tool to “run and manage” organizations and conduct elections and proposal votes, but they do not claim that Snapshot itself provides automatic on-chain execution. Harmony’s usage description is consistent with Snapshot acting as a key coordination venue for DAOs. [4]

User experience

Wallet-based flow and discoverability

Snapshot is wallet-first. The v1 interface prominently features a “Connect wallet” entry point and an explore directory of spaces. This is aligned with how most Web3 governance communities operate, where token ownership and wallet signatures are the foundational identity mechanism. [3]

The explore view also gives a sense of the range of communities using Snapshot. Examples shown in the directory include large communities like Decentraland (35K members), The Sandbox DAO (14K), and Magic Square (96K), alongside much smaller spaces with tens of members or fewer. This distribution matters because it suggests Snapshot’s UI pattern can work for both early-stage collectives and mature ecosystems with large voter bases. [3]

v1 vs v2 interface transitions

Snapshot’s v1 interface includes prompts to switch to a newer interface and links indicating a v2 experience. From a product maturity standpoint, this suggests ongoing iteration. From a user standpoint, it can also introduce mild fragmentation if different communities link to different interface generations. [3]

Admin experience and self-service configuration

Harmony’s migration perspective is valuable because it reflects real operational pain points. Harmony explicitly criticized its fork for being outdated, lacking admin features, and requiring manual, slow updates with a human bottleneck. In contrast, Harmony praised Snapshot.org for allowing space owners to edit spaces anytime, avoiding pull request workflows, and gaining access to strategies, plugins, and custom domain support. For DAOs that expect governance parameters to evolve, these admin ergonomics can be decisive. [4]

Pricing and fees

Snapshot usage is commonly described as free, particularly from the perspective of running proposals and collecting votes without gas costs for participants. Harmony explicitly stated that “the service is free to use,” while also noting an important practical nuance: new spaces may need to use or purchase an ENS name using ETH as a one-time expense. [4]

From a budgeting standpoint, the cost center is less “Snapshot fees” and more “governance setup overhead,” including ENS acquisition and any operational work required to configure strategies, validations, and community processes.

Adoption and scale

Snapshot’s usage metrics, as reported in the IPFS case study, are among the strongest indicators of product-market fit in Web3 governance tooling. The case study reports:

  • 7M CIDs
  • 5M votes cast
  • more than 9K projects and DAOs on Snapshot (cited as over 9,645 projects)
  • 63K proposals created

It also names example users including Gitcoin, Ethereum Name System (ENS), Aave, Uniswap, and Sushi. [2]

Separately, Snapshot’s own v1 directory view shows 72K spaces listed, which is consistent with broad adoption across many smaller or experimental governance spaces, even if not all are equally active. [3]

Third-party technology tracking can show different numbers depending on methodology. For example, Sumble’s tech page claims 380 organizations “using Snapshot” within its dataset, which likely reflects mentions rather than total platform activity. This discrepancy is not necessarily a contradiction, but it is a reminder to interpret third-party “usage” numbers based on how they are collected. [5]

Comparison with alternatives

Snapshot sits in a crowded governance tooling landscape, but its core niche is off-chain, gasless signaling paired with flexible voting power strategies. Alternatives often differ along two axes: whether governance is primarily on-chain, and whether the tool extends into broader DAO operations such as treasury management, member onboarding, or funding.

Tally

Alchemy lists Tally as an alternative and describes it as an “all-in-one tool that helps DAOs govern better.” For teams that want a more integrated governance cockpit, particularly around proposal lifecycle and on-chain governance visibility, Tally is frequently evaluated alongside Snapshot. [6]

Aragon

Aragon is framed by Alchemy as a platform that “enhances on-chain governance.” If your governance model requires binding execution and on-chain enforcement, Aragon-style on-chain systems can be a better fit, at the cost of higher complexity and, depending on design, more on-chain transactions. [6]

DAOhaus, Colony, and DAOstack

These tools, also listed by Alchemy, skew toward broader DAO creation and management. DAOhaus focuses on creating and managing a DAO and distributing a shared treasury. Colony and DAOstack are presented as no-code DAO toolkits and governance protocol libraries and interfaces, respectively. They may be chosen when a team wants a more opinionated structure around roles, permissions, and treasury workflows, rather than a standalone voting venue. [6]

Commonwealth

Commonwealth is described by Alchemy as a platform for on-chain communities to discuss, vote, and fund projects together. Compared with Snapshot’s voting-first orientation, Commonwealth can be evaluated when discussion, community engagement, and funding workflows are first-class requirements. [6]

Ink Finance and broader “governance plus finance” platforms

CB Insights lists Ink Finance as Snapshot’s top competitor, describing it as governance and asset management tooling for DeFi, including “compliant financial ecosystems.” This category is relevant if a DAO is optimizing for operational finance and compliance-oriented controls as much as for voting UX. CB Insights also lists Syndicate as a comparator providing Web3 APIs and infrastructure, though it is broader than governance alone. [7]

How to choose

Snapshot tends to be a strong choice when:

  • You want high participation with minimal friction (no gas for voting).
  • You need flexible voting power computation and multiple voting types.
  • You value transparent, auditable governance records stored on IPFS.

A more on-chain governance platform may be preferable when your priority is binding execution and direct protocol-level enforcement rather than signaling.

Final verdict

Snapshot is a mature, widely adopted governance voting platform that has become core infrastructure for a large portion of the Web3 ecosystem. Its off-chain signed-message model and IPFS-backed storage offer a compelling combination of low-friction participation and verifiability, and its strategy system enables governance designs that range from simple token-weighted votes to more complex token and NFT based schemes. [1] [2]

Operational evidence supports its value. Harmony’s migration post highlights concrete reasons a major ecosystem preferred Snapshot.org over maintaining a fork: outdated code, missing admin features, manual configuration bottlenecks, and reliability issues, contrasted with Snapshot.org’s self-serve administration, plugins, strategies, and custom domain capabilities. [4]

The platform is not without tradeoffs. It is typically “signal voting,” so communities need a clear execution layer and governance process around it. There is also a practical barrier to entry in the ENS requirement for creating spaces, plus real-world migration friction for teams coming from forks or legacy instances. [2] [4]

For most DAOs that want a proven, configurable, and cost-efficient voting layer with broad community familiarity, Snapshot remains one of the strongest default choices in the market, especially when paired with a well-defined path from off-chain consensus to real execution.

Frequently Asked Questions