Witness-DAO

Free · no account · nothing is sealed

Governance evidence readiness scan

Paste a Snapshot space or a Gnosis Safe address. The scan reads your recent governance and tells you how strongly each action is bound to independently observable reality — and therefore what it could prove if you sealed and anchored it.

Try ens.eth, aave.eth or gitcoindao.eth. A tally recomputation reads every vote, so a busy space can take twenty seconds or so.

What this does, precisely

It reads

  • Snapshot proposals, the votes on them, and the tally — which it independently recomputes from the enumerated vote set rather than repeating what the hub reports.
  • Safe multisig confirmations, executions and ERC-20 treasury movements across Ethereum, Optimism, Base and Arbitrum.
  • It runs the same witness-dao providers you would install, so this page demonstrates the code rather than an approximation of it.

It does not

  • Seal anything, create any record, or spend anything.
  • Return or retain a wallet address. It counts actions and discards the addresses; results are aggregates.
  • Produce an evidence report. A report is a signed artefact derived from sealed records; this is a survey of the inputs.
  • Require a key, a wallet signature, or an email address.

Why two grades rather than one

Records do not exist yet, so there is no verification state to combine with the binding. The scan therefore projects both ends of the honest range.

Sealed and anchored today

What a default deployment actually produces right now. Nothing pinned ships with the library, so every anchor reads asserted_unverified and every record caps at SIGNED_PENDING.

Ceiling, once anchors can be verified

The best each action could ever grade, limited purely by how well it is bound to reality. Reaching it means accepting a trust-pin set — a block-header source, a log key, a TSA root — so anchors can be checked against something you chose in advance.

Showing only the ceiling would be marketing. Showing only today’s grade would understate the product. The gap between them is entirely about anchor verification, and nothing about your governance.

Governor and Tally contracts

Governor (on-chain Tally-style) contracts are supported by the library but not by this hosted scan, because reading Governor events needs a JSON-RPC endpoint. Shipping a default public RPC would mean choosing on your behalf which node operator sees which addresses you are investigating, and it would put this service between you and your own chain data. Run `witness-dao ingest --dao <governor-address> --source governor --chain-id 1` locally with WITNESS_DAO_RPC pointed at a node you trust.

Readiness scan · Witness-DAO