Snapshot configuration & membership

Snapshot configuration

Strategies configuration for multi-stakeholder votingarrow-up-right

Strategies:arrow-up-right

We use three separate strategies so users can see in the UI what their voting weight is for each gov. group: Builders, Pods, and Token holders.

  1. MGV token with delegation and including vested, claimable tokens

  2. Builders Group Activity Score with delegation, quadratic-voting, and scaled to the circulating supply of MGV tokens

  3. Pods Group Activity Score with delegation, quadratic-voting, and scaled to the circulating supply of MGV tokens

Proposal configurationarrow-up-right

Validation strategies:

We use basic validation with a minimum score: Members with a voting power corresponding to more than 0.1% of the circulating supply can make proposals

  • Snapshot requires an absolute number, so we calculated what 0.1% corresponds to as of 2024-01-08:

    • Circulating supply: 137,392,418.57352012 MGV

    • 0.1% of circulating supply: 137,392

Voting configurationarrow-up-right

Quorum:

We’d like to set the quorum to 15% of the total voting power. However, Snapshot requires an absolute number, so we’ve calculated what 15% corresponds to as of 2024-01-08:

  • Circulating supply: 137,392,418.57352012 MGV

  • Total voting power: 3 * circulating supply = 412,177,255.72056036

  • 15% of total voting power: 61,826,588

Delegationarrow-up-right

The Delegation section is left unconfigured which (unintuitively) means that we use Snapshot’s built-in delegation system.

Membership

Membership of a governance group/Council is represented by ownership of an NFT (ERC-721). There is an NFT collection for each of the governance groups.

Each membership NFT controls a TBA (ERC-6551) and that TBA in turn is given tokens to represent the member’s attributes, such as their Activity Score (ERC-20, only relevant for Builders and Pods).

As we’d like members to be able to keep their membership NFTs after they leave Mangrove (it’s a nice memorabilia to have 🙂) we model active membership by giving the TBA an “Active Badge” token in a multi-token (ERC-1155) contract; When a member leaves a group, the active badge is burned.

The following diagram illustrates the setup:

Last updated

Was this helpful?