The soul remains. Audit complete. But the architect leaves with a box of code under his arm.
On July 4, Brantly Millegan, the long-serving Chief Operating Officer of ENS Labs, announced his departure via a thread on X. He didn't just resign—he brought down the curtain on four projects he personally shepherded: ethid.org, GrailsMarket, ENSMarketBot, and the Ethereum Follow Protocol (EFP). All will be wound down in the coming weeks. The code? Left open source. The team? Already looking for new gigs.
For the casual observer, this is a footnote in the sprawling Ethereum ecosystem. For those of us who dig deep for the truth in the chain, it's a signal. A subtle tremor in the organizational bedrock of one of crypto's most established naming services.
Context: The Man Behind the Machines
Brantly Millegan joined ENS early—back when the domain service was a niche tool for power users who wanted vitalik.eth instead of a 42-character hex address. He rose to COO, overseeing not just the core protocol's growth but a suite of auxiliary products that made ENS more accessible. Ethid.org acted as an identity layer; GrailsMarket was a marketplace for rare ENS names; ENSMarketBot automated trading decisions; and EFP built a social graph layered on top of ENS. These were not revenue monsters, but they were glue—holding together a fragmented user experience.
But glue can also be a leash. When the glue-maker walks away, the ecosystem's seams show.
Core: What Really Happened Here?
Let's strip away the public relations coating. Brantly cited "recent events" as the catalyst. The crypto grapevine—and I've been tracking these narratives since my earliest audit days—remembers his 2021 comments opposing LGBTQ+ rights, which sparked outrage and a token-holder vote to remove him from the ENS DAO board. That vote failed, but the wound never fully healed. Now, whether the "recent events" are a revival of that controversy or something else entirely, the outcome is the same: a top executive is out, and four projects are dead.
From a technical standpoint, the impact on ENS core is near zero. The registry, the resolver, the .eth minting—none of it touches these shutdowns. But as an archaeologist of the abstract, I see deeper patterns. The COO is the person who ensures internal coordination, keeps the lights on for non-critical tools, and shields the core devs from bureaucratic noise. Losing that role without an announced successor creates an operational vacuum. During the 2020 DeFi Summer, I witnessed similar scenarios where sudden departures caused cascading delays in protocol upgrades. ENS is mature, but still depends on a small team for maintenance.
More troubling: the projects being killed are not just arbitrary experiments. EFP, for instance, had growing traction as a decentralized follow protocol. Its shutdown halts development—and while the code remains open source, unmaintained code becomes a bug magnet. I've audited dozens of abandoned repositories; the number of unpatched vulnerabilities grows exponentially after the last commit.
Contrarian: Maybe This Is Good?
A contrarian lens flips the narrative. Brantly's pet projects may have been distractions—resource sinks that diluted ENS Labs' focus on the core domain service. By amputating these limbs, ENS Labs can double down on what matters: scaling the .eth namespace, improving cross-chain resolution, and fending off competitors like Unstoppable Domains. The open-source nature even invites community forks. A dedicated group could pick up EFP and run with it, free from corporate overhead.
But here's the catch: the community rarely forks operational responsibility. Code is easy to copy; maintainers are not. The GrailsMarket bot had active users who depended on its signals. Ethid.org held user identity preferences. Without a clear migration path or a new maintainer, those users will drift to centralized alternatives—exactly the outcome decentralization is supposed to prevent.
And what about the team? Brantly said they're "looking for work." That's not just four projects dying; it's a group of experienced builders dispersing into the wind. These are the people who knew the ENS ecosystem's quirks. Losing them means losing institutional memory—a form of entropy that no smart contract can patch.
Takeaway: Beyond the Code
This episode teaches us something about governance that no white paper captures: people are the state, not the contracts. ENS Labs can replace a COO, but it cannot replace the trust that users placed in Brantly's projects overnight. The soul may remain, but it needs a new vessel.
As I told my DAO clients during the bear markets, chop is for positioning. Right now, the chop in ENS's organizational chart presents a positioning opportunity—but not for yield. For vigilance. Watch for the next core departure. Watch for unresolved user asset complaints from the shut-down services. And watch whether the community can breathe life into those open-source ghosts.
Digging deep for the truth in the chain means reading between the blocks. Brantly's exit is not a catastrophe. It's a canary.
