LibraryData and agents2017Design paperCorpus record
Ethereum Name Service: names, resolvers, and records
ENS. ENS.
ENS publishes a name registry and a resolver interface. The name is a record. It is not a certificate that the website it points at is honest.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
ENS publishes a name registry and a resolver interface. The name is a record. It is not a certificate that the website it points at is honest.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 1
01 Claim ledger
What the paper is allowed to say
Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.
Claim 01 · Paper model
The defect
A human-readable name feels like identity. The protocol only maps a name to records under the rules of the registrar.
Claim 02 · Paper model
The proposal
ENS publishes a name registry and a resolver interface. The name is a record. It is not a certificate that the website it points at is honest.
Claim 03 · Paper model
The mechanism
The registry stores who controls a name. The resolver stores the records the controller points at. They are different contracts.
Claim 04 · Paper model
The bound
No fee and no name count is stated here.
02 Three cuts
Observation, model, falsifier
A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.
01 The defect
Observation
What the study says
A human-readable name feels like identity. The protocol only maps a name to records under the rules of the registrar.
Model
What has to hold
You are reading the ENS docs. EIP-137 is the earlier interface standard and is a related, not identical, text.
Falsifier
What would retire it
Are the records on-chain or fetched from a gateway?
02 The proposal
Observation
What the study says
ENS publishes a name registry and a resolver interface. The name is a record. It is not a certificate that the website it points at is honest.
Model
What has to hold
You are reading the ENS docs. EIP-137 is the earlier interface standard and is a related, not identical, text.
Falsifier
What would retire it
Who can change the resolver for the name?
03 The mechanism
Observation
What the study says
The registry stores who controls a name. The resolver stores the records the controller points at. They are different contracts.
Model
What has to hold
No price, supply, yield, or adoption figure is added by this desk.
Falsifier
What would retire it
Who can change the resolver for the name?
04 The bound
Observation
What the study says
No fee and no name count is stated here.
Model
What has to hold
You are reading the ENS docs. EIP-137 is the earlier interface standard and is a related, not identical, text.
Falsifier
What would retire it
Who can change the resolver for the name?
03 Sequence
One action, as an operating tape
- 01The registry stores who controls a name. The resolver stores the records the controller points at. They are different contracts.
- 02A registrar's allocation rule, such as an auction or a renewal fee, is a policy of that registrar. It is not part of the resolver interface.
- 03CCIP-read or off-chain resolution, where documented, means the record may not sit on Ethereum at the moment you ask.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
ENS publishes a name registry and a resolver interface. The name is a record. It is not a certificate that the website it points at is honest.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A resolver can return any address the controller sets. The protocol does not check the address.
What actually moves
The cut
A registrar's allocation rule, such as an auction or a renewal fee, is a policy of that registrar. It is not part of the resolver interface.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A resolver can return any address the controller sets. The protocol does not check the address.
What a later deployment may change
The cut
CCIP-read or off-chain resolution, where documented, means the record may not sit on Ethereum at the moment you ask.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A later client, parameter or reward formula is a different object from this paragraph.
05 Register
What has to be true
Model · Not re-measured
You are reading the ENS docs. EIP-137 is the earlier interface standard and is a related, not identical, text.
Model · Not re-measured
The document is the one at the source URL. A marketing page with the same brand is not this text.
Model · Not re-measured
No price, supply, yield, or adoption figure is added by this desk.
06 Divergence
What happened after the paper
A resolver can return any address the controller sets. The protocol does not check the address.
A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.
07 Pre-mortem
What to check before you use the idea
- 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.
08 Anatomy
The paper, in the order a builder needs
The problem it names
A human-readable name feels like identity. The protocol only maps a name to records under the rules of the registrar.
What the design proposes
- The registry stores who controls a name. The resolver stores the records the controller points at. They are different contracts.
- A registrar's allocation rule, such as an auction or a renewal fee, is a policy of that registrar. It is not part of the resolver interface.
- CCIP-read or off-chain resolution, where documented, means the record may not sit on Ethereum at the moment you ask.
How the mechanism is specified
- The registry stores who controls a name. The resolver stores the records the controller points at. They are different contracts.
- A registrar's allocation rule, such as an auction or a renewal fee, is a policy of that registrar. It is not part of the resolver interface.
- CCIP-read or off-chain resolution, where documented, means the record may not sit on Ethereum at the moment you ask.
What this page does not treat as proven
- No fee and no name count is stated here.
- Ownership of a name is not ownership of a trademark. This note does not say otherwise.
- A resolver can return any address the controller sets. The protocol does not check the address.
Why the desk still reads it
ENS publishes a name registry and a resolver interface. The name is a record. It is not a certificate that the website it points at is honest.
09 Lexicon
Terms, opened into the record
- Registrar
- The contract that allocates names. Different registrars can have different rules.
- Resolver
- The contract that answers records for a name. It does not allocate the name.
10 Repository
Every linked record on this page
Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.
Protocols
This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.
Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.