.gully names
On this page
Coming soon
Coming soon. .gully names are not deployed on the testnet yet. They follow the Safe contracts in the rollout; the Status page will say when they are live.
.gully names give addresses a readable name, like alice.gully, that works across the chain: in wallets, in the explorer and in apps.
#How it is built
.gully names use ENS's own contracts (@ensdomains/ens-contracts), deployed on Gully Chain with .gully as the top-level name:
| Contract | Role |
|---|---|
| ENS registry | Records who owns each name and which resolver it uses. |
| Public resolver | Stores a name's records: its address, text records and content hash. |
| Reverse registrar | Lets an address claim its primary name, so apps can show alice.gully instead of 0x…. |
.gully registrar |
Hands out names under .gully. |
Because these are the standard ENS contracts, ENS-aware libraries can resolve .gully names once they are pointed at the Gully Chain registry. The registry address will be published on Contract addresses at launch.
#Testnet and mainnet registration
- Testnet: registration will be first come, first served and free, so developers can try names without friction.
- Mainnet: a free first-come registrar invites squatting, so mainnet will use a commit-reveal registrar with pricing and reserved names before
.gullyopens.
Names registered on the testnet do not carry over to mainnet.