Snapshot

Snapshot provides governance spaces where an organization sets proposal rules, voting power, and vote formats. Its standard interface records signed, gasless votes, while Snapshot X is a separate onchain option that can combine a proposal with an execution strategy.

Spaces define who can propose and vote

A space has a controller and member roles: admins can change settings and manage proposals, moderators can manage and create proposals, and authors can create proposals without passing the normal validation rule. The space can set a base network, proposal validation, voting delay, and voting period.

Voting strategies can measure ERC-20 balances, ERC20Votes delegation, ERC-721 or ERC-1155 ownership, whitelists, contract calls, external APIs, or ticket-style one-person voting. Several strategies can be combined, and they assess assets at proposal creation, so tokens acquired later do not add voting power to that proposal.

A signed vote is not a treasury transaction

In a standard Snapshot space, an eligible voter signs a message without sending an onchain transaction or moving assets. That removes per-vote network fees, but the result does not itself control a treasury or call a contract.

SafeSnap connects a Snapshot proposal to a Safe through a Safe module and a Reality.eth oracle question. After a proposal passes, the oracle resolves the linked question and the cooldown ends before its transaction payloads can be triggered. Oracle bonds, an arbitrator, and the cooldown shape that route from community vote to assets.

Snapshot X puts acceptance and action onchain

Snapshot X uses an execution strategy that decides whether a proposal passes and carries out its payload. A Safe-module strategy requires the space to be whitelisted and the connected Safe to authorize the module; a timelock strategy queues accepted transactions for its delay and can include a veto guardian.

Standard Snapshot is useful where a group needs flexible membership and vote calculations with low participation friction, but it needs an explicit connection when a decision must act on assets. Aragon takes the other architectural route: its DAO account, permissions, and installed plugins are the base for both treasury authority and voting.