GIP-90: Should Gnosis.eth update its ENS resolver to resolve .GNO domains on Gnosis Chain?

Governance GIPs
1

GIP-90: Should Gnosis.eth update its ENS resolver to resolve .GNO domains on Gnosis Chain?

  • In Favour
  • Against
0 voters 
GIP: 90
title: Should Gnosis.eth update its ENS resolver to resolve .GNO domains on Gnosis Chain?
author: Ralph, Philipp
status: Phase-2
type: Meta
created: 2023-11-01

Executive Summary

.GNO domains is launching on Gnosis Chain, with one of the key features being a CCIP resolver that resolves .GNO domains on ENS. For this to be implemented gnosis.eth is required to update its resolver to the new CCIP resolver being developed.

Introduction

We at Gnosis have been working with SpaceID, and DM3 protocol to bring .GNO domains to Gnosis. We call it Genome.

Genome’s 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.

Product Features:

  • .GNO domains integrated with the Gnosis ecosystem
  • Genome .GNO NFT collection native to Gnosis
  • Developing a CCIP resolver enabling .GNO domains to be resolved on ENS
  • .GNO Integration with current and future JV (Space-ID) partners

Genome is live on testnet! https://test.genomedomains.com/

ENS Resolver Features:

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. ENS’ explainer on CCIP: https://docs.ens.domains/dapp-developer-guide/ens-l2-offchain . And, our CCIP resolver in this case: https://github.com/dm3-org/genome-ccip-resolver (only deployed on Gnosis testnet so far)

Now, each example.gnosis.eth subdomain will also have an example.gno domain. Those are centrally managed by Space-ID.

Both are linked.

.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 used

Impact and Benefits

The main goal of Genome and .GNO domains is increasing ease of access to new and existing users alike. With the increasing costs of building on Ethereum, allowing .GNO domains to resolve on ENS not only lowers costs for owning a domain but also opens up a new set of possibilities for experimentation.

Proposed Changes / Implementation Plan

ENS records for gnosis.eth need to be updated to set the resolver to Genome’s resolver address ( GitHub - dm3-org/genome-ccip-resolver)

Team/ Organization/References

Ralph Xu, Gnosis Builders
Philipp, Gnosis Builders
Alex Plutta, DM3 Protocol/Corpus Ventures
Eduardo Vega-Patiño, DM3 Protocol/Corpus Ventures

Gnosis Snapshot

Phase 2 Proposals: Please ignore this section, and leave as is. It is used for Phase 3 proposals.
Phase 3 Proposals: Add a link to the corresponding Gnosis Snapshot poll you’ve created.

2 Likes