Skip to content
Logo

Protected external namespaces

Hyndle rejects names that end with a protected external Web3 namespace. This prevents a Hyndle identity from impersonating or conflicting with a name issued by another protocol.

Examples that are rejected include:

vitalik.eth
alice.crypto
pay.bnb
name.arb
identity.sol
identity.btc
identity.gram
profile.base
profile.hood
profile.bera
profile.abs
profile.hl
profile.nad
profile.mega
profile.celo
name.op

Protected names are rejected during search and cannot be reserved or minted through Hyndle.

Near matches

A protected suffix is matched as a complete final label. A bare word such as ethereum is not automatically rejected merely because it contains eth as part of the word.

Current protected suffixes

The current policy protects these complete final labels:

  • ENS: .eth
  • Unstoppable Domains and partner namespaces: .x, .polygon, .nft, .crypto, .blockchain, .bitcoin, .dao, .888, .wallet, .binanceus, .hi, .klever, .kresus, .anime, .manga, .go, .zil, .coin, .web3
  • SPACE ID and partner namespaces: .bnb, .arb, .inj, .manta, .cake, .taiko, .zkf, .mode, .sei, .gno, .zeta, .mint, .merlin, .floki, .burger, .alien, .ail, .ll, .tomo, .four, .g, .ip, .mph, .duck, .0g, .mito, .wod
  • TRON ecosystem naming: .trx, .tron, .usdd, .tns
  • TON ecosystem naming: .ton, .gram
  • HoodDomains on Robinhood Chain: .hood
  • Beranames on Berachain: .bera
  • Abstract Name Service on Abstract: .abs
  • Hyperliquid Names on HyperEVM: .hl
  • Nad Name Service on Monad: .nad
  • MegaNames on MegaETH: .mega
  • Precautionary re-additions (see below): .op, .lin, .scroll, .blast, .mnt, .zr, .era, .mon
  • Other established namespaces: .sol, .btc, .near, .apt, .sui, .tez, .algo, .avax, .stark, .xrp, .hbar, .base, .celo

This is a product-safety summary of the enforced list. The protocol can expand the list when another public naming namespace creates a credible collision risk. Every change requires a database collision review before enforcement.

.base is blocked as a precaution against identity and integration confusion with the Basenames (Coinbase) ecosystem, not because .base is itself an official Basenames product suffix. Basenames registrations actually take the form name.base.eth, an ENS subdomain of base.eth already covered by the .eth entry above. This is a namespace-collision rule, not a statement about Hyndle's settlement chain: a name ending in .base cannot be registered through Hyndle regardless of which chain Hyndle's own contracts are deployed to.

.hood is blocked because HoodDomains issues .hood names on Robinhood Chain. HoodDomains describes itself as an independent naming service and is not endorsed by Robinhood Markets. The protection prevents identity collisions; it does not imply a partnership or endorsement.

.bera is blocked because Beranames issues .bera names on Berachain, an ENS-compatible, NFT-backed name service. The protection prevents identity collisions; it does not imply a partnership or endorsement.

.gno is Gnosis Chain's own naming service (Genome, built with SPACE ID), confirmed directly against Gnosis Chain's official documentation, not an unrelated network that happens to share a SPACE ID integration.

.abs, .hl, .nad, and .mega are blocked for the same reason as .bera and .hood: each is a real, active, independently-verified naming service issuing names on Abstract, HyperEVM (Hyperliquid), Monad, and MegaETH respectively. None of these implies endorsement by the underlying chain's foundation; several of these services explicitly state they are independent projects.

.celo is blocked for the same reason as .base: Celonames' actual registrations take the form name.celo.eth, an ENS subname already covered by the .eth entry, not a literal .celo suffix. Blocked as a precaution against identity/integration confusion, not because Celonames itself issues a bare .celo name.

.op (Optimism), .lin (Linea), .scroll (Scroll), .blast (Blast), .mnt (Mantle), .zr (Zora), .era (zkSync Era), and .mon (Monad) were each verified to have a real naming-service project at some point, but every frontend for these was unreachable (DNS failure, or an expired/parked domain) when last checked. They are blocked precautionarily rather than dropped: real historical registrations may already exist on-chain regardless of frontend status, and any of these could relaunch under new hosting without Hyndle's protection list noticing in time. This is a deliberately conservative choice, not a claim that these services are currently operable.

Where protection is enforced

Protection is checked by the server during availability lookup, reservation creation, payment-intent issuance, administrative approval, and mint-authorization issuance. A client-side warning is not the security boundary.

The blockchain registry stores deterministic name identity, but complex external namespace policy is enforced before the mint signer issues an authorization.

Separate from wallet-address protection

Suffix protection prevents collisions with other naming systems. Hyndle also rejects literal blockchain addresses and payment identifiers as names. See Protected wallet identifiers.