ENS is a deployed contract. Where is it?
Specification: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-137.md
And why didn't they specify that in the EIP?
Add a comment
|
1 Answer
EIP-137 is a specification that anyone can follow should they want to implement their own EIP-137-compliant ENS service. (Think private networks, etc.)
To that end, it must remain agnostic towards specific implementations. By including the the address of the ENS team's deployed contract, that agnosticism would be lost, and it would no longer be a specification.
The ENS team's deployed registrar contract can be found here. EtherScan has an ENS portal, which can be found at: https://etherscan.io/ens (URL included in full deliberately... ) From there you can follow incoming transactions through to the registrar contract.
answered Feb 13, 2018 at 8:39
-
Arguably, the eth registry is only tangentially connected to the ENS spec. Without more clarification, I would say that the ENS contract is the registry, hosted at etherscan.io/address/0x314159265dd8dbb310642f98f50c066173c1259b as mentioned here docs.ens.domains/en/latest/introduction.html#ens-on-ethereum– carverFeb 13, 2018 at 17:38