# What Is Dead May Never Die.

*Lighthouse Labs on the future of coordination infrastructure after Tally*

By [Lighthouse Labs](https://paragraph.com/@lighthousegov) · 2026-03-25

daos, governance

---

Last week, Tally announced it is winding down operations after six years of powering governance for over 500 DAOs. The coverage has been predictable:

> "_DAOs are dead._"  
> "_Governance tooling has no business model._"  
> "_Decentralization was just regulatory theatre._"

We think this diagnosis is wrong. Not because the symptoms aren't real, but because it confuses the failure of a specific product category with the failure of coordination itself.

Tally built a version of what governance tooling was understood to be: voting portals, delegation dashboards, proposal workflows. It served many users, but they couldn't build a sustainable _VC-backed_ business. That fact deserves examination, not a eulogy for the entire field.

The Voting Portal Was Never the Product
---------------------------------------

The first generation of governance tooling did not play out as expected. But the deeper issue is that even where DAOs _did_ thrive, the experience of participating in governance remained fundamentally broken. Voter turnout stayed low. Proposal quality was uneven. Treasury decisions were made by tiny fractions of tokenholders.

Voting portals can shine a spotlight on governance, but we need real innovation if the ecosystem is going to evolve.

What We've Been Building — and Why It's Different
-------------------------------------------------

At Lighthouse Labs, we've spent the past three years working at the intersection of mechanism design, identity infrastructure, and governance research. Not because governance tooling seemed like a good market opportunity, but because we believe the coordination layer for internet-native organisations hasn't been invented yet.

That conviction has produced work across several areas that, taken together, represent a fundamentally different approach to the problem.

### ENS Metadata

If you can't describe what an organisation is, you can't govern it.

The Node Metadata Standard, currently in [draft status as an ENSIP](https://github.com/ensdomains/ensips/pull/64/changes), introduces a composable schema for attaching structured metadata to ENS names. Think of it as a way for any entity represented by an ENS name or subname to also describe its role, capabilities, and relationships in a machine-readable format that lives on-chain.

This is more than just profiles and avatars, it's the precondition for governance that understands who is participating, in what capacity, and with what context. Without it, every governance interface is flying blind.

The foundations of this new standard are already out there and being discussed, especially within the context of debates about the future of agent identity architecture on ENS. It's our most recent contribution to the ecosystem, and it's the foundation everything else builds on.

### The ENS Retrospective

We proposed one of the first major DAO retrospective’s together with [James](https://x.com/blockchainjames) (🔥[\_](https://x.com/fireeyesgov)🔥). What has [since been produced](https://drive.google.com/drive/folders/1JIbN_V4hyDJo-fUoZVTrb7iYg7lFlIe2) by the [Metagov](https://metagov.org/) team creates an _empirical_ baseline for what in the past has been mostly _anecdotal_.  

### AI Governance Assistance

Concurrent to this work, we ran AI-assisted [grant evaluation](https://discuss.ens.domains/t/ai-for-grant-spp-evaluation-screening/21939) experiments. Using language models to systematically assess SPP2 applications against consistent criteria, we explored the idea of automated or augmented screening to reduce operational burdens in decentralized organizations. The results weren't a replacement for human judgment, but they revealed how much can be done with the data we already have if you just run it through the right tools and processes.  
  
We also implemented and improved upon the well-renowned Talk to the City method and ran it in parallel with the Retro to [compare and contrast](https://discuss.ens.domains/t/a-continuous-governance-surface-a-talk-to-the-city-inspired-experiment/21975) findings.

This research matters because it demonstrates something most governance teams skip: empirical accountability. If you're going to build tools for collective decision-making, you should first understand how collective decisions actually get made and where they break down.

### Signals Protocol: Capturing Preference Intensity

Token-based, closed-list voting has been the centerpiece of collective decision-making for too long. Real-world experience so far has shown that forcing users into a binary “yes/no” choice results in difficult decisions and inflexible initiatives.

Using similar economic systems to allow voters to instead express a preference (and preference intensity) before moving to the final vote can expose true community sentiment and result in better-planned proposals going up for a vote.

This is what we provide with [the Signals Protocol](https://www.researchretreat.org/papers/paper/?venue=dacc25&id=6), which allows voters to temporarily lock up capital in support of their preferences. The result is better use of the “wisdom of the crowd” while the economic game theory of anonymous blockchains still works to enforce good behavior.

The Consolidation Ahead
-----------------------

We're clear-eyed about the market. Tally's closure will accelerate consolidation in governance tooling, and many teams are already moving to fill the gap. This is natural and healthy. The ecosystem needs multiple independent frontends and diverse approaches.

But we'd gently observe that most of the emerging responses to Tally's shutdown are variations on the same theme: better voting interfaces, more security monitoring, slicker dashboards. Although these are necessary, they are not sufficient. We need deeper structural reforms in our behaviors and an openness to experimentation if we truly believe that internet native organizations  have a viable future.

* * *

_Lighthouse Labs builds coordination infrastructure for decentralised systems. Our contributions to Ethereum include Harbor Protocol, Signals Protocol, EGPL, and the ENS Metadata Standard. We are active contributors to ENS DAO governance and the broader Ethereum ecosystem._

---

*Originally published on [Lighthouse Labs](https://paragraph.com/@lighthousegov/what-is-dead-may-never-die)*
