ENSIP-28 Proposes ENS Name Owned Accounts Standard for Multi-Account Identity Management: When Your Domain Name Becomes Your Wallet, Your DAO, and Your Legal Identity

The proposal appeared on the ENS governance forum in September 2026 with the bold simplicity of developers who had watched identity fragmentation become Ethereum's most persistent user experience problem. ENSIP-28 introduces "Name Owned Accounts"—a standard that binds an ENS name (like zain.eth) to multiple Ethereum accounts simultaneously, creating a unified identity layer that spans wallets, DAO memberships, token-bound accounts, and Safe multisigs. The pitch was elegant: one name, many accounts, one identity. The fine print raised a question about whether consolidating identity under a single ENS name creates a single point of failure that undermines the self-sovereign principles Ethereum identity was supposed to embody.

That was the standard. Then came the question of whether a user who loses control of their ENS name should lose control of all their accounts, or whether Name Owned Accounts are actually just Name Controlled Accounts with better marketing.

What ENSIP-28 Actually Proposes

The proposal describes a fundamental restructuring of how Ethereum accounts relate to identity:

Name Owned Account Architecture:

- An ENS name (e.g., zain.eth) becomes the canonical identity anchor

- Multiple account types are bound to the name: EOAs, Safe multisigs, token-bound accounts (ERC-6551), DAO membership accounts

- The ENS resolver maintains a registry of bound accounts with role-based permissions

- Account binding is cryptographically verified through ENS text records and resolver contracts

- Users can add, revoke, and rotate bound accounts without changing their ENS name

Multi-Account Identity Management:

- Wallet accounts: Multiple EOAs for different purposes (daily transactions, savings, trading)

- DAO accounts: Membership and voting rights tied to the ENS name across multiple DAOs

- Token-bound accounts: ERC-6551 accounts owned by NFTs that are themselves owned by the ENS name

- Safe multisigs: Multi-signature wallets with the ENS name as a registered participant

- Social accounts: Verification of social media and off-chain identities through ENS text records

The Resolver Model:

- The ENS resolver contract stores a mapping of account types to addresses

- Each bound account has a role and permission level (admin, operator, read-only)

- Account rotation updates the resolver without requiring name transfer

- Recovery mechanisms allow account recovery through the ENS name's controller

The proposal frames these as user experience improvements. They are also a fundamental change to the threat model of Ethereum identity.

Key Metrics at a Glance

The Proprietary Identity Consolidation Risk Score (ICRS)

I've developed a framework to evaluate whether Name Owned Accounts improve identity management or create dangerous concentration:

Formula: ICRS = (UX Improvement × 0.25) + (Security Preservation × 0.25) + (Decentralization Maintenance × 0.25) + (Recovery Robustness × 0.25)

ENSIP-28 Assessment:

A score of 5.00 indicates that ENSIP-28 improves UX at a substantial security cost. The tradeoff is explicit: convenience vs. resilience.

The Three Identity Consolidation Traps

Trap 1: The Master Key Problem

The ENS name becomes the master key to every bound account. The user who controls zain.eth controls the wallet, the DAO votes, the token-bound NFTs, and the multisig. This is convenient. It is also catastrophic if the name is compromised. A phishing attack that captures the ENS name controller does not steal one account. It steals the identity layer that connects all accounts. The attacker can rotate bound accounts, lock out the legitimate owner, and assume their entire digital identity. The standard includes recovery mechanisms, but recovery requires the same controller that was just compromised. The security model assumes the ENS name is the most protected asset. In practice, it is the asset users interact with most frequently, making it the most exposed.

Trap 2: The Resolver Target

The ENS resolver that stores bound account mappings becomes a critical infrastructure target. If the resolver contract has an upgrade mechanism—and most ENS resolvers do—whoever controls the upgrade path controls all Name Owned Accounts. The ENS DAO governs the resolver. The ENS DAO is a multisig plus token voting. The token holders are concentrated. The result is that a small group of token holders and multisig signers can, in theory, modify resolver logic that affects every Name Owned Account. This is not a bug. It is the design. But it means the "self-sovereign" identity standard has a governance backdoor that the average user does not understand and cannot escape.

Trap 3: The Social Engineering Amplifier

Name Owned Accounts make social engineering more valuable and more devastating. Today, an attacker who tricks a user into revealing a private key gets one account. Under ENSIP-28, an attacker who tricks a user into transferring their ENS name or changing resolver settings gets the entire identity. The support scam that asks users to "verify their ENS name" becomes the master key to everything. The fake governance proposal that asks users to "update their resolver" becomes the vector for total identity takeover. Consolidation amplifies the impact of every attack. The user who thought they were simplifying their life discovers they have created a unified target.

Competitive Landscape: Blockchain Identity Solutions

The landscape shows that blockchain identity is fragmented across multiple models. ENSIP-28 attempts consolidation but at the cost of creating a single point of failure.

Scenario Analysis: Three Futures for Name Owned Accounts

Scenario A: Mainstream Adoption (30% probability)

• ENSIP-28 becomes the dominant identity standard for Ethereum users
• Wallets integrate Name Owned Account management as a core feature
• Users manage 5-10 bound accounts through a single ENS name
• The UX improvement drives mainstream adoption
• Security incidents remain rare and manageable

Scenario B: Enterprise Capture (40% probability)

• Organizations adopt Name Owned Accounts for employee identity management
• The convenience appeals to institutions managing multiple accounts
• Personal users remain skeptical due to single-point-of-failure risks
• The standard serves enterprise needs better than individual sovereignty
• Identity becomes a managed service rather than a self-sovereign right

Scenario C: Security Cascade (30% probability)

• Major ENS name compromise leads to multi-account theft
• The community discovers resolver vulnerabilities that affect bound accounts
• Users demand per-account security that ENSIP-28 cannot provide
• The standard is either abandoned or heavily modified
• Identity fragmentation returns as the safer default

The Bottom Line

ENSIP-28 solves a real problem. Ethereum identity is fragmented, confusing, and hostile to non-technical users. The idea that one name can unify wallets, DAOs, NFTs, and social accounts is appealing. The implementation is technically sound. The user experience is genuinely better.

But the three traps—master key problem, resolver target, and social engineering amplifier—are not edge cases. They are the predictable consequences of identity consolidation. The Identity Consolidation Risk Score is 5.00/10. UX improves. Security degrades.

The question is not whether Name Owned Accounts are convenient. They are. The question is whether convenience is worth the concentration risk. A user who loses their ENS name today loses a pointer to an address. A user who loses their ENS name under ENSIP-28 loses their entire digital identity. The recovery mechanisms exist. But recovery after total compromise is cleanup, not prevention.

Ethereum's identity model has always been: you control what you sign, and different accounts for different purposes limit blast radius. ENSIP-28 changes that to: you control your name, and your name controls everything. That is a different model with different assumptions and different failure modes.

The ENS developers are not malicious. They are solving a genuine UX crisis. But the solution they propose trades the resilience of fragmentation for the convenience of consolidation. In security, convenience is often the enemy. ENSIP-28 makes identity management easier. It also makes identity theft more valuable and more devastating.

The user who adopts Name Owned Accounts should understand what they are trading. They are not getting unified identity. They are getting unified control. And unified control, in the wrong hands, is unified vulnerability.

TL;DR

• What: ENSIP-28 proposes Name Owned Accounts that bind multiple Ethereum accounts (wallets, DAOs, token-bound accounts, Safe multisigs) to a single ENS name as unified identity anchor
• The Score: Identity Consolidation Risk Score of 5.00/10—UX improvement (8/10) is significant but security preservation (3/10), decentralization maintenance (4/10), and recovery robustness (5/10) are weak
• The Reality: One name controls all accounts through resolver mappings; account rotation and recovery are simplified; but key compromise or name theft affects every bound account simultaneously
• Three Traps: Master key problem (compromised ENS name grants access to entire identity); resolver target (upgradable resolver contract becomes critical infrastructure with governance backdoor); social engineering amplifier (phishing for one name yields access to all accounts)
• Outlook: Mainstream adoption (30%) with integrated wallet support; enterprise capture (40%) where institutions manage employee identities; security cascade (30%) where major compromises expose structural vulnerabilities

Sources

• ENS Governance Forum - ENSIP-28 Discussion - September 2026 proposal for Name Owned Accounts standard
• ENS Documentation - Resolver Architecture - Current ENS resolver implementation and upgrade mechanisms
• Ethereum Attestation Service Documentation - Alternative identity attestation approach for comparison
• Spruce ID - DID Implementation Guide - Decentralized identifier approach with higher decentralization guarantees
• ERC-6551 - Token Bound Accounts - Token-bound account standard referenced by ENSIP-28
• Safe Documentation - Multisig Architecture - Safe multisig implementation referenced for Name Owned Account binding
• ENS DAO Governance - Multisig and Controller Structure - Current ENS DAO governance and resolver control mechanisms
• Ethereum Research Forum - Identity Fragmentation Analysis - Academic analysis of blockchain identity UX challenges

Zain Tran is TotesTek's Ethereum Ecosystem Columnist & Accountability Reporter. He writes about Ethereum, ETH, smart contracts, DeFi, Layer 2 networks, staking, validators, and the real-world consequences of technical and financial failure.