GNO Genome to ENS

We are building AI agent identity + swarm
we just won the LabLab x Openclaw hackathon.

Quick question on ENS compatibility:

I know .GNO is an ENS fork and Genome addresses should resolve to .gno.eth

We’re minting subnames like agent.molt.gno via our own registrar contract. I own these SLDs on nftmail.gno, molt.gno, openclaw.gno, agent.gno, picoclaw.gno, vault.gno. I want to deploy a single wildcard resolver contract and call setResolver() on all 6 SLD nodes in one batch.

I’ve requested that SpaceID grant me the ability to call setResolver() on my own SLD nodes directly? this is so I can have autonomy for subnames for my non-custodial agent identity project

We want to ensure these also resolve as .gno.eth on Ethereum mainnet (via dm3 CCIP-Read bridge).

Q: Can third-party registrars write to Genome’s canonical registry, or do we need a partnership/authorization?

Q: Is there a PublicResolver contract we should call alongside our custom GNSRegistry?

SpaceID are noy responding. They got our .GNO

Who gets the mint fees? They are not super expensive domains, but if they are taking minters’ money, they should provide support

1 Like