NFTs are a type of token that represents something unique or indivisible.

Unlike ERC-20 tokens, NFTs are non-interchangeable, meaning each token has its own distinct value and properties. NFTs are designed to represent ownership or proof of authenticity for a specific digital or physical asset. These assets can include digital art, collectibles, virtual real estate, in-game items, and more.

So, can you give someone Voting Power if they hold an NFT from your collection?

Sure thing, read on!

Snapshot Pro plan is designed specifically for spaces seeking advanced governance tools. By upgrading to Pro, you gain access to a powerful set of features that streamline proposal creation, voting, and oversight, letting you focus on what really matters: effective, transparent governance.

Learn more: https://snapshot.box/#/pro

What is Snapshot?

Snapshot is a voting platform that allows DAOs, DeFi protocols, or NFT communities to vote easily and without gas fees.The tool allows high customization of the voting process to cater to the diverse needs of the users and organizations. Customization includes different aspects like calculation of the users' voting power, selection of the voting mechanism, proposal and vote validation, and many more.In short, Snapshot is an off-chain gasless multi-governance client which results are easy to verify and hard to contest.

Key features

• Gasless: Create proposals and cast your votes without any gas fees.

• Flexible voting strategies: Customize how the voting power is calculated through single or combined strategies that enable voting with ERC20s, NFTs, other contracts, and more.

• Proposal and voting validation: Use custom logic to define who can create a proposal or cast a vote.

• Multiple voting systems:

How does it work?

Snapshot’s protocol involves three core elements: spaces, proposals, and votes. A space functions like an organization’s profile, and every proposal and vote is tied to that space. To create a space, the only requirement is to have an ENS domain. Once a space is set up, users can submit proposals and cast their votes on the space’s page. Administrators of the space can tailor the rules for creating proposals and voting by configuring various voting and validation strategies. For instance, a space might require users to hold a minimum of 500 tokens to create a proposal, or it might assign voting power proportionally to the token balance in a user’s wallet.

What are you looking for?

Organizations can create multiple spaces and link them together. This is useful for enforcing different space settings for proposal creation, voting, and execution. For example, instead of having to change the space settings each time you create a proposal, you could create additional spaces with some of your most frequently used settings.

Setup

You can define a main space, or multiple subspaces, in the Sub-spaces section of the space settings.

Do this for both your main space and all subspaces to link them to each other. If you have setup everything correctly they will be displayed on the space page.

Limits

• A space can add upto 16 sub-spaces

Space Hibernation is placing inactive or incorrectly configured spaces into hibernation mode. This process aims to enhance the user experience.

Space Controller and admins will see this warning message if space has gone into hibernation mode:

When does a Space hibernate?

A space will automatically enter hibernation mode if it meets any of the following conditions:

Verification for legitimacy

Space verification is a process of checking if the space is real and can be trusted.

Verified spaces have a special badge next to their name, as presented on the screenshot below.

What is a role?

Role is a set of permissions related to managing your space and its proposals which an account (wallet address) can be granted.

Role permissions

Controller

Controller of space has a full control over the space settings including managing the list of admins.

Admin

Admin can edit space settings with the exception of the list of admin users and archive proposals.

Moderator

Moderator can manage proposals within the Space and create new ones.

Author

Author can create proposals regardless of their voting power and the proposal validation strategy.

Assign a role to the user

Controller

The controller is first assigned during the process of space creation. By default, it is the ENS domain controller. To learn more about this step, head to .

There can be only one controller per space and can be updated only by the current controller.

To update the controller role head to the space settings on Snapshot and the Advanced tab. At the bottom of the page you'll find the Danger zone where you can change the controller:

Paste the address of the account you want to set as space controller in the pop-up window and click Set. It will trigger your wallet browser extension and ask you to sign a transaction with a gas fee.

Admins, moderators, and authors

To update the admins and authors lists head to the space settings on Snapshot and the Members tab.

You can add addresses one by one and choose their applicable role:

If you do not want to have the wallet control your settings, you can follow the steps below to create a space on Snapshot.

Drawbacks

• You will not be able to change settings from the UI

• Every time you want to change the settings, you will need to broadcast a new transaction

How to Create Space

• Create a JSON file for your settings on Snapshot. The format of the JSON file could be as follows:

• Store the JSON file on IPFS

• Use the IPFS link on the ENS text record. This will make the ENS owner the only controller of the settings.

• You can check if your space is valid from the GitHub link below

• Once the above transaction is successful, go to the below link to update the space in Snapshot:

  https://hub.snapshot.org/api/spaces/<ENS DOMAIN>/poke

By adding a custom domain to your space, you can whitelabel the Snapshot website and present your community with a fully branded governance experience. This feature allows you to display only your specific space at your custom URL and even customize colors to match your brand identity.

Examples

More than 400 DAOs already use custom domains for their governance, such as:

vote.balancer.fi vote.morpho.org vote.sushi.com

Requirements

To enable this whitelabel experience, you must subscribe to our . Once your subscription is active, follow the setup process below.

Setup steps

1. Add a CNAME record

Go to your DNS provider or registrar and create a new CNAME record.

• Host: your custom domain (for example, vote.myprotocol.xyz)

• Points to: cname-2.snapshot.box

2. Contact us

After you have created the CNAME record, let us know you’d like to enable whitelabel. Reach out to us through our , , or .

You can think of a space as an organization's account on Snapshot which can be viewed by anyone visiting the platform. It serves as a hub for all proposals related to the organization and a source of information for the users.

Moreover space allows its organization to manage the roles of organization members and customize the proposal and voting settings.

If you already have an ENS domain, feel free to skip this and follow the guide.

POAPs stands for Proof of Attendance Protocol. In simple terms, POAPs are like digital badges or tokens that you can earn for attending or participating in certain events, both in-person and online.

Let's say you attend a conference, workshop, or even a virtual event. The organizers of that event can create a unique digital token called a POAP. It serves as proof that someone was present or participated in that specific event. Each token has a unique code or ID that represents their attendance.

Delegate your voting power on Snapshot

1. Go to https://snapshot.org/#/delegate

2. Enter the address you want to delegate to.

3. To limit the delegation to a specific space, tap the on toggle button and enter the space key (example: balancer.eth) you want your delegation to take effect on. If no space is selected, the effect will take place for all spaces.

4. Click Confirm to save your delegation.

At Snapshot Labs, we want to help our users safely browse and discover spaces and make informed decisions about them. That’s why we’ve introduced verification and warning badges.

The goal is to provide users a simple way to navigate voting in web3. To facillitate that Snapshot displays a verification badge or warning label next to the space name and in each proposal belonging to that space.

The verification badge signifies that the space has been verified as the authentic version of the protocol it claims to be. Please note that the verified badge does not represent an endorsement of the protocol by Snapshot Labs. A verified badge also says nothing about its merits as an investment. A space may carry a verified badge but might still be a bad investment idea. Think of the verified badge only as a tool to help you find the correct version of the space you’re searching for.\

The warning badge means that we either identified that space as impersonating a project, IP infringement or potential scam.

What is a skin?

A skin is a custom color scheme which you can use for your space if it has a custom domain set up. The customization will be visible only on the custom domain and will not affect the color scheme of your space on https://snapshot.org.

Mana is a meta-transaction relayer that allows users to interact with Snapshot X without paying gas fee. This service works in conjunction with signature based Snapshot X . Users sign a meta transaction in the SX UI and then the relayer submits each encoded transaction along with its signature to the signature authenticator. If the signature is valid, then the transaction will be forwarded to the relevant space contract.

The system included a mechanism that allows DAOs to fund the transactions sent by the relayer, enabling the free end user experience. However importantly, users can directly interact with Snapshot X and therefore do not rely on trusting the relayer to not censor votes. Additionally, Anyone can run a relayer if they want to take over the sponsoring of transactions.

Note that currently Mana only supports proposal creation, proposal updates, and vote casting transactions. It does not currently support proposal execution or space controller actions.

GitHub

To enhance the user experience of interacting with the protocol, we offer a number of additional off-chain services. All of these products are fully open source in the . These are all completely optional and therefore do not introduce any censorship concerns.

• : An easy to use interface for interacting with the protocol.

• : A fast and efficient indexer for all the protocol data.

• :

The API indexes Snapshot X data. Specifically, it monitors events emitted by spaces and space factories so that votes, proposals, and the deployment of new spaces can be tracked. Anyone can run the API. It uses and support multiple chains.

GitHub

ERC-721 was the first standardized interface for creating and trading NFTs and is still considered the gold standard.

ADD SOME JOYFUL TEXT HERE

In Snapshot, the balanceOf method is applied to both the erc721 and erc20 strategies. The main difference in their implementation is that the decimal of an NFT should always be set to 0.

This strategy returns the balance of the specific ERC721 NFT that the user holds.

It's the most common strategy for NFT-based voting.

How to set it up? Just provide the contract address of the NFT and its symbol.

One who owned the specified NFT at the snapshot of proposal creation will be able to vote based on the number of NFTs they have in their wallet.

Strategy setup:

You can test it out in the Playground on Snapshot:

This strategy gives an arbitrary weight to the balance of the voters for a specific ERC721 NFT.

By adjusting the multiplier to 100, if a user owns 1 LAND in his wallet, he will get 100 votes (1*100) on the proposal.

Strategy setup:

You can test it out in the Playground on Snapshot:

Each NFT under the same contract address can be identified by its unique tokenID.

This strategy returns the balance of the voters for a specific ERC721 NFT with a given tokenID.

If a user holds the NFT which tokenID is included in the tokenIds parameter, they will get 1 vote regardless of how many they hold in total.

Strategy setup:

You can test it out in the Playground on Snapshot:

This strategy is a modification of .

It allows 1 vote per whitelisted tokenID specified in the parameter.

So in contrary to the previous strategy, the user who holds three NFTs, each included in the strategy setup, will have 3 Voting Power.

Strategy setup:

You can test it out in the Playground on Snapshot:

The strategy returns the weighted balance of the voters for ERC721 NFT of which the Token ID is specified in the tokenIdWeightRanges.

Why it might be useful for your space?

• NFTs in the collection have continuous tokenIDs

• You want to assign different weights to specific batches of the collection (higher VP for first NFT minters, lower VP for latest NFT owners)

The NFT can be assigned a different weight based on the range its token ID falls within.

For example, a user who owns 3 NFTs with the tokenIds: 1000, 6000 and 8000 respectively will have 3 Voting Power. [(1*2)+(1*1)+(1*0)]

Strategy setup:

You can test it out in the Playground on Snapshot:

How can users delegate their Voting Power?

Before we jump straight into the Voting Strategies setup, let's first understand how users can delegate their Voting Power to others through Snapshot.

<UPDATE FOR NEW DELEGATION UI>

Voting Strategies

In order to take the delegated Voting Power into account, your space has to use one of the delegation Voting Strategies.

In Snapshot, based on whether the delegated power can be taken back by the delegators when they vote, there are two main delegation strategies:

• with-delegation - the delegator cannot vote, only the delegate can participate in voting

• delegation - allows the delegator to vote despite having delegated their Voting Power

Let's have a look at both in detail:

This strategy is a combination of delegation + own Voting Power (if not delegated to anyone), moreover, it prevents the delegators from taking back their delegated VP.

By using this strategy, one can no longer vote if he delegated to another one, and the delegatee's voting power will be his own VP + delegated VP.

The sub-strategies are used to define the source of own VP and delegation.

Strategy setup

You can test it out in the Playground on Snapshot:

This strategy returns the delegated Voting Power only.

Now, what's the deal with both delegate and delegator casting a vote?

In the delegation strategy, if A delegates to B and both of them vote, then the delegated voting power is not calculated. Only the vote of A will be calculated.

The vote of B will be counted if A does not vote.

It can include a list of sub-strategies (erc20-..., erc1155-..., whitelist, etc) to calculate the user's Voting Power based on the delegation.

Strategy setup

The below example shows that the space allows YFI balance as the delegated voting power in yam.eth space.

You can test it out in the Playground on Snapshot:

Let's start with a quick overview of the ERC721 and ERC1155 standards:

Let's have a look at what Voting Strategies you can use in your space:

The strategy returns the balance of a specific ERC-1155 token in the user's wallet.

Since the ERC-1155 standard supports multiple token types, the tokenId here may refer to a particular kind of token or a single item of the collection under the contract address.

Strategy setup:

You can test it out in the Playground on Snapshot:

This strategy returns the balance of voters for all tokens in an ERC1155 contract.

Strategy setup:

You can test it out in the Playground on Snapshot:

Use this strategy if you want to calculate the Voting Power taking into account multiple tokenIDs.

Strategy setup:

You can test it out in the Playground on Snapshot:

The equivalent of the Voting Strategy.

By adjusting the multiplier to 5, if a user owns 1 DAWN in his wallet, they will get 5 Voting Power (1*5).

Strategy setup:

You can test it out in the Playground on Snapshot:

If you'd like to give more or less weight to a list of specific tokenIDs, you can do so by using this strategy. It might serve as a great addition to the for VP differentiation.

Strategy setup:

You can test it out in the Playground on Snapshot:

Who can vote on proposals?

There are several aspects that define if you are eligible to vote on a specific proposal.

Voting strategies

Each space specifies their in its settings. You can see the custom setup by opening the space settings. This setup can define if you are eligible to take part in the voting and what is your Voting Power calculated at the timestamp of proposal creation.

One of the most common questions we receive on our support channels is Why can't I vote?

More often than not the answer is - you did not hold the sufficient amount of specified token at the time of proposal creation.

Cast a vote

1. Connect your wallet

Click the Connect wallet button in the top right corner.

Connect with the wallet provider where you hold the tokens relevant for the space you want to vote in.

2. Find the proposal

Go to the space page on Snapshot. You can vote directly from this view or go to the proposal you are interested in to read more details before you vote.

In the proposal page you can see your Voting Power. If it shows 0 it means you cannot vote on the selected proposal. \

3. Vote!

Select the option you want to vote for - Accept, Reject, Abstain.

Depending on the space settings you will have to sign a gasless Ethereum message and/or sign a transaction to confirm your action.

You will notice that a new icon has appeared in the top right corner, just next to your avatar:

The number indicates the number of pending transactions. Once it disappeared you can reload to page to view your vote. Voilà! You have just cast a vote 🎉​

The UI is the official interface for Snapshot X.

GitHub

https://github.com/snapshot-labs/sx-monorepo/tree/master/apps/ui

UI

To add your own voting validation strategy on Snapshot you need to fork the score-api repository and create a pull request.

1. Navigate to the src\validations.

2. Create a copy of the basic strategy folder and rename it to the name of your voting validation.

3. Customize the logic of your voting validation.

If you are not sure about the Validation class, have a look at its definition:

The validation name has to be included in the in the validationClasses variable.

4. Test your validation

To make sure your validation passes all tests, run:

4. Make sure you pass the checklist

Have a look here on the requirements for adding a new validation strategy and make sure you fulfill the points in the checklist:

5. Create a pull request

The team will then review your PR and after it's approved and merged it will be available to choose in your space settings.

Authenticators are the contracts in charge of authenticating users to create proposals and cast votes.

All proposal creation, proposal update, and vote transactions must be sent to the relevant DAO's space contract via an authenticator.

DAOs are free to write their own custom authenticators that suit their own needs however we provide the following approaches:

Ethereum signature authenticator

Will authenticate a user based on a message signed by an Ethereum private key. Users create an EIP712 signature for the transaction which is checked for validity in this contract.

• v,r,s: ECDSA Signature

• salt : The salt used in the signature to prevention replays (only required for proposal creation and updating).

• target: The destination space contract.

• functionSelector: The function selector of the desired action.

• data: The ABI encoded transaction payload for the action. Refer to the section for more information on the payload contents.

This can work in conjunction with a meta transaction relayer to allow proposal creation or vote costs to be sponsored by the DAO, providing a free end user experience.

Ethereum transaction authenticator

Will authenticate a user by checking if the caller address corresponds to the author or voter address.

• target: The destination space contract.

• functionSelector: The function selector of the desired action.

• data: The ABI encoded transaction payload for the action. Refer to the section for more information on the payload contents.

And more!

Our modular approach here allows spaces to authenticate users via other authentication methods without any changes to the space contract.

1. Copy the address of your Safe execution

Head to your space settings and scroll down to the bottom of the page and click the Safe address on the right side of the screen.

A new tab will open on the Etherscan explorer.

Copy the address of the contract:

2. Open Safe dashboard of your Treasury account

Click the App tab in the sidebar to open the list of available Safe applications.

3. Select the Zodiac app

4. Add your Safe execution strategy contract

Click on Custom Module.

Paste the contract's address you copied in the first step in the Module Address field.

As a last step you will have to sign a transaction.

And that's it, your proposals can now be executed! 🎉

Snapshot has several bot integrations which can be set up for your organization in order to receive Snapshot specific notifications.

Have a look at the list below to see what is currently possible:

Snapshot Discord bot

For: Discord Status: Ready Install: Invite the Discord bot with this link: https://discord.com/oauth2/authorize?client_id=892847850780762122&permissions=83968&scope=bot

Type / to see the commands (require administrator role)

Need help? Contact our support on

Domino

For: Discord, Telegram, X, Email, Slack, Webhook, and many more custom automations Status: Ready Install:

propbot

For: X Status: Ready Install:

Boto

For: Telegram Status: Ready Install:

Snapshot uses webhooks to notify your application when an event happens. Webhooks are particularly useful for asynchronous events like when a proposal is created, when it starts, or when it ends.

The webhook server sends a request for any new event, the request is sent to the configured URL with POST method and the event object as body.

Here is an example of the event object:

Here are the possible events:

proposal/created When a new proposal is created

proposal/start When the voting period for a proposal starts.

What's special here?

Starknet having its own language (Cairo) and being a ZK Rollup, there are some Starknet specific details. The Snapshot X Starknet implementation allows DAOs to govern their L1 DAO trustlessly, with very little fees and no user friction. Indeed, users do not have to bridge their tokens, nor do they need to create and install a Starknet wallet.

This is all handled seamlessly by the Snapshot X protocol by taking advantage of the existing native bridge, some storage proofs, and a transaction relayer.

Snapshot X has completed a full audit with and .

Who can vote on proposals?

There are several aspects that define if you are eligible to vote on a specific proposal.

Plugin is an extension which enriches Snapshot by additional functionalities without changing the core of Snapshot's logic. The possibilities are many, from plugins which reward users with an NFT when they cast a vote, through adding a comment box for voters to explain their choice, to enabling on-chain execution of Gnosis Safe transactions.

You can browse through all plugins by heading to and selecting the Plugins filter in the search bar:

Add a plugin to your space

You can extend your space's functionality by adding plugin(s) to it. They will be applied to all proposals created after the plugin has been added.

Access your settings

Navigate to your space settings from the space menu by clicking on Settings.

Edit the controller of your space

Space controller is the main account that is able to manage the space settings and assign other addresses as admins of the space. By default it's set as the ENS Controller address however you can change it to another address.

To replace the current space controller by a new controller click the Edit controller button.

Edit your profile information

To complete your profile, you can upload an avatar/logo, enter a name for your DAO, a description, select up to 2 categories and other details. These settings can be changed at any time.

Social accounts

You can link your social media accounts to the space on Snapshot by typing in your account handle, i.e.

Sub-spaces

In order to connect the space with sub-spaces you need to set them up for both main- and the sub-space.

1. First create the sub-space as you would create a normal space. Once the sub-space is set up, type it's linked ENS domain name in the Sub-spaces input field. If everything went well, you will be able to click the + on the right.

2. Head to the sub-space settings and type in the linked ENS domain name of the voting in the correct input field.

Voting strategies

Specify how the voting power should be calculated by adding one or up to 8 strategies.

To learn more about what they are and how they work head to .

Admins and authors

In order to specify who can manage the space or create proposals, fill in the apropriate field with addresses for:

• Admins - able to edit the space settings and moderate proposals.

• Authors - able to create proposals without any constraints Make sure that members specified in authors field are allowed to submit a proposal.

Head to to learn more about each role.

Proposals

You can provide guidelines and a template which will be displayed during the proposal creation:

Proposal validation

To validate if someone can post a proposal or not you can use the basic validation by default which takes your voting power with space strategies and checks if you pass a defined threshold.

To learn what a validation is head to .

Voting

The voting delay is a value in time between the time of proposal creation and the moment when users are allowed to vote. The voting period is the duration that the proposal is active and votes can be cast. It is counted from the moment

Quorum is the amount of voting power collectively achieved by voters which is required for a proposal to pass.

Shielded Voting

You can enable Shielded Voting within your space if you want to enable partial privacy and reduce voter apathy. Shielded Voting designed by Shutter is enabling that by using threshold encryption. You can learn more about it in the

In short, Shielded Voting is a voting setting in which the voters choices are private during the voting period and get revealed when the proposal closes.

To enable it head to Voting tab and select Shutter within the Privacy setting.

Delegation

In the Delegation tab you can set a custom delegation contract to enable delegate discovery for your space:

Custom domain and skin

You can add a custom domain to your space by following the guide.

If you want to apply a different design (skin) to your space, you have to set a custom domain first. Head to to learn how to add a custom skin for your custom domain.

Treasuries

In order to link your organization's treasury to Snapshot you have to:

1. Choose the treasury network

2. Enter its Ethereum address

3. Fill in the name of that treasury.

It is possible to add multiple treasuries to one space.

Plugins

You can customize your space even further with various plugins which provide extra features. To learn more about the plugins head to section.

Save your settings

Make sure to click the Save button on top of the settings page to apply the changes to your space. Once you sign a message (gasless) in your wallet, changes will be applied!

What is a voting strategy?

Voting strategy is a set of conditions used to calculate user's voting power. Strategies enable Snapshot to calculate the final result of voting on a given proposal.

In technical terms a strategy is a JavaScript function that returns a score for a set of addresses.

Strategy/-ies are defined in the space settings in Voting strategies section. Each space can select from one up to eight voting strategies. The default strategy is erc20-balance-of - it calculates the balance of a predefined ERC20 token for each user.

Voting strategies can be used to create a score from on-chain data, the data however does not necessarily need to be monetary. As an example a strategy can calculate how many POAPs or specific NFTs a user owns.

You can browse through 400+ strategies by selecting the Strategies filter on the main page of . If you can't find a strategy that fulfills your needs you can create a new one. To learn more about creating custom voting strategies head to .

How to set up a strategy?

Majority of spaces on Snapshot is using a single strategy however if you need a more complex calculation, you can combine up to 8 strategies. They will be applied to all proposals created for your space (created after the update of the settings) and the voting power will be calculated cumulatively.

In order to set up a voting strategy head to your space settings and scroll down to Strategies section. You should see the below pop-up after clicking Add strategy and selecting a strategy from the list:

You will see that there is information that you need to provide in order to make the strategy work, for example the network where the token is deployed, its symbol and address of the token's contract.

Each strategy will require a different setup and you can read the full description and see the required parameters in the strategy's page, for example . You can find each strategy's details through using the search bar and Strategies filter.

Testing a voting strategy

Before you add the strategy to your space's settings we highly recommend to test it in the Playground in order to avoid any potential issues with the voting process.

You can access it from the strategy's detail page by clicking the Playground on the right-hand side:

Your browser will load a Playground page where you can test the custom setup for the chosen strategy. As you can see on the below screenshot you can set the required parameters and provide a list of addresses which in this case are or are not holding a the PUNK ERC721 token.

If everything is set up correctly you should see the calculated voting power for each address after clicking the ▶️ button:

In this section we will go over the actions that can be made by the Space Controller. Note that we use Open Zeppelin's OwnableUpgradable module to gate access to this functions, and therefore at the contract level we use the term owner instead of controller.

Cancel a proposal

A proposal can be cancelled as long as it has not already been executed.

• proposalId: The ID of the proposal

This can be used to prevent damage from malicious or broken proposals.

Update space settings

All Space settings can be updated using the updateSettings function:

A single entrypoint is used instead of separate ones for each value so that a single transaction can be used to update a large number of settings. This improves the UX while also preventing undesired behaviour that may arise if proposals are created half way though the settings update process.

If one does not want to update a certain value, then the following placeholder values can be used in the function call (arrays can just be left empty):

Upgrade implementation

A Space contract's implementation can be upgraded to a new version using the following methods:

• newImplementation: The address of the new space implementation.

• data: A encoded function call to initialize the new implementation.

Refer to for more information.

Manage ownership

The owner can be transferred to a new address or renounced entirely.

You can use a Gnosis Safe to vote, create a proposal or setup a space on Snapshot.

Connecting your Safe

To connect your Safe to Snapshot

1. Go to your Safe wallet like https://app.safe.global/apps/open?safe=<NETWORK>:<SAFE_ADDRESS>

2. Go to the Apps tab.

3. Search for Snapshot and click on it.

4. You should now see the Snapshot interface connected to your Safe wallet.

Signing with your Safe

There are two ways to sign with your Safe multi-sig wallet on Snapshot:

1. Synchronous signing (offchain) - you keep the confirmation modal open until all Safe signers confirm the transaction.

2. Asynchronous signing (onchain) - you can close the confirmation modal and the transaction will be created in your Safe transactions queue. The Safe signers can confirm it later.

For more information, refer to the .

Synchronous signing

By default, the first signer who is signing a message will have to keep the confirmation modal open until all other signers confirm the message.

This happens offchain and does not create a transaction in your Safe transactions queue. but in messages tab of your Safe. Other signers need to confirm the message in their Safe interface.

Asynchronous signing

If you'd like to enable asynchronous signing for all Safe's signers and not have to keep the modal open, you have to enable on-chain signatures in the Safe settings.\

1. Go to Safe Settings -> Safe Apps.

2. Enable Always use on-chain signatures

That's all 🎉 Signers can now sign even if you you close the confirmation modal.

It will create a pending transaction in your Safe transactions queue. This transaction must be confirmed by the Safe signers within 144 hours.

What's in this book?

What's Snapshot X?

Snapshot X is an on-chain voting protocol. Technically speaking, it's a set of modular smart-contracts that interact with each other to do all the book-keeping. The difference with the original is that Snapshot X is fully on-chain. What this means is:

• The protocol is censorship resistant: Anyone can cast a vote. The protocol runs without any reliance on offchain or centralized services which have the power to censor votes. [1]

• Voting power is computed on-chain: The voting logic is fully on-chain and auditable so you can be sure of the logic used to compute voting power and decide on the outcome of proposals.

• The execution is trustless: Proposal transactions are automatically executed following the passing of a proposal. Say you create a new proposal which, if it passes, will transfer 1ETH to vitalik.eth. If the proposal passes, the 1ETH will automatically get sent to vitalik.eth

If anything in these docs is unclear or you would like more detail, do not hesitate to reach out on .

[1] We note that there are in fact offchain services (eg the relayer Mana) built for use with Snapshot X, but these are not mandatory and therefore cannot lead to censorship.

​​What is a proposal?

Proposal is the key element of the voting system. It presents a change suggestion related to a specific organization and enables eligible users to cast their vote.

Voting power for each user is calculated on the basis of the voting strategies selected in the space settings.​

Each proposal has the same voting system which provides three choices: accept, reject, abstain.

Who can create a proposal?

Users who:

• authenticate themselves via Authenticators whitelisted by the space,

• and are eligible according to the Proposal validation strategy selected by the space.

Create a proposal

1. Open space settings.

Head to the space which you wish to create your proposal for.

Make sure the connected wallet is where you hold the tokens relevant to the specific space.

2. Click the New proposal icon

Click the new proposal icon in the top right corner:\

3. Provide proposal details

Provide the necessary details - title, description and discussion link if there is one.

4. Choose the execution strategy

Select the Execution strategy you would like to use:\

5. Specify transaction details

Define what should happen if the proposal passes by choosing one of the execution options:

A modal will open with the transaction details to fill in:\

6. Publish your proposal

Click Publish​ and authenticate yourself via your wallet. Depending on the you will have to sign a gasless Ethereum message and/or sign a transaction to confirm your action.

7. Give it a minute..

Wait for the transaction to succeed. You can see it's pending in the top right corner, just next to your avatar:\

Once the icon with the pending transaction disappears, you can reload the page to view your proposal.

And that's it! You have created a new proposal 🎉

Executing proposals

Once the proposal has reached a quorum and passed, anyone can execute the transactions specified for it by clicking the Execute transactions button:

Snapshot allows you to subscribe to an e-mail notification system which helps you to stay up to date with spaces you follow.

You can opt in to receive the following notifications:

• Weekly digest - summary of spaces' activity over the previous week

• New proposal - new proposals in spaces you follow

• Closed proposal - list of closed proposals with their results

How to subscribe to the e-mail notifications?

1. Connect your account

Connect your wallet to Snapshot by clicking the Connect wallet button in the top bar.

2. Open profile menu

Click on your account displayed in the top bar and select ✉️ Email notifications:

3. Subscribe with your e-mail address

Type your e-mail address and click Subscribe. You will be asked to sign a message in your wallet provider extension.

4. Confirm subscription

After signing the message and receiving the confirmation of a successful subscription head to your mailbox and verify your e-mail:

A new tab will open with a successful verification message.

5. Enjoy!

That's it! 🎉

Notifications are sent out every Monday on a weekly basis.

Manage subscriptions

You can easily opt-in and out of the available notifications.

Click on your profile name in the top bar and select Email notifications:

A new pop-up window will open where you can toggle the different options:

How to unsubscribe?

You can easily unsubscribe via the link in each weekly digest or proposal-related notification email.

Head to your inbox and find an email from the Snapshot subscription, apart from the initial verification message. Scroll down and find the Unsubscribe link.

You'll be redirected to a page informing you that you have successfully unsubscribed from the notifications.

SafeSnap enables trustless execution for your Snapshot governance on a Safe treasury using Reality.eth oracle.

How does it work?

SafeSnap plugin is an oracle based solution which works together with Safe and Snapshot in the following way:

• A Safe module, where anyone can create a new proposal: an array of multisend transaction payloads.

• Each proposal is a Reality.eth question asking if (1) the linked Snapshot proposal passed, (2) did the proposal include the payload, and (3) does the payload do what the proposal describes.

• If the proposal passes on Snapshot, then Reality.eth should resolve to the same outcome, and after a 24 hour cooldown period, the proposal’s transactions are executable by anyone.

• Reality uses an ERC-20 token (a given DAO’s governance token) for the bond. The minimum bond can be set by way of a proposal to the DAO.

• The UI is a Snapshot plugin, in which users can enter an array of tx-payloads to be executed sequentially by the Safe if the proposal passes. Once the proposal has passed, the Reality.eth question has resolved, and the 24 hour cooldown period is over, there is the option on the Snapshot interface to trigger each of the multisend transactions in the proposal.

Setup

Follow the official Zodiac guide on how to setup a SafeSnap for your project. I'm a non-dev operator (space controller or admin):

I'm a developer:

Security recommendations

In order to ensure maximal safety we recommend to define several paremeters for your setup:

• Set a substantial bond for an answer

• Select an arbitrator

• Select a long cooldown

• Set up a monitoring infrastructure

Additional resources

Learn more about SafeSnap here:

Proposal validation strategy is used to determine whether a particular author is allowed to create a proposal.

Each Space has to set a proposal validation strategy which consists of an address and a set of params that are stored in the space. These strategies should have the following interface:

• author: The author of the proposal.

• params: Parameter array set in the space contract that is the same for every user of the Strategy.

• userParams: Parameter array submitted by the author when they create a proposal, and can therefore be different for each user.

There is no requirement to use either of these parameter arrays in your strategy, in which case you can just pass an empty array.

DAOs are free to write their own custom strategies that suit their own needs however we provide the following approaches:

Proposition power

A strategy that validates an author to create a proposal if their propositionPower calculated from a set of Voting strategies exceeds a proposalThreshold value. It means that if the proposal threshold is set to 5, the author needs to have at least 5 Proposition power to create a proposal. This strategy uses the same logic as , so refer to that section for more information.

When calling this strategy, params should be:

userParams should contain the indexed strategies that the author has power with:

Active proposal limiter

A strategy that validates an author to create a proposal if the author has not exceeded a limit of maxActiveProposals.

Each time an author creates a proposal, a counter is incremented up to a limit of maxActiveProposals. After this point, no more proposals can be created until a cooldown period has elapsed since the most recent proposal they created.

Using this strategy can help to prevent proposal creation spam in your space.

And more!

These strategies can be combined and extended to provide flexible Proposal validation mechanisms. The interface for Proposal validation strategies can be found .

How do I receive notifications?

It's simpler than you think:

1. Join (follow) a Space you would like to receive notifications for

1. Click the Alert bell icon to turn the notifications on

1. Open and and log in with the account you used on Snapshot.

2. Start receiving notifications from chat.snapshot.eth!

Managing notifications

You can easily toggle, start, or stop notifications by sending a message in the chat app:

Lighthouse

connects you to all your Snapshot spaces and keeps you updated with push notifications whenever a proposal is created or ending soon. Read proposals and comments, and even vote without leaving the app. Everything is cryptographically verified, allowing you to focus on the content that matters.

If you own or manage a space, Lighthouse also enables you to securely communicate with your voters, analyze engagement, and more.

Galxe is building a protocol that powers on-chain credentials with plug-and-play NFT modules. The permissionless infrastructure allows everyone to create, distribute, and gamify NFTs with customized on-chain data.

With the Galxe plugin users can easily create a campaign and integrate it into Snapshot. This solution will incentivize communities to participate in the proposal vote by rewarding them with OATs (On-Chain Achievement Tokens). After users have voted, they can claim an OAT directly from the Project Galaxy Plugin section on the proposal page on Snapshot.

Setup

1. Go to your settings

In order to add a plugin head to your space settings by clicking Settings on your space's page:

2. Create a new proposal

Create a new proposal which you would like to link to the Galxe plugin. You don't need to specify anything related to Galxe yet.

Once the proposal is created, copy the proposal ID from the address bar in your browser as you will need it in the next step.

3. Add the plugin

2. Scroll down to the Plugins section and click Add plugin. Select the plugin you want to add in the pop-up window:

Add the proposal ID and the Galxe Campaign information which you would like to link with the proposal.

Make sure to replace <Proposal ID> with your proposal ID which you copied in the previous step.

Then replace the <Space Name/campaign/Campaign ID> with the details of your space and campaign.

Example:

If you have multiple proposals that distribute OATs to voters, you can also add multiple proposalID:campaignInfo pairs at once in the following format:

4. Confirm and save space settings

Click Add and scroll up to the top of the page to click Save to persist the updated settings.

That's it, your users will be able to see the Galxe plugin on the proposal's page!

Domino is a crypto notification system which makes it simple for DAOs to monitor and build automated workflows based on governance data. The Domino plugin allows you to alert space members about new and ended proposals on Snapshot.

Setup & how it works

1. Go to your space settings

In order to add a plugin head to your space settings by clicking Settings on your space's page:

2. Add the Domino plugin

Scroll down to the Plugins section and click Add plugin. Select the plugin you want to add in the pop-up window:

3. Save your settings

Scroll up to the top of the page and click Save to update your space's settings. The plugin will affect all the newly created proposals.

4. Create a proposal

Create a new proposal for your space. You don't need to set anything up for the Domino notifications, they will be enabled automatically.

5. Get notified

Users can now head to the proposal's page and click any automation to receive notifications about the proposal.

As a next step users will be redirected to Dominos's in order to set up their custom notification rules:

That's it! You're all set up and users can receive direct notifications about the Snapshot proposals 🎉

Head to the and follow the below steps:

1. Organization's details

Provide the profile information like name, description, social links or handles and treasury.

Execution Strategies have two key roles:

1. Determining the status of a proposal at any time,

2. Executing the payload of a proposal if it has been accepted.

Each proposal should have an Execution strategy set when it is created. This consists of a strategy contract address, along with an execution payload.

This page provides more details on the Execution strategies along with the implementations that we offer.

Voting strategies are the contracts used to determine the voting power (VP) of users. Voting strategies can be created in a permissionless way, however, to use one, one must whitelist the strategy in the space contract for your DAO.

The most common example is using the ERC-20 token balance of a user to determine their voting power. But you could imagine other voting strategies: owning a specific NFT, owning NFT of collection X and another NFT of collection Y, having participated in protocol XYZ... the possibilities are endless! We are fans of the , the concept of a governance system with arbitrary programmability. This will allow complex and expressive mechanisms of coordination to be seamlessly integrated into governance decisions.

Snapshot X reaches this standard, and we are excited to see what people build!

All voting strategies must have the following :

getVotingPower is called internally by the space contract when a vote is cast. timestamp is the snapshot at which voting power is calculated for all users. We use a timestamp rather than a block number to better enable multi-chain applications since a timestamp is universal to all chains.

“oSnap” is short for Optimistic Snapshot Execution. oSnap lets DAOs propose transactions, do an off-chain governance vote, and have the transaction data submitted in a trustless fashion.

How does it work?

Snapshot X's main contract is the Space contract. Proposals are created, votes are cast, and all of the proposal state is stored here. Beyond this however, the majority of the protocol functionality has been abstracted out of the Space contract.

These abstractions consist of:

• .

• .

• .

At the moment, Snapshot already supports calculating the Voting Power of the underlying token in the LP/staking contract from the most popular AMMs like Uniswap v2 and v3, Balancer, or SushiSwap.

This page only goes through popular strategies as projects may have a different method to call deposited balance in their contracts, which is often customized for a specific use case.

By enabling such a strategy in your space, you can allow the proposal to capture more users interested in your governance.

Some spaces allow only users holding tokens in liquidity/staking pools to have Voting Power.

The strategy fetches the balance of the input token address in all Uniswap-v2 liquidity pools.

This allows uni-v2 LP token holders to vote based on the underlying token cumulated in each pool.

Strategy setup:

You can test it out in the Playground on Snapshot:

Many platforms offer decent yields on one's Uniswap LP tokens.

By staking in their farms, users transfer their LP tokens to the contract they are interacting with (staking contract) and then can earn rewards from the farm they have joined.

The specific type of LP that can be farmed depends on the individual platforms.

The staked-uniswap strategy allows you to get token balance of an LP in a staking contract.

Strategy setup:

• tokenAddress: the underlying token you want to use to calculate Voting Power

• uniswapAddress: the Uniswap LP address where users can deposit their token

• stakingAddress: the staking contract address where users stake their LP token

You can test it out in the Playground on Snapshot:

In comparison with , Uniswap v3 provides users with the most flexibility and granular control over personal assets by introducing features like concentrated liquidity and multiple LP fee tiers per pair — 0.05%, 0.30%, and 1.00%.

In this context, the USDC / ETH LPs with 0.3% and 0.05% fees represent different contract addresses (poolAddress) respectively.

The demo illustrates how to get USDC balance in the USDC / ETH 0.3% liquidity pool. If you want to calculate the other token in the pool, you can change the paramtokenReserve to 1.

Strategy setup:

You can test it out in the Playground on Snapshot:

LP tokens provided in SushiSwap are called SLP tokens, and the SLP tokens can be staked into the farm (MasterChef LP Staking Pool) to earn rewards.

This strategy can return the balance of the underlying token in SushiSwap's LP pools and farms as well.

Strategy setup:

• address - the underlying token address

• useStakedBalances - if true it will also return the token balances from the MasterChef LP Staking Pool

• masterchefVersion - if v2 it will return the token balances from the MasterChef V2 staking contract instead of MasterChef V1.

You can test it out in the Playground on Snapshot:

The MasterChef contract has been developed by many projects based on SushiSwap’s original contract like . With MasterChef, users can stake their tokens and in exchange they will get a token reward.

The strategy is more generic and it gets the balance of the LP token or the underlying base token in the LP from a MasterChef staking pool.

Strategy setup:

• chefAddress: Masterchef contract address

• pid: masterchef pool id (starting with zero)

• uniPairAddress: address of a Uniswap pair (or a sushi pair or any other with the same interface)

You can test it out in the Playground on Snapshot:

A lot of use cases are beyond regular LP/staking scope, for example calculating the balance of staked NFT or from a custom contract.

The good news is, if there's a method in your contract that reads the balance of the staked token with a single call (interaction with the Smart Contract), you don't need to create a new strategy.

Instead, use contract-call strategy, which allows any contract method to be used to calculate voter scores.

Strategy setup:

You can test it out in the Playground on Snapshot:

How to delegate?

Snapshot enables a couple of ways to delegate your Voting Power to another address (a delegate).

You can delegate your Voting Power via:

👉 Delegates Registry per Space (if the Space has set up their custom delegation contract)

👉

👉

Let's look at each option in detail.

Delegates registry

It is possible to discover the Delegate registry of Spaces that provided their custom delegation contract in settings.

Head to the Space page and click Delegates in the left sidebar**:**

You will then see a list of delegates for the Space with the number of their delegators and their total Voting Power within the Space.

You can delegate your Voting Power to one of the delegates directly by clicking the Delegate button:

Delegate page

1. Go to

2. Enter the address you want to delegate to.

3. To limit the delegation to a specific space, tap the on switch button and enter the space key (example: balancer.eth) you want your delegation to take effect on. If no space is selected, the effect will take place for all spaces.

4. Click confirm to save your delegation.

Smart contract interaction

You need to call the setDelegate method with the space id as the first argument (space id is its ENS domain name, for example fabien.eth), and the address of the delegate as the second argument.

Here is an example of integration in a Solidity contract:

Supported networks

• Mainnet

• Sepolia

• Optimism

• Arbitrum

Delegation contract

Snapshot uses the Gnosis "Delegate Registry" contract here:

The contract is deployed on this address: The contract is also available on "Supported networks" listed above.

Delegations are stored on this subgraph:

POAP is a badge which can be acquired by attending events or experiences. In technical terms - a Proof Of Attendance Protocol NFT (non-fungible asset).

With the POAP plugin you can reward voters in your space with a unique POAP for each vote they cast on a Snapshot proposal and as a result grow the overall governance participation of your community.

Setup

1. Open your space settings on Snapshot

Ensure that you have the permissions required to add new plugins, or reach out to the admins of the space you'd like to add the plugin to.

Scroll down to Plugins and click the Add plugin button.

2. Select the POAP module

A new popup window will show up where you can search for and select the POAP Module by simply clicking on it.

No need for additional settings on this step; leave it as-is and click "Add."

Don't forget to save your settings! Go to the top of the page and click Save. Confirm the changes by signing the message in your wallet.

3. Create a new proposal

Now when you create a new proposal, the POAP plugin will be automatically added. There is no need to manually add it to each new proposal.

Once the proposal has been created, you can get your Snapshot proposal ID from the URL of the proposal. Copy all characters following the proposal/ in the address box in the browser and save them somewhere - you will need it to link the proposal to your POAP drop.

4. Create a POAP drop

Follow the instructions in POAP's guide but be sure to request "0" mint links.

Take note of your Drop ID, as you will need this for the next steps.

5. Link your proposal to your POAP drop

Reach out to the POAP team by filling out the required fields in the . Do not post your request anywhere else.

How to check the status of your request?

If you want to check on the status of your request, you should do so by using the chat bubble:

• Click the chat bubble in the lower-right corner of the .

• Type “check on my petition”

• Enter your drop ID.

• Get a response!

If curation needs to contact you, they will do so via the email [email protected]. If customer support needs to contact you, they will do so via the email [email protected]. Beware of scams and never reply to other email addresses.

Support

Join POAP Discord: Snapshot Help Center:

\

A Sybil attack is a type of attack on a computer in which an attacker subverts the service's reputation system by creating a large number of identities and uses them to gain a disproportionately large influence.\

source:

In the crypto world, attacks, hacks, and scams are unfortunately all too common. Phishing links can be found everywhere - on Twitter, in seemingly harmless blog posts, and in personal emails. We’ve not been immune to them either! As a popular tool for decentralized decision-making, is an attractive target for scammers looking to manipulate governance proposals for their own gain.

Before we jump into specific use cases, let's have a look at the most common configurations that the majority of spaces use on Snapshot.

Voting strategy + Proposal validation strategy

The minimum setup required to run your governance on Snapshot consists of:

We want to ensure that we limit the risk of API downtime and provide a reliable and continuous service. Therefore we decided to implement API Keys to ensure that the requests come from genuine users.

What is a proposal?

Proposal is the key element of the voting system. It presents a change suggestion related to a specific organization and enables eligible users to cast their vote.

A specific (single choice, weighted, quadratic, and others) can be selected individually for each proposal.

Voting power for each user is calculated on the basis of the voting strategies selected in the .

What is a whale?

A cryptocurrency whale, more commonly known as a "crypto whale" or just a "whale," is a cryptocurrency community term that refers to individuals or entities that hold large amounts of cryptocurrency. Whales own enough cryptocurrency to influence currency markets. https://www.investopedia.com/terms/b/bitcoin-whale.asp

Whales can influence not only currency markets but also the governance process of web3 communities. With the large holdings, their sheer Voting Power can oftentimes swing a proposal for their advantage. This leads to outcomes that are not welcomed by the community, poses a threat to taking the Treasury over, and also to lowering community participation in the vote as its members don't see the point in voting knowing that one wallet can decide on its outcome.

Let's have a look at different setups that will allow your space to minimize the power of whales.

Voting types

You can predefine the Voting type that all proposals in your space will use. In the case of the anti-whale approach, the best solution is the Quadratic Voting type.

1. Quadratic voting

Snapshot's Quadratic Voting (QV) type goes beyond the conventional approach of simply calculating the square root of each voter's voting power. It presents a more nuanced and democratic framework for decision-making.

One of the main features of our QV type is its emphasis on the number of individual voters rather than the size of their voting power. By doing so, it ensures that every voice counts, thereby enhancing collective decision-making and preventing power concentration.

Additionally, Snapshot's QV type provides voters with the flexibility to distribute their voting power across multiple choices. This feature allows for a more precise representation of a voter's diverse opinions, all without any additional cost.

Drawing key principles from the Quadratic Funding model, our QV type fosters greater participation and effectively balances influence. It represents a significant advancement over simpler voting mechanisms that rely on basic square root calculations of voting power.

You can set it up for all proposals in your Space by heading to the Voting tab in the Space settings and selecting the desired Voting System in the Type field: