Update ENS-Contracts-Overview.md #168
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Reformat capital letters
| * **DNS Oracle (dnssec.ens.eth)**: This oracle performs a CCIP read on a given DNS name and grants the owner. To learn more read [Secure offchain data retrieval Standard](https://eips.ethereum.org/EIPS/eip-3668) | ||
| * **Reverse Registrar (addr.reverse)** This reverse registrar allows an account to set their primary name. | ||
| * **Reverse Registrar (addr.reverse)**: This reverse registrar allows an account to set their primary name. |
| * **The Root control (root.ens.eth)**: This is a simple access control for the root. It serves as an interface for the ENS registry, except it also allows some names to be locked. Once locked the owner cannot unlocked it. At the time of this writing, only .eth was locked, and since this contract doesn't allow to transfer ownership of the root node itself, it means that the .eth registrar is now forever locked on the main registry. The owner of the root contract is set as the multisig.ens.eth. | ||
| * **The Multisig (multisig.ens.eth)**: This is a group of 7 keyholders who were initially charged with the responsibility of managing most of ENS aspects. With the launch of the ENS DAO, most of these responsibilites are slowly being transferred away, but as requested by EP1, the root ownership still belongs to them. | ||
| * **.ETH Registrar (registrar.ens.eth)**: This is an ERC721 compatible contract, and is the address ENS users will likely add to their wallets to see their domains as NFTs. Transferring an NFT will not automatically update the ownership on the Registry, but allows the NFT owner to call the "claim()" function which will update the registry on their behalf. This contract allows its owner (currently set as the DAO) to add and remove controllers, as well as change ownership of the registrar. Metadata for the NFTs are not set in the contract, but at stored at the metadata.ens.domains service. | ||
| * **DNS Registrar (dnsregistrar.ens.eth)**: This contract owns mosts TLDs recognized by ICANN and use DNSSec to update these names. | ||
| * **DNS Oracle (dnssec.ens.eth)**: This oracle performs a CCIP read on a given DNS name and grants the owner. To learn more read [Secure offchain data retrieval Standard](https://eips.ethereum.org/EIPS/eip-3668) |
| * **DNS Oracle (dnssec.ens.eth)**: This oracle performs a CCIP read on a given DNS name and grants the owner. To learn more read [Secure offchain data retrieval Standard](https://eips.ethereum.org/EIPS/eip-3668) | ||
| * **Reverse Registrar (addr.reverse)** This reverse registrar allows an account to set their primary name. | ||
| * **Reverse Registrar (addr.reverse)**: This reverse registrar allows an account to set their primary name. |
There was a problem hiding this comment.
Suggested change
| * **Reverse Registrar (addr.reverse)**: This reverse registrar allows an account to set their primary name. | |
| * **Reverse Registrar (addr.reverse)**: This reverse registrar allows an account to set their primary name. | |
| * **The Multisig (multisig.ens.eth)** This is a group of 7 keyholders who were initially charged with the responsibility of managing most of ENS aspects. With the launch of the ENS DAO, most of these responsibilites are slowly being transferred away, but as requested by EP1, the root ownership still belongs to them. | ||
| * **.ETH Registrar (registrar.ens.eth)** This is an ERC721 compatible contract, and is the address ENS users will likely add to their wallets to see their domains as NFTs. Transferring an NFT will not automatically update the ownership on the Registry, but allows the NFT owner to call the "claim()" function which will update the registry on their behalf. This contract allows its owner (currently set as the DAO) to add and remove controllers, as well as change ownership of the registrar. Metadata for the NFTs are not set in the contract, but at stored at the metadata.ens.domains service. | ||
| * **DNS Registrar (dnsregistrar.ens.eth)** This contract owns mosts TLDs recognized by ICANN and use DNSSec to update these names. | ||
| * **The Root control (root.ens.eth)**: This is a simple access control for the root. It serves as an interface for the ENS registry, except it also allows some names to be locked. Once locked the owner cannot unlocked it. At the time of this writing, only .eth was locked, and since this contract doesn't allow to transfer ownership of the root node itself, it means that the .eth registrar is now forever locked on the main registry. The owner of the root contract is set as the multisig.ens.eth. |
There was a problem hiding this comment.
Suggested change
| * **The Root control (root.ens.eth)**: This is a simple access control for the root. It serves as an interface for the ENS registry, except it also allows some names to be locked. Once locked the owner cannot unlocked it. At the time of this writing, only .eth was locked, and since this contract doesn't allow to transfer ownership of the root node itself, it means that the .eth registrar is now forever locked on the main registry. The owner of the root contract is set as the multisig.ens.eth. | |
| * **The Root control (root.ens.eth)**: This is a simple access control for the root. It serves as an interface for the ENS registry, except it also allows some names to be locked. Once locked the owner cannot unlocked it. At the time of this writing, only .eth was locked, and since this contract doesn't allow to transfer ownership of the root node itself, it means that the .eth registrar is now forever locked on the main registry. The owner of the root contract is set as the multisig.ens.eth. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reformat capital letters