What Tally’s Shutdown Actually Tells Us About DAO Governance Demand
An Analysis of DAO Governance Interface and Infrastructural Failure
Ordo7 min read·Just now--
Did you know that Tally is shutting down? Apart from being sad news, it also reveals something more fundamental about DAO governance, which is worth understanding.
This article will explain a little about what Tally was, what they were trying to do, and why everything unravelled.
What Tally Was
Tally was a place where:
- Governance proposals could be created
- Delegates could vote
- Governance activity could be tracked
- Token holders interacted with governance.
In other words, it was a governance interface and infrastructure layer for DAOs.
You can think of it as the front-end for DAO governance. Similar to how Stripe is a payments infrastructure and Slack is a communication infrastructure, Tally tried to be DAO governance infrastructure.
And if you contribute to a DAO, you’ll have seen Tally’s name come up a lot when people are talking about proposals, voting, and delegation.
But now it’s over, but why?
Why Tally Shut Down
Tally put it best in their own words:
The simplest way to say it is this: there isn’t a venture-backed business in governance tooling for decentralized protocols, at least not yet.
There weren’t enough real, active governance participants to sustain a business around governance tools. That’s it.
Tally took a risk. Like all businesses, they bet on what a future world would look like. The success of their business model was dependent on there being thousands of DAOs, millions of active participants, and constant governance activity.
But the reality was (and, of course, still is) that there are few active participants, most token holders are passive, and governance is actually handled mostly by small delegate groups.
Governance exists, but not at the scale needed to make an infrastructure company like Tally a viable going concern.
But Tally knew this for quite some time.
Realising that things were not going to change anytime soon, there were signs in February to early March of this year that they were searching for a new economic base.
That was when they announced their ICO/token sale, .
It wasn’t long after this announcement that they published their shutdown announcement and the decision not to proceed.
So, the warning signs were there.
But if we want to dig a little deeper into the reasons for Tally’s failure, they can reveal a lot more about the state of DAO governance generally — and what needs to change to help pivotal players like Tally survive.
The diagram below is a useful starting point — not just for understanding Tally but also DAO governance more generally. The same principles apply.
What the Structure Shows
Here we can see the structural ordering of governance. Participation formation, the fourth level, was where Tally’s problems became clear to see. Far from just happening on its own, participation is produced by upstream conditions — orientation, institutional order, and community composition — and then preserved through institutional continuity.
This is crucial to understand because participation cannot be increased directly through tools or interfaces. It must be formed structurally.
And since upstream conditions dictate what happens downstream, we need to start at the top.
Orientation and institutional order determine how governance is structured in the first place. In many DAOs, governance is deliberately kept minimal or loosely defined to preserve flexibility. But that creates a structural trade-off: without clear purpose, enforceable rules, and stable authority, governance cannot organise participation into a repeatable system.
If those conditions are weak or unclear, that flows directly into community composition. And this is where the first symptoms of Tally’s failure started to become visible. There was a large nominal community, but the active core of it was tiny and so the demand for governance tools remained low — too low for Tally to survive.
From there, the effects continued downstream into participation formation. Since the community composition had already failed, the people in the Tally ecosystem had no chance of being formed into participants. That’s why activity remained low — too low to be sustainable.
And finally, this reached institutional continuity. Since participation never formed properly, it could not persist, which led directly to the economic consequences.
The first diagram explains where the problem exists structurally, and this second diagram shows the downstream consequences when continuity doesn’t form.
If institutional continuity is weak, you do not get participation continuity. Without participation continuity, trust does not deepen, reputation does not stabilize, and economic expansion does not follow.
Why the Demand Was Too Thin
Tools like Tally depend on recurring participation, not one-off activity.
As you can now see here, low participation wasn’t some accidental side issue. Tally’s own earlier governance writing calls low participation a “major weakness” of DAO voting systems, says many DAOs use delegation because participation is low, and says participation incentives are often costly and ineffective. In other words, this thinness is a built-in governance problem the company has understood for years.
That’s important to grasp because once governance is mostly delegated, the demand profile changes. If a small professionalized layer is doing the work, a broad, thick user base just cannot form. Intead, you get a narrower workflow market — too narrow for venture-scale.
That’s because the number of actors who actually need governance tooling remains small, even if the total number of token holders is large.
Tally’s own writing, again — this time on delegate compensation — basically says protocols need to reward “active, high-quality contribution” and turn “passive token holders into active protocol stewards,” which is another way of admitting that most token holders are passive and active governance needs extra scaffolding to exist.
What DAOs Would Have To Change
But that requires upstream work, not just participation work.
Tally expressed the problem very well. If DAOs were set up in a way to ensure that participation is thicker, with more active users and more governance activity, then things could have been a lot different.
But thicker participation is not the starting point. It is the downstream result of stronger orientation, institutional order, and community composition.
If this were understood, governance would be more structured. There would be clearer roles and more consistent usage. Continuity would exist, ensuring recurring participation and sustained engagement.
And if that had been in place, there would have been enough demand for tools like Tally to survive.
Orientation must be clear, institutional order must be strong enough to govern action, and community composition must be sufficiently formed to produce a real participating body.
Without that, participation will not thicken, and without thick participation, infrastructure demand will not persist. This is the practical implication.
DAOs have to strengthen the layers above participation before even considering relying on better tools or incentives alone.
Why Tally Is Not To Blame
It’s crucial to understand that Tally itself did very little wrong. That’s because the root failure is upstream from Tally. If you look at the first diagram again, Tally operated at the participation formation layer. But the real failure lay further upstream, in orientation, institutional order, and community composition — conditions Tally did not control.
Tally did a great job. It made governance easier to use but the system didn’t produce enough people who wanted — or were even able — to use it.
Tally built for a world in which participation would become much broader than it actually did. The harsh reality is, and this applies to any organization or group of people, participation must be formed before tools become viable.
What Tally Still Proved
Make no mistake. Tally didn’t fail because the team was weak or the product was bad. Quite the opposite. They did remarkably well —but only if their own efforts were the determining factor.
The team was fantastic. Led by CEO Dennison Bertram and co-founder and CTO Rafael Solari, they and the team they led are elite-level crypto engineers and operators.
The product was also excellent. In a little over just 5 years, they achieved over $1B processed, were used by the major protocols, had no major security incidents, welcomed over a million people to the platform, and tens of millions of token holder addresses cast proposals there. The issue wasn’t product quality or adoption at the top end.
But these headline numbers masked a deeper malaise. While millions of addresses interacted with governance at some level, actual recurring usage — which is what Tally really depended on — was far narrower, with activity concentrated among a relatively small number of participants.
Regardless, they showed that governance infrastructure for decentralized protocols can function in practice. And Tally will certainly go down in the history books for this achievement alone.
Takeaway
The reason for Tally’s failure was, in fact, largely out of its hands. The underlying social system (DAOs) has not yet been sufficiently formed. Tally was built for millions of participants, but the ecosystem produced only thousands. So this was a formation failure before it was a scaling failure.
If you look at any major DAO, you’ll see the same structural weakness play out. They have governance and they have delegates. But even the largest DAOs out there don’t generate enough depth to sustain a full governance tooling market.
Tally’s own year-end review shows that major DAOs often had voter counts in the low hundreds or low thousands on important proposals, not mass participation. Uniswap’s DUNI proposal had 145 voters, and a later Uniswap funding proposal had 139 voters.
Arbitrum had more activity, but even there the big proposals Tally highlighted were in the low thousands of voters, not millions.
Tally’s failure is not about one company. It’s actually evidence of a larger formation problem in DAO governance. Tally was one manifestation of a wider governance formation problem across crypto.
And until that is understood and efforts are made to make the changes needed, other tools like Tally will always struggle, no matter how good they are.
