ENS (Name Service)
Overview
ENS support exists in contract registry code and shared ENS hooks/utilities. Arbitrum and Sepolia artifacts include Green Goods ENS registry addresses, while Celo keeps the module address at zero. Green Goods ENS events are not currently configured in the indexer, so chain claims should stay resolver/indexing-aware.
Builder notes
- Use shared ENS hooks for address, avatar, name, registration status, and Green Goods ENS reads.
- Keep docs clear about whether a chain has deployed ENS wiring or only implementation support.
- Do not hardcode ENS names or resolver addresses outside deployment/config sources.
Next page
Next best action
Deployment artifacts decide which ENS surfaces are active for a chain.
Deployment status