Naming system in the form of registry contract within Hedera

[som-web23]

Description:

This PR proposes new schema of naming system in the form of registry contract within Hedera that would allow multi-parties to co-exist and provide minting, managing of web3 domains in .hbar or HTTLDs (Hedera Top Level Domains)

This PR modifies ... in order to support ...

• It is a Draft for HIP - Registry Contracy for Naming Services

Related issue(s):

Fixes #

Notes for reviewer: A Draft for HIP - Registry Contracy for Naming Services

Checklist

• [ yes] Documented (Code comments, README, etc.)
• [ NA] Tested (unit, integration, etc.)

[netlify[bot]]

✅ Deploy Preview for hedera-hips ready!

Name	Link
🔨 Latest commit	10c97499cbe836d91e1717dc8acd55b726f3ecc4
🔍 Latest deploy log	https://app.netlify.com/sites/hedera-hips/deploys/6605d49893476f0008b53049
😎 Deploy Preview	https://deploy-preview-534--hedera-hips.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Cooper-Kunz]

Is there a discussion forum by which we can talk about this? It seems to outline a specific set of smart contracts (without a reference implementation) but does not define a way by which to mitigate multiple issuers of a domain/namespace.

Specifically, does this HIP imply that in order to establish .calaxy, I have to use web23's contracts? It reads as so.

[rahul-web23]

Is there a discussion forum by which we can talk about this? It seems to outline a specific set of smart contracts (without a reference implementation) but does not define a way by which to mitigate multiple issuers of a domain/namespace.

Specifically, does this HIP imply that in order to establish .calaxy, I have to use web23's contracts? It reads as so.

Hello @Cooper-Kunz , we have a Slack Channel as a discussion forum for the HIP. We have outlined a set of smart contracts where we allow multiple issuers of domain/namespace , as providers. Each and every provider has the capabilities to issue domains/TLDs and register it under the smart contract.

These registry contracts have a pure intention to avoid duplicates. This is a common domains/namespaces dumping station , where any provider can book domains at their end using their smart contracts and they just need to intimate these smart contracts that yes something has been booked. So in order to establish .any .tld there needs to be couple of things whih needs to be done :-

1. Check whether .tld is available or not
2. Register .tld as a provider/issuer Role.

This registration of TLDs ensures registry contracts holds a record of .tld under your provider Role and will not be duplicated in any sense. Now as a provider you can implement your logic to mint domains under that .tld, and that is independent of Registry Contracts. Also web23 doesn't own,govern or control any of these. These Smart contracts once released would be owned by Swirlds Lab or so and Web23 would be interacting with these smart contracts as Providers.

[mgarbs]

What do we want to do with this HIP @som-web23 @rahul-web23 @nostradaomus ? Making it Stagnant for now because it hasnt had activity for a while. It can be resurrected or a new HIP can be created

[nostradaomus]

@mgarbs I think it's best if the parties involved (which at this point is just BCW Group and Kabuto) start fresh on a new proposal.