# GIP-140: Should GnosisDAO revamp Snapshot voting strategies

- Space: [GnosisDAO](https://snapshot.box/s:gnosis.eth.md)
- Author: 0xdaf3323dcECe13126590708eAb07DF0CC31CDD44
- State: Passed
- Voting type: Basic
- Start: 2025-10-21 14:23 UTC
- End: 2025-10-28 14:23 UTC
- Votes: 82
- Quorum: 75,000 voting power
- Discussion: https://forum.gnosis.io/t/gip-140-revamp-snapshot-voting-strategies/11696/1
- Open in Snapshot: https://snapshot.box/#/s:gnosis.eth/proposal/0x3bc992771ddb3b5ddfb098ba242590e8b0d686e75c16b6691e06e3f958156821

## Results

- For: 202,995.27 voting power, 100.0%
- Against: 0.22 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

# Summary
This proposal replaces the current subgraph based GNO strategy with a set of strategies that read state directly on-chain and from the beacon chain. There are 3 main objectives to this proposal:
- Add support for StakeWise tokens (`sGNO` and `osGNO`)
- Improve accuracy for validator balances
- Remove the external dependency on The Graph (everything is now handled by Snapshot)

# Introduction
The GnosisDAO Snapshot space is currently impacted by the GNO strategy, which depends on Subgraph indexers. This has led to availability issues and inaccurate voting powers because beacon chain state cannot be inferred from the execution layer. We propose moving to on-chain data with a set of new strategies to reduce inaccuracy in the voting power calculation.

In addition to delegations, voting power will come from:
- GNO balance (Gnosis Chain and Ethereum)
- Locked GNO (Gnosis Chain, Ethereum)
- Validator balance (Gnosis Chain)
- StakeWise’s `sGNO` and `osGNO` (Gnosis Chain)

# Specification

1. Deprecate the subgraph-dependent GNO strategy.
2. Execution layer sources (Gnosis Chain / Ethereum)
    - Use the [contract-call strategy](https://github.com/snapshot-labs/score-api/tree/master/src/strategies/strategies/contract-call), pointing to an aggregator contract on Gnosis Chain that returns each account’s total GNO voting power across GNO, lGNO, sGNO, and osGNO. The contract was deployed and verified at [0xE6C45c06e4C73e2aD58Aedf9bf83bCe1534b524a](https://gnosisscan.io/address/0xE6C45c06e4C73e2aD58Aedf9bf83bCe1534b524a#code)
    - Use the [contract-call strategy](https://github.com/snapshot-labs/score-api/tree/master/src/strategies/strategies/contract-call), pointing to an aggregator contract on Ethereum that returns each account’s total GNO voting power across GNO and lGNO. The contract was deployed and verified at [0x1B2Eef4dd90cF1aF05967e0F246d4C0a19387B2A](https://etherscan.io/address/0x1B2Eef4dd90cF1aF05967e0F246d4C0a19387B2A#code).
3. Consensus layer
    - Created a new [beacon-chain strategy](https://github.com/snapshot-labs/score-api/tree/master/src/strategies/strategies/beacon-chain) to attribute staked GNO from the beacon chain by withdrawal address.
4. Delegation
    - Update the delegation strategy to support the 3 previously mentioned strategies.

# Implementation plan
Now that [GIP-130](https://forum.gnosis.io/t/gip-130-changes-to-gnosis-eth/10373/5) passed, we can simply update the **snapshot** text field on **gnosis.eth** to update the configuration of the Snapshot space. The plan is to set it to **ipfs://QmP6TVsWAcbxBNM229mgHXpxW7C9bTujk9LzDsiAWqDf7h** with the following transaction:

```
[
    {
        "to": "0x4976fb03C32e5B8cfe2b6cCB31c09Ba78EBaBa41",
        "operation": "0",
        "value": "0",
        "method": "setText(bytes32 node, string key, string value)",
        "params": [
            "0x77651e2c25d2b7b073d1068420770f96a43563e74df60e234b2433b2be66e29e",
            "snapshot",
            "ipfs://QmP6TVsWAcbxBNM229mgHXpxW7C9bTujk9LzDsiAWqDf7h"
        ]
    }
]
```

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

