---
title: "Tally (now Cactus)"
url: "https://caper.network/wiki/dao-governance/tooling/voting/tally"
updated: 2026-08-20
license: CC-BY-4.0
license_url: "https://creativecommons.org/licenses/by/4.0/"
---

# Tally (now Cactus)

|  |  |
| --- | --- |
| **Category** | On-chain governance · [Governor](/wiki/dao-governance/concepts/fundamentals/dao-governance-models) tooling |
| **Launched** | 2020, by Tally (CEO Dennison Bertram) |
| **What it did** | Hosted read / propose / vote / queue / execute interface for OpenZeppelin Governor DAOs |
| **Scale** | Powered on-chain governance for [Uniswap](/wiki/daos/dexs/uniswap-dao), [Arbitrum](/wiki/daos/networks/arbitrum-dao), [ENS](/wiki/daos/infrastructure/ens-dao), [Aave](/wiki/daos/lending/aave-dao) and 500+ DAOs |
| **Status** | Hosted product wound down March 2026; platform continued as **Cactus** under [ScopeLift](https://scopelift.co/blog/tally-is-now-cactus) |
| **Site** | [tally.xyz](https://www.tally.xyz/) (now Cactus) · [shutdown notice](https://newsletter.tally.xyz/p/tally-is-shutting-down) |
| **Related** | [Snapshot](/wiki/dao-governance/tooling/voting/snapshot) · [Proposal lifecycle](/wiki/dao-governance/concepts/voting/proposal-lifecycle) · [Governance models](/wiki/dao-governance/concepts/fundamentals/dao-governance-models) |

**Tally** was, for most of the on-chain-governance era, the place a major DAO went to actually run a vote. Where [Snapshot](/wiki/dao-governance/tooling/voting/snapshot) handled gasless off-chain signaling, Tally was the **binding on-chain** layer: a hosted interface sitting on top of the [OpenZeppelin Governor](https://docs.openzeppelin.com/contracts/5.x/governance) contracts, where a proposal moved from draft to an executed transaction that actually moved the treasury. Launched in 2020 by CEO Dennison Bertram, it powered governance for [Uniswap](/wiki/daos/dexs/uniswap-dao), [Arbitrum](/wiki/daos/networks/arbitrum-dao), [ENS](/wiki/daos/infrastructure/ens-dao), [Aave](/wiki/daos/lending/aave-dao) and more than 500 other DAOs. In March 2026 the hosted product [announced it was winding down](https://www.coindesk.com/markets/2026/03/17/gensler-and-biden-were-just-better-for-crypto-says-tally-ceo-as-dao-governance-platform-shuts-down); the platform has since been taken over by [ScopeLift and rebranded Cactus](https://scopelift.co/blog/tally-is-now-cactus).

## What Tally standardized

Tally didn't invent on-chain governance — it made it legible. A Governor DAO's state lives in a contract: who can propose, the voting delay and period, quorum, and a timelock that queues a passed proposal before it can execute. Tally read that state directly from chain and wrapped the whole [proposal lifecycle](/wiki/dao-governance/concepts/voting/proposal-lifecycle) in one interface — draft a proposal as executable calldata, open it for [token-weighted voting](/wiki/dao-governance/concepts/voting/token-weighted-voting), watch it reach quorum, queue it in the timelock, then trigger the on-chain execution. Because it indexed every [OZ-Governor](https://docs.openzeppelin.com/contracts/5.x/api/governance) deployment the same way, any DAO using the standard contracts got a working governance front-end for free, and delegates got one dashboard across every protocol they participated in.

## Who ran on Tally

The client list read like a census of on-chain governance: [Uniswap](/wiki/daos/dexs/uniswap-dao), [Arbitrum](/wiki/daos/networks/arbitrum-dao) — one of the largest DAO treasuries anywhere — [ENS](/wiki/daos/infrastructure/ens-dao), [Aave](/wiki/daos/lending/aave-dao), ZKsync, and hundreds of smaller protocols. By its own account the platform processed over a billion dollars in on-chain governance transactions across those DAOs. That concentration is exactly why its wind-down mattered: a large slice of the industry's binding governance flowed through one hosted interface.

## The March 2026 wind-down

On 17 March 2026 Tally announced it would [shut the hosted product down](https://newsletter.tally.xyz/p/tally-is-shutting-down) after six years, having scrapped a nearly-complete ICO first. Bertram's reasoning was pointedly counter-intuitive: the regulatory pressure that had made on-chain governance a near-necessity had eased. He argued that the Gensler-era SEC [effectively forced decentralization through legal risk](https://www.coindesk.com/markets/2026/03/17/gensler-and-biden-were-just-better-for-crypto-says-tally-ceo-as-dao-governance-platform-shuts-down), and that a more permissive stance — alongside the 2025 Clarity and stablecoin frameworks — gave projects compliant, centralized paths that no longer required DAO governance as legal cover. Demand for the tooling, in his telling, fell with the pressure that had created it. The episode became a marker of a wider **governance-tooling retrenchment** in 2026, as the sector consolidated toward a handful of professional-governance vendors.

## Continued as Cactus

The story didn't end at shutdown. Engineering studio [ScopeLift took over the platform](https://scopelift.co/blog/tally-is-now-cactus) and relaunched it as **Cactus** — “new name, same platform” — keeping the Governor-indexing interface alive for the DAOs still running binding on-chain votes. The underlying OpenZeppelin Governor contracts were always the DAOs' own on-chain property, unaffected by any front-end changing hands; Tally was the interface, not the governance itself. That distinction is the useful lesson of the whole episode. One practical note for anyone chasing the rebrand: the rename did not come with a new domain. Checked on 20 August 2026, [tally.xyz](https://www.tally.xyz/) serves the Cactus product directly, at 200 and with no redirect, while the unrelated cactus.build belongs to a different company entirely.

## How Caper approaches this

Tally's wind-down is a clean illustration of front-end risk: when a DAO's governance runs through a hosted third-party app, the app is a dependency that can be sold, rebranded, or shut down. [Caper](/wiki/foundations/what-is-a-caper) removes that layer by making governance native to the protocol. A caper's proposals are [created](/wiki/governance/proposals), [voted on](/wiki/governance/voting), and [executed](/wiki/governance/execution) by the caper's _own_ on-chain contract — there is no separate governance company whose survival the members depend on. If every interface to Caper disappeared tomorrow, the proposal and voting logic would still be sitting in the contract, executable directly. Governance you don't have to keep a vendor alive to use is the point.

## References

- Tally, [“Tally Is Shutting Down”](https://newsletter.tally.xyz/p/tally-is-shutting-down) (shutdown announcement).
- CoinDesk, [‘Gensler and Biden were just better for crypto,’ says Tally CEO as DAO governance platform shuts down](https://www.coindesk.com/markets/2026/03/17/gensler-and-biden-were-just-better-for-crypto-says-tally-ceo-as-dao-governance-platform-shuts-down) (17 March 2026).
- ScopeLift, [“Goodbye Tally, Hello Cactus”](https://scopelift.co/blog/tally-is-now-cactus) (platform continuation).
- OpenZeppelin, [Governor documentation](https://docs.openzeppelin.com/contracts/5.x/governance).
- Tally / Cactus, [tally.xyz](https://www.tally.xyz/).