Tally — on-chain DAO governance, plumbed into treasury
Tally is the leading on-chain governance UI. We link every Tally-passed proposal to the treasury action it triggered.
Tally serves DAOs running Compound-style or OpenZeppelin Governor-style on-chain governance. Unlike Snapshot (off-chain voting), Tally proposals execute on-chain directly. The accounting integration ties each proposal's execution transaction to its treasury impact for the audit trail.
What the Tally integration does
Proposal ingest
All proposals across connected DAOs.
On-chain execution linkage
Each Tally execute() call linked to the resulting treasury impact.
Voter-attribution tracking
Per-proposal voter list preserved.
The connection in 4 steps
Connect Tally via GraphQL API
Provide your DAO's Governor contract address (or Tally DAO slug). Wag3s queries the Tally API to ingest all proposals — pending, active, executed, cancelled, and defeated — with full on-chain metadata.
Import on-chain proposal history
All proposals are imported with their calldata, execution status, proposer address, vote counts, quorum result, and the block timestamps of key events (creation, voting end, execution).
Link executed proposals to treasury transactions
Each Tally execute() transaction is linked to the on-chain treasury action it triggered — ERC-20 transfers, ETH disbursements, or smart-contract calls — and matched to the corresponding Wag3s wallet movement.
Anchor treasury disbursements to governance record
Every treasury spend that originated from a Tally proposal execution is annotated in the audit trail with the proposal title, vote outcome, and on-chain execution hash — creating a verifiable governance-to-disbursement chain.
Common configurations
The protocol holds $50M+ in treasury managed by a Compound Governor. All grants and protocol upgrades pass through Tally. Wag3s ties each executed disbursement to its Tally proposal, producing a governance-anchored treasury spend report for the quarterly foundation disclosure.
Liquidity mining rewards and ecosystem grants are approved via Tally proposals and distributed directly from the Governor timelock. Wag3s ingests each execution, classifies the token outflows as grant expense or incentive cost, and reconciles the total against the treasury balance.
Temperature checks happen off-chain on Snapshot; final execution goes through Tally. Wag3s ingests both, linking the Snapshot vote to the Tally execution transaction so the full governance trail from community signal to on-chain disbursement is captured in one audit record.
Tally integration questions
Does Wag3s support both Compound Governor and OpenZeppelin Governor contracts?
Yes. Wag3s decodes both Governor Bravo (Compound-style) and OpenZeppelin Governor contract variants. As long as the Governor contract ABI follows the standard interface, proposal and execution data is ingested correctly.
How are defeated or cancelled proposals handled?
Defeated and cancelled proposals are recorded in the Wag3s governance log but do not generate any treasury entries. They appear in the historical governance timeline and can be used as audit evidence that certain spending was not approved.
Can Wag3s handle Tally DAOs with a Timelock between the Governor and treasury?
Yes. Tally Governor → Timelock → treasury is the standard pattern. Wag3s traces the proposal calldata through the Timelock execution to the final treasury transfer, linking all three steps in the audit trail.
Other connectors that pair with this one.
Connect Tally in minutes
Free during Alpha. No credit card. Native sync, audit trail, no spreadsheets.