[What Happens When One ENS Name Manages Thousands of Accounts] @ensdomains @ethereum With the launch of ENSv2 on October 27, https://t.co/NvxB4rnXZr.eth and https://t.co/xwZsp1UT6i.eth can now be managed by different owners—allowing companies to grant specific teams only the permissions they need, without transferring full ownership of company.eth. This structure introduces a critical condition: a single domain can become a single point of failure for an entire service. If the parent name expires, all subordinate names beneath it become unreachable. ENS is known as a service that replaces long wallet addresses with human-readable names like alice.eth. In October, ENS disclosed it had approximately 905,000 .eth names and 34 million subordinate names. The total of over 36 million names includes both directly registered names and subnames issued by organizations. The model of using one name to manage multiple users and services is already in widespread use. ENSv2 restructures the foundation for managing these subnames. Each name can now maintain its own subname registry, and owners can assign granular permissions—such as registering new subnames, editing profiles, or managing subnames—based on specific roles. For example, an organization can issue individual names to employees or assign editing rights per team. While subnames existed before, ENSv2 integrates these management capabilities directly into the core contract architecture. On the flip side, responsibility becomes centralized. When resolving a name, ENSv2 traces up the chain from parent registries. If company.eth expires or its subname registry connection is severed, even possessing https://t.co/xwZsp1UT6i.eth won’t allow you to resolve its payment address. The ability to manage a subname is now tied directly to the parent name owner’s renewal and permission management. Expiration rules further intensify this responsibility. ENSv1 allowed 90 days of grace after expiration during which names remained resolvable. ENSv2 reduces this grace period to 28 days—and resolution stops immediately upon expiration. Renewing within the grace period restores functionality, but any lapse may disrupt connected services. When migrating existing names to v2, the expiration date is extended by 62 days to offset this difference. For example, if a v1 name had 100 days remaining until expiration, after migration it will have approximately 162 days left, and the point at which others can re-register remains around 190 days later for both versions. While re-registration eligibility aligns, v2 names become unresolvable during the final 28 days. The risk of losing the name to another party and the risk of temporarily disabling services now follow different timelines. For an individual’s personal nickname, this may simply be a reminder issue. But if an organization has issued thousands of subnames to customers, employees, or agents, a single failure to renew the parent name can disrupt access to multiple services. The more finely grained the role-based permissions, the more critical it becomes to assign clear responsibility for parent name renewal and establish emergency recovery procedures. Registration pricing changes are aligned with this design. The annual base price for .eth names of five characters or more has increased from $5 to $8—a 60% rise—while registering for six years or more reduces the annual cost to approximately $4.50. This pricing structure incentivizes long-term ownership over short-term use. However, as more accounts become linked to a single name, the cost of a failed renewal far exceeds the registration fee. Whether ENSv2 succeeds cannot be measured solely by new name registrations. More compelling indicators will be the actual adoption of subnames by organizations, the adoption of role-based permission delegation, and the growing number of apps capable of reliably resolving these names. ENS already supports name resolution for over 600 apps. Going forward, who takes responsibility for operating and maintaining these names will determine the protocol’s trustworthiness. #ENS #Ethereum