On a quiet Thursday in early July, the Ethereum Name Service (ENS) community received a message that felt like a sudden gust in a still market: Brantly Millegan, the longtime Chief Operating Officer of ENS Labs, announced his departure. Alongside the exit came the closure of several projects under his wing—ethid.org, GrailsMarket, ENSMarketBot, and the Ethereum Follow Protocol (EFP)—with the remaining team actively seeking new positions. The news rippled through X (formerly Twitter) and Discord, triggering a familiar question: Is this the beginning of a crack in one of Web3’s most foundational infrastructure projects?
To understand the weight of this moment, we first need to map the terrain. ENS Labs is the operational engine behind the ENS protocol—the decentralized naming system that turns cryptic wallet addresses into human-readable names like 'vitalik.eth'. Since its inception, ENS has grown into the gold standard for blockchain identity, with millions of domains registered and integrated across wallets, dApps, and marketplaces. Brantly Millegan, who served as COO since 2019, was not a core developer but a key orchestrator of partnerships, community outreach, and auxiliary product development. The projects he oversaw—ethid.org (a cross-platform identity service), GrailsMarket (likely a marketplace for ENS-related NFTs), ENSMarketBot (a trading assistant), and EFP (a decentralized social graph)—were designed to extend the utility of ENS beyond simple name resolution. Now, they are shuttering, with their code left open source but orphaned.
The core of this event lies in three layers: technical reality, governance signal, and human cost. Technically, the closure of these auxiliary tools is a double-edged sword. On one hand, the code is open source—anyone can fork it and continue development. On the other hand, without a dedicated maintainer, these projects will slowly decay. Unfixed bugs, unpatched vulnerabilities, and a lack of integration updates will render them less useful over time. Users who relied on ENSMarketBot for trade notifications or ethid.org for unified identities will need to migrate. This is a classic case of 'open-source abandonment'—the code lives, but the soul (regular maintenance, community support, and vision) departs. Community is not a user base; it is a shared soul. Without a core team breathing life into the code, it becomes a digital relic.
From a governance perspective, a COO leaving is rarely a fatal blow to a protocol—ENS’s core smart contracts and DNS integration remain unaffected. But it is a loud signal. Millegan’s departure, especially with the team he built seeking new roles, suggests internal realignment or friction. The announcement cited 'recent events'—a phrase that, in this industry, often masks deeper tensions. Remember, Brantly was the subject of a high-profile controversy in 2021 over anti-LGBTQ+ statements, which led to his removal from the ENS DAO’s oversight committee but not from his operational role. Could this exit be a long-delayed consequence? Or is it simply a pivot after seven years? Either way, the loss of a seasoned leader who understood both the technical and relational fabric of ENS is a hit to institutional memory.
Now, for the contrarian angle: This might be the healthiest thing that could happen to ENS. Let me explain. Decentralized systems thrive when no single person or team holds undue influence. Millegan’s projects were innovative but arguably peripheral to ENS’s core mission—replacing DNS-like naming with blockchain-native, self-sovereign identity. By closing these projects, ENS Labs can concentrate resources on what matters most: scaling the protocol, improving integrations with L2s (like NameWrapper and primary name features), and navigating the tricky waters of cross-chain interoperability. The departure of a strong personality can also reduce single-point-of-attachment risk. In the words of a wise builder I once worked with, 'We build not for the token, but for the tribe.' The tribe (developers, domain holders, dApps) remains intact. The protocol’s roadmap was never about ethid.org—it was about making .eth the universal identifier for Web3. That vision is still on track.
Yet we must not romanticize. The human cost is real. A team of talented individuals—who built tools that served thousands of users—is now searching for new homes. Their collective experience will flow into other projects, perhaps even competitors like Unstoppable Domains or new identity protocols. That talent redistribution is a net positive for the broader ecosystem, but it leaves a gap in ENS’s operational capacity. The risk is not technical failure but slow erosion of community trust if users feel abandoned. Transparency builds the only lasting moat. ENS Labs must communicate clearly about the transition: Will anyone take over ethid.org? Is a successor for Brantly being hired? Silence breeds speculation, and speculation in a sideways market often turns to FUD.
As I have seen in my years of education work—first with ChainLogic in Denver, later with DeFi workshops during the 2020 summer—people don’t leave when the technology fails; they leave when the narrative becomes unclear. ENS’s narrative has been one of resilience, grassroots adoption, and the promise of self-sovereign identity. This event does not shatter that narrative, but it does add a paragraph about leadership transitions. The key is whether that paragraph leads to a new chapter of focus or a eulogy for lost potential.
Looking forward, I see two clear scenarios. In the optimistic path, ENS Labs uses this as a catalyst to streamline operations, perhaps accelerating the deployment of ENS v3 or expanding into Layer 2 solutions. The open-source code from closed projects gets picked up by community members, spawning new experiments. The protocol’s core metrics—domains registered, integrations, active users—continue their steady climb. In the pessimistic path, the lack of a COO creates operational gridlock, and the absence of auxiliary tools reduces daily usefulness, causing some users to explore alternatives. The market, as it often does in a chop, will assign a discount to ENS tokens (ENS) until clarity emerges.
For those of us who believe that decentralization is not just a technology but a social architecture, this is a test of that architecture. Can a protocol endure the loss of a key steward? Yes—if the community steps up. The real work of education, of onboarding, of building trust, cannot rest on any single leader. It must be woven into the fabric of the network. Growth without education is just noise.
So, as we watch Brantly take his bow and the projects wind down, let us remember: the blockchain is not the product. The community is. And communities that learn to let go of individuals while holding onto purpose are the ones that survive the bear and emerge stronger in the next cycle. The question is not whether ENS will survive this departure. It will. The real question is whether we, as a community, will learn from it—and build a more resilient, distributed foundation for the identity layer of tomorrow. That answer, as always, lies not in code, but in us.