The Genome mission is to create a digital-ID product centered around .GNO domains, integrating the communities, dApps, and utilities native to Gnosis chain as well as linking .GNO domains with ENS. Genome is built by Gnosis, @dm3protocol and @SpaceIDProtocol
Product Features:
- .GNO domains integrated with the Gnosis ecosystem
- Digital-ID NFT collection native to Gnosis
- Developing a CCIP resolver for ENS enabling .GNO domains to be resolved on Ethereum
Space-ID
Space-ID has already built the infrastructure system for their own TLD name service. Since then Space-ID has launched .bnb .arb and .sei TLDs. Having a large partnership ecosystem means it will one of the definitive and established TLD name service for the foreseeable future
Integrations:
Space-ID has developed their own Web3 name SDK that integrates the Space-ID contract & domains, and supports all the Space-ID APIs. Space-ID provides a free HTTP API with a rate limit to help Dapps integrate the name-resolving and reverse-name-resolving services.
Docs:
https://www.npmjs.com/package/@web3-name-sdk/core
DM3**
Previously a part of the ENS team and also worked on Space-ID’s .bnb product as well as developing resolvers for Optimism and messaging protocols for ENS. DM3 will be developing a resolver that will link Space-IDs .GNO domains with ENS
ENS defines this standard where an example.eth address can issue text.example.eth on Layer 2 (or another Layer 1 like Gnosis Chain). With no or minimal trust assumptions.
Each example.gnosis.eth subdomain on Ethereum will point to a example.gno domain on Gnosis Chain and managed by Space ID.
.gno is resolved via https://www.npmjs.com/package/@web3-name-sdk/core
.gnosis.eth is resolved via an up-to-date version of ethersjs for example.
When I enter example.gnosis.eth in metamask - for example - the CCIP resolver contract returns a URL to a CCIP-Read client like ethers.js. This URL can be used to perform an off-chain lookup instead of fetching the records from the contract directly.
When calling the URL, the Gateway resolves the request by using the Gnosis RPC provider to query the data from the SpaceId contract on the Gnosis Chain. The data returned is signed by the gateway and then returned to the Read Client. To add additional security, the gateway signs the response before, so only “trusted” gateways can be use
Docs & Resolver Repo: