Original explanations of blockchain names, permissions and identity, connecting ENS product announcements to the designs published by ENS Labs.
Why read Ethereum Name Service (ENS)?
Read ENS when you want to understand what a blockchain name lets its users control. The ENSv2 subnames guide distinguishes records held in a resolver from names represented as transferable tokens. Its examples show why a display name, an owner and permission to edit a record are different concepts, and how retained administrative permissions change a service's trust model.
The ENS and GLEIF article applies that distinction to organizational identity: a readable name and a verifiable legal identity provide different kinds of information. It describes work in development, including a proposed standard, rather than a completed identity service. ENS Labs authors these selected technical explanations; ENS's protocol, development organization and community governance remain distinct parts of the project.
Start with the original
Selected work
Technical guide ·
Exploring Subnames in ENSv2
Who can edit, transfer or delegate a subname? Start with the resolver/registry distinction, then compare the examples and the administrative roles an operator retains.
Project explanation ·
ENS and GLEIF Explore Verifiable Organizational Identity Onchain
What would connect a name to a legal organization? ENS Labs explains a proposed association with vLEIs and identifies the standardization work still to come.
Projects & roles
Ethereum Name Service
The project's own site links its naming application, developer documentation and @ensdomains.
ENS governance
The public entry point to community governance, separate from ENS Labs' software-development work.
Onchain
Linked wallets
- Ethereum
0xd7a029db2585553978190db5e85ec724aa4df23fOpen in explorer - Ethereum
0xfe89cc7abb2c4183683ab71653c4cdc9b02d44b7Open in explorer