If e33 was about protecting what you say, e34 is about protecting who you are while you say it.

For most of the internet's history, identity was built on a simple bargain. Prove who you are by handing over data: a name, an email, a phone number, a government ID. That model made onboarding easy, but it also created huge databases of personal information that are attractive targets for attackers and convenient control points for platforms.

The next generation of identity works differently. Instead of revealing everything, a person proves only what is needed and presents an identity layer they control themselves. That is the core idea behind decentralized identity, selective disclosure, and user-owned naming systems like ENS.

Centralized identity systems solve one thing very well. They make it easy for a platform to know who a user is. But that convenience comes at a cost. Every new requirement to verify age, citizenship, or real-world identity creates another place where sensitive data can be stored, copied, leaked, or misused.

The problem is not only privacy. It is also resilience. When identity is controlled by a handful of companies or databases, users can be locked out, profiles can be deleted, and attackers only need to compromise one system to cause broad damage. The same data used to protect a platform can end up being the data that endangers its users.

A decentralized identifier, or DID, is a type of identifier designed to be decoupled from centralized registries, identity providers, and certificate authorities. The W3C defines DIDs as identifiers that let the controller prove control over the identifier without needing permission from any other party. In simple terms, a DID is a way to say "this identity is mine" without depending on one company to vouch for it.

That distinction matters because it changes the ownership model. Instead of a platform being the permanent source of truth, a user can hold and present proofs from their own wallet, device, or credential. Identity becomes portable, cryptographically verifiable, and far less dependent on any single provider's database.

ENS, short for Ethereum Name Service, is one of the clearest real-world examples of decentralized identity in practice. At its simplest, ENS turns a long wallet address into a human-readable name, but its role goes well beyond readability. ENS names can point to wallet addresses, websites, avatars, and other records that together form a portable profile across apps.

That makes ENS more than a naming tool. It functions as a user-controlled identity layer. Instead of every app forcing a fresh profile on a new user, an ENS name can travel with that person and carry a stable set of records they control. In a web3 setting, that is a meaningful shift: identity starts with something the user owns, not something a platform grants.

Forward resolution lets an ENS name point to an address or other record. Reverse resolution, also called a primary name, lets an address point back to a preferred ENS name, so apps can display a human-readable identity instead of a raw hexadecimal string. Together, these two directions make identity legible both to people and to software.

Text records extend this further. An ENS name can carry an avatar, a description, social handles, a website link, and addresses across multiple chains, so one name works as a lightweight profile across different apps and networks. ENS subnames add another layer, letting communities, teams, and applications issue identities under a shared namespace, which opens the door to portable, community-specific identity systems.

Zero-knowledge proofs sound abstract, but the idea is practical. A person can prove a statement is true without showing the data that makes it true. That means someone can prove they meet an age requirement without sharing a birth date, or prove they hold a credential without revealing the credential itself.

This shifts the default from "collect everything first, protect it later" to "prove only what is needed." In a world of data breaches, account compromise, and identity theft, that is not just a privacy improvement. It is a security improvement too.

XMTP shows what selective identity can look like inside a real messaging system. Its identity model centers on an inbox ID, a stable destination for messages that stays constant even as a user adds or removes wallets, passkeys, or other supported identifiers over time. A messaging identity does not have to be trapped inside one wallet address or one login method.

XMTP is also designed to support multiple types of identifiers, including Ethereum wallets, smart contract wallets, and passkeys, with a broader model for extending to additional identity systems over time. The basic logic is simple: if an identity can prove ownership cryptographically, it can be linked to the inbox.

Each inbox can also designate a recovery identity, which makes it possible to revoke a compromised identifier or rotate control without losing the messaging identity itself. This avoids the classic centralized failure mode of losing a phone number and, with it, an entire account.

This matters for the Nodle story because it moves the trust stack from a single authority to a distributed one. In the same way that local AI keeps compute on-device, and decentralized messaging keeps communication off a single readable server, decentralized identity keeps naming and proof of ownership from collapsing into a centralized database.

For someone new to crypto or web3, identity is often the hidden layer. People learn about wallets, tokens, and apps first, but identity determines whether those tools can be used without over-sharing. A better identity layer means fewer passwords, fewer KYC leaks, better recovery options, and less risk of one breach exposing an entire digital life.

It also creates room for healthier communities. If a user can present a consistent, self-owned identity without handing over a full profile to every platform, then a network can build trust and reduce spam without forcing everyone into a single centralized account system.

e34 closes the identity gap. e35 will bring the whole stack together: local AI, decentralized messaging, decentralized identity, and self-custody, all aligned around one idea, sovereignty through the full technology stack.

That is the real arc of Crypto 101. Not just understanding each layer on its own, but understanding how those layers work together to give users more control, more privacy, and more freedom online.