ENS Subname Compatibility Integration

General Technical
1

GhostAgent.ninja × Genome

Hi
We’ve been exploring ENS compatibility for our subname mints and would like to ensure we align with Genome’s canonical registry architecture rather than building parallel infrastructure.

Specifically:

  1. Canonical Registry Integration Can third-party registrars (like ours) write subnames directly to Genome’s canonical registry? If so, what’s the authorization process?
    eg: on SpaceID we minted openclaw.gno = openclaw.gnosis.eth
    USing our registry factory contract we can mint: freshbot.openclaw.gno currently

  2. dm3 CCIP-Read Resolver Does the dm3 bridge read from a specific PublicResolver contract on Gnosis Chain? Would our subnames need to be written there to resolve as .gnosis.eth on Ethereum mainnet?

  3. Partnership Path Is there a formal integration program for projects building on GNS/Genome?