ENS DAO just voted to hand over 1% of its total token supply—100,000 ENS—to a newly formed foundation. No vesting schedule. No auditable salary cap. Just a 9-day timelock and a five-person board that includes the protocol’s founder. This isn’t a bug fix. It’s a governance refactor that shifts the trust model from code to people.
Context
The proposal, branded “DAO New Era,” carves ENS into three independent entities: the DAO retains governance over the treasury and protocol parameters; ENS Labs focuses on R&D (ENSv2, core infrastructure); and the new ENS Foundation handles operations, policy, and real-world engagement—ICANN, IETF, W3C, intellectual property, hiring. The foundation gets a one-time transfer of 1M ENS from the DAO’s 54.6% holdings to fund salaries and operations. The remaining 54.6% stays under DAO control. A 5-person board runs the foundation: Nick Johnson (ENS founder), Alexander Urbelis (ENS exec), Kartik Talwar (A.Capital), Brett Sun (Prelude), and Anthony Leutenegger (Aragon). The Security Council retains emergency veto power. The treasury’s endowment fund is untouched.
This is a classic “separation of concerns” pattern—but in crypto, separation of concerns often means separation of accountability.
Core: The Fine Print of the Fork
Let’s dissect the technical and economic mechanics.
Token Flow and Incentives
The 1M ENS transfer is a one-time allocation with no explicit vesting schedule or clawback clause. The foundation can use it for salaries, operational costs, or—if the board decides—staking or lending. The protocol’s revenue (domain registration fees) flows into the endowment fund, which remains under DAO control. The foundation has no direct claim on future revenue. This means the foundation’s burn rate is fixed: 1M ENS, period. If they run out, they must return to the DAO for another vote. That’s a strong leash, but the leash is only as good as the DAO’s willingness to say no.
Governance Friction
The 9-day timelock on all foundation transactions is a deliberate drag. It’s the same pattern used by Compound and MakerDAO—a “cooling-off” period to prevent a single malicious board vote from draining funds. But in a market where liquidity can evaporate in hours, 9 days is a lifetime. The Security Council can cancel any operation that exceeds the foundation’s mandate, but the council’s members are not publicly disclosed in detail. Trust is computed, but here the computation is opaque.
Board Composition
Five seats. Two are from the core ENS team (Johnson and Urbelis). The remaining three are independent: Talwar (VC), Sun (Aragon co-founder), Leutenegger (Aragon CE). That’s a 40% insider representation. In traditional corporate governance, this would raise red flags for minority shareholder protection. In crypto, it’s a step toward professionalism—but it also means the foundation’s strategic direction will be heavily influenced by the people who built the protocol. That’s efficient, but it blurs the line between “community oversight” and “founder control.”
ENSv2 and the Real-World Gambit
The proposal explicitly states that ENS Labs will now focus on protocol development, including ENSv2—a major upgrade to the on-chain registration and resolution architecture. The foundation will handle the boring stuff: talking to ICANN about a .ens top-level domain, filing patents, hiring lawyers. This is the real bet. If .ens becomes a recognized internet domain, ENS’s value proposition shifts from “crypto name service” to “global identity infrastructure.” That’s a 10x addressable market. But it’s also a 10x regulatory surface area.
Contrarian: The Centralization Dividend
Most analysts see this as a maturation signal. I see it as a tax on decentralization.
First, the 1M ENS allocation is a governance subsidy. The foundation will spend it on salaries and operations, which means the DAO is effectively paying for a centralized management layer. The DAO retains control, but the DAO’s voting power is diffuse. The foundation’s board, by contrast, is small and coordinated. In practice, the board will drive the agenda, and the DAO will react.
Second, the legal structure creates a new attack surface. If the foundation is registered in the US (likely for ICANN engagement), it becomes subject to SEC jurisdiction. The Howey test evaluates whether token holders rely on the efforts of others. With a foundation actively managing the protocol’s future, that “effort of others” argument becomes stronger. The foundation’s very existence could be used as evidence that ENS is a security.
Third, the separation of power between Labs and the foundation introduces a coordination risk. What happens if Labs wants to build a feature that the foundation’s IP strategy forbids? Or if the foundation prioritizes .ens commercial deals over protocol decentralization? The proposal doesn’t define a dispute resolution mechanism. Code is law, but governance is politics.
Based on my experience auditing the Anchor Protocol’s smart contracts in 2021, I learned that the most dangerous vulnerabilities are often in the governance layer—not the code. Anchor’s withdrawal function had an integer overflow that amplified the death spiral. Here, the overflow is structural: the foundation’s board has the power to spend 1M ENS, but the DAO’s only recourse is a 9-day timelock and a vote. In a crisis, that’s too slow.
Takeaway: The Trust Refactor
ENS DAO didn’t just create a foundation. It created a new trust boundary. The old system trusted the DAO’s smart contract and the token holders. The new system trusts a five-person board and a security council. Math doesn’t negotiate, but humans do. The foundation’s success depends on whether the board’s incentives align with the community’s.
If the foundation delivers .ens and ENSv2, the 1M ENS will be remembered as a brilliant investment. If it fails, it’s a governance tax. Either way, the industry will watch this experiment closely. The next time a DAO votes to centralize, it won’t be a surprise. It will be a pattern.