| hip | title | author | working-group | type | category | needs-council-approval | status | discussions-to | created | updated |
|---|---|---|---|---|---|---|---|---|---|---|
534 |
REGISTRY CONTRACT for naming structure |
Som Kirann([email protected]), Rahul Pandey([email protected]) |
Standards Track |
Application |
false |
Stagnant |
2022-07-29 |
2024-03-28 |
- Abstract
- Motivation
- Rationale
- Specification
- Detailed note on the flow
- Reference Implementation
- Rejected Ideas
- Open Issues
- References
- Copyright/license
Fostering overall growth of Hedera, minting of HTLDs (Hedera based -Top-Level-Domains) & SLDs (Second-Level-Domains) within Hedera are open. Any entity, person could mint of the HTLDs & SLDs which could eventually create issues like: a. Duplication of TLDs; .hbar (for example) by one contract & .hbarby the other contract b. Duplication of SLDs; for example, minted SLD user.tld by one contract & user.tld by the other contract c. Inconvenience amongst the community owing to the duplication of names d. Challenges for the wallets providers to choose one contract over the other
To develop a naming standard in registry contracts to prohibit duplicate Hedera specific TLDs and their corresponding Second-Level-Domains, thus allowing multiple parties to mint the routes without worrying of duplicates leading to a healthier ecosystem and new use cases.
Taking the motivation, a further step ahead, it is proposed to allow multiple parties who could be resellers, companies to exist within the ecosystem of Hedera and allow community/users to mint/book domains ending in .hbar or any other TLD without the fear of duplication or phishing attempts. Proposed Hedera centric registry contract that would also be extended to other inter-operable chains in the future would be able to accommodate multiple parties. Same registry contract would contain the real truth of mappings between Account IDs on the Mainnet & the corresponding human readable user-names. For example, john.hbar tied to 0.0.XXXXXXX
Architecture of the proposed registry contract over Hedera would be, as follows:
(Image source: https://drive.google.com/file/d/1e3yxtaY8glEiptSXlrNxznxfzTfk1SKr/view)
1. What is Registry Contract Suite?
Registry Contract Suite is a group of smart Contracts developed over Solidity. These smart contracts are intended to register HTLDs (Hedera Top-Level-Domains) and Second-Level-Domains (SLDs) in a hierarchical manner. SLDs and HTLDs once registered could be queried and looked up to avoid duplication.
2. How does Registry Contract Suite Works?
Registry Contract Suite is a well structured group of smart contract that maintains an alphabetical hierarchy to register HTLDs and is structured to create and store HTLDs in their respective Alphabetical Registry Component.
Once a HTLD is registered by the provider, an entry in respective alphabetical hierarchy smart contract is made. All further domains and subdomains under that hierarchy would be stored in that structure. So that for future, queries for that registered domain names or HTLD/s could be appropriately handled.
3. Who are providers and how could someone become a provider of domains/HTLDs?
Providers for Registry Contracts are the account addresses of Mainnet of entities who have access to register and update HTLD/s and domains. These providers could do a handful of operations and are provisioned to register a domain/HTLD. All these would be handled by Swirlds Lab or Hbar Foundation.(So that no Provider controls or gate keeps the process)
To become a provider, entities need to raise a request to the admin of Registry Contracts, who have the privilege to add addresses as providers for the Registry Smart Contract Suite. Initially this would be done through a form accessible via the website of Web23 at web23.io with a goal of moving to a fully decentralized approach.
4. Structure of Smart Contracts
The structure of smart contracts are as follows:
a. AlphaInterface: This solidity file is an interface and it enables functions and abstract logic for the AToZRegistry Solidity Smart Contract. It enables functionalities such as register HTLD, activate TLD, etc.
b. AlphaRegistry: This solidity file is responsible for doing all the jobs and is exposed for providers. It would internally call different smart contracts from the suite to get the job done.
c. UTools: This smart contract empowers the suite with a handful of utility functions like substring and all.
d. AToZRegistry: This solidity file is responsible for creating an alphabetical order of smart contracts
e. Exposed Functionalities and Functions (may not be in the order)
i). isTLDAvailable method is used to check whether a particular TLD is available or not.
Inputs:- TLDName
Output:- True or False
Scenario :- This method is an external view function and will return Boolean and is used to Check whether a TLD is available or not
ii). isDomainAvailable method is used to check whether a particular Domain under a TLD is available or not.
Inputs:- DomainName, TLDName
Output:- True or False
Scenario :- This method is an external view function and is used to check whether a particular Domain under a TLD is available or not.
iii). registerTLD method is used to register TLD, only providers who are registered would be able to register a TLD
Inputs:- TldOwnerAddress, TLDName, ChainId, Expiry
Output:- True or False
Scenario :- This method is an external view function and is used to register TLD, only providers who are registered would be able to register a TLD
iv). registerDomain method is used to register domain, only providers who are registered would be able to register a domain
Inputs:- DomainOwnerAdress,TldOwnerAddress,TLDName,DomainName,ChainId,Expiry
Output:- True or False
Scenario :- This method is an external view function and is used to register Domain, only providers who are registered would be able to register a domain
v). activateDomain method is used to activate Domain
Inputs:- DomainName, TLDName
Output:- True or False
Scenario :- This method is an external view function and is used to activate a Domain, only providers who are registered would be able to activate a domain.
vi). deactivateDomain method is used to deactivate a domain
Inputs:- DomainName, TLDName
Output:- True or False
Scenario :- This method is an external view function and is used to deactivate a Domain, only providers who are registered would be able to deactivate a domain.
vii). updateDomainExpiry method is used to update the Domain Expiry
Inputs:- DomainName, TLDName, expiry
Output:- True or False
Scenario :- This method is an external view function and is used to update the Domain Expiry. The expiry should be a greater than the current date.
viii). deactivateTLD method is used to deactivate TLD
Inputs:- TLDName
Output:- True or False
Scenario :- This method is an external view function and is used to deactivate TLD so that no domain under that TLD could be booked.
ix). activateTLD method is used to activate TLD
Inputs:- TLDName
Output:- True or False
Scenario :- This method is an external view function and is used to activate TLD so that domain under that TLD could be booked.
x). updateTLDExpiry method is used to update the TLD Expiry
Inputs:- TLDName,Expiry
Output:- True or False
Scenario :- This method is an external view function and is used to update TLD Expiry
xi). addProvider method is used to add Provider to the Registry, so that they could add TLDs and domains to the Registry.
Inputs:- ProviderWalletAddress
Output:- True or False
Scenario :- This method is an external view function and can be only executed by the administrator/Super Admin of the Smart Contract Suite and is used to add Provider to the Registry , so that they can add TLDs and Domains to the Registry.
xii). getProvider method is used to get Provider by passing their provider ID
Inputs:- ProviderID
Output:- ProviderWalletAddress
Scenario :- Each time a provider is registered , a Provider ID would be allocated by the smart Contract suite and the provider Wallet Address will be mapped/associated with that Provider ID. This method on passing that provider ID, would return the Provider Wallet address of Mainnet.
N/A
N/A
N/A
N/A
This document is licensed under the Apache License, Version 2.0 – see, https://www.apache.org/licenses/LICENSE-2.0)