From 6029f9c2d511dff784af2953cdf0a6accb1a1eff Mon Sep 17 00:00:00 2001 From: Trinh Trung Hieu <132073919+veoquynhs@users.noreply.github.com> Date: Thu, 25 Jan 2024 07:53:21 +0700 Subject: [PATCH] Update Capitalization in ENS-Contracts-Overview.md (#168) --- contract-api-reference/ENS-Contracts-Overview.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/contract-api-reference/ENS-Contracts-Overview.md b/contract-api-reference/ENS-Contracts-Overview.md index dd654d68e..1f61b33c3 100644 --- a/contract-api-reference/ENS-Contracts-Overview.md +++ b/contract-api-reference/ENS-Contracts-Overview.md @@ -12,12 +12,12 @@ The heart of the system is the ENS registry, it has been deployed on all ethereu On Ethereum Mainnet, the owner of the root node (which can be found by querying the registry for the node with id 0x0) is the Root Access control contract. Here are the owners of the major nodes and their related contracts: -* **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. +* **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) -* **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. #### Resolvers @@ -28,10 +28,10 @@ Resolvers are contracts that store metadata about the address/subnode, like an E * **ENS DAO (wallet.ensdao.eth)**: This is the main contract of the DAO, and the address that holds funds. It's set as owner of the root, token, registrar, controller and the dns registrar. This is an [Open Zepellin Governor contract](https://docs.openzeppelin.com/contracts/4.x/governance) that accepts incoming proposals by Token vote. All proposals have a minium 48 delay. The DAO has no roles set for admin, meaning that the governor and delay properties cannot be changed anymore. It has the power to add and remove controllers to the registrar and withdraw money from the controller. * **Governor (governor.ensdao.eth)**: This contract will calculate votes and if there is a majority win over quorum, then it will propose a transaction for the DAO. -* **The Token (token.ensdao.eth)**: this is the ERC20 compatible token. It also contains code for the airdrop and vote delegation. This contract allows the owner (the DAO) to mint up to 2% of the total supply once per year. -* **Registrar controller:** Controllers on the registrar have the power to register new names and extend the expiration date for new names. More than one controller can be added. This is the contract that receives payment for registration. +* **The Token (token.ensdao.eth)**: This is the ERC20 compatible token. It also contains code for the airdrop and vote delegation. This contract allows the owner (the DAO) to mint up to 2% of the total supply once per year. +* **Registrar controller**: Controllers on the registrar have the power to register new names and extend the expiration date for new names. More than one controller can be added. This is the contract that receives payment for registration. * **Price Oracle**: This contract checks an ether price oracle to calculate the price in ether for a renewal. It's logic can be changed by the DAO to anything, but any functionality that discriminates specific users would violate the article I of the ENS constitution. -* **Vesting (tokenlock.ensdao.eth):** at the time of this writing, this contract holds 65% of the token supply and releases slowly to the beneficiaries of core development tokens in the airdrop (including the DAO itself). +* **Vesting (tokenlock.ensdao.eth)**: At the time of this writing, this contract holds 65% of the token supply and releases slowly to the beneficiaries of core development tokens in the airdrop (including the DAO itself).