DAO Proposals — Onchain Verified

What this Actor does

Shows DAO governance votes checked directly against each DAO's own Governor contract — not just Snapshot, the offchain temperature-check layer most trackers show. Covers ENS, Arbitrum, Uniswap, Compound, Optimism, Lido, Curve (Ownership), Curve (Parameter) and Aave today.

This is not another Snapshot mirror. Public trackers can be wrong or simply silent. While building this, we found a well-known public tracker showing Arbitrum's DAO as archived — zero active proposals — while its Governor contract had a live, binding vote on 48M ARB with a deadline days away. An agent trusting only the tracker would have missed it entirely. The discrepancy field exists specifically to catch this class of failure.

Usage scenario

A trading agent tracks governance for DAOs whose tokens it holds or trades. It needs to catch votes that could move price or liquidity — without blindly trusting one external source that might be stale, incomplete, or simply wrong.

Input — optional filter by a single DAO:

{ "dao": "ENS" }

Leave dao empty to fetch all nine configured DAOs in one run.

Example output

One real dataset item (trimmed to the fields that matter most for evaluating a proposal — the full field list is in the Output tab):

{
  "dao": "ENS",
  "proposal_id": "80619211450810140112687536515944199882433060764177806587986222097717655810120",
  "sources": ["onchain"],
  "title": "Proposal #806192114508…",
  "vote_type": "onchain_binding",
  "status": "active",
  "closes_at": "2026-08-08T21:10:45.413Z",
  "votes": { "for": "1146479.618632655947352941", "against": "387647.529426331501519092", "abstain": "0", "unit": "ENS" },
  "after_close": {
    "code": "onchain_timelock",
    "detail": "Onchain vote. If it passes, it enters the Timelock queue and becomes executable after the contract's delay."
  },
  "discrepancy": "This ENS onchain vote is live right now, but Snapshot shows zero active or pending proposals for this DAO — the offchain signal stays silent about it.",
  "onchain_verified_at": "2026-08-06T07:14:00.340Z",
  "fetched_at": "2026-08-06T07:14:00.340Z"
}

discrepancy is null when the two sources agree — that's the common case. When it isn't null, that's the actual product: a signal the offchain layer alone would have missed. sources_status in the run's key-value output shows, per DAO, whether Snapshot and onchain each answered fully — never a silently incomplete result.

Configuration

Input field	Required	Meaning
dao	No	Filter to a single DAO: ENS, Arbitrum, Uniswap, Compound, Optimism, Lido, Curve (Ownership), Curve (Parameter), or Aave. Omit to fetch all nine.

No API key, no account, no proxy configuration needed — this Actor reads directly from Snapshot's public GraphQL API and each DAO's own Governor contract via public RPC endpoints.

FAQ

Why not just use Snapshot directly? Snapshot only shows what was submitted through it. The covered DAOs all also run binding, execution-triggering votes directly through their Governor contract — votes that can be missing from Snapshot entirely, or behind on indexing. Missing those means missing the votes that actually change something onchain.

What does a run cost? A typical run (all configured DAOs) takes a few seconds and a small, fixed amount of compute.

Does it collect personal data? No. Every field is onchain or public-governance data — proposal text, vote tallies, wallet addresses, contract links. No names, emails, or other personal identifiers.