Multichain resolution

Hyndle is designed so one name can hold records for multiple networks. Resolution support must be distinguished from network marketing claims: a chain is supported only when the resolver, application, and integration path are available and tested.

EVM networks

EVM-compatible networks share the same 20-byte account format. A single EVM address record can be useful across Base, Robinhood Chain, Ethereum, Arbitrum, Optimism, Polygon, BNB Chain, Avalanche, and other compatible networks.

Non-EVM networks

Bitcoin, Solana, Tron, TON, XRP Ledger, NEAR, Aptos, Tezos, and Hedera use network-specific address formats. They require separate resolver records, validation rules, and integration testing.

These network records are introduced individually. Use only record types shown as available in the official Hyndle application. See Network availability.

Owner-published non-EVM records remain visibly unverified until a network-specific proof confirms control of the destination address. See Public name profiles.

Ownership generations

Records are isolated by ownership generation. A transfer or reclaim begins a new generation, preventing the new owner from accidentally publishing records configured by a prior owner.

Integration principle

Applications should read the current owner, lifecycle state, and current-generation resolver records from the configured contracts at a consistent block when possible.

When handling user input, applications must test supported literal address formats before attempting Hyndle name resolution. A valid blockchain address is an address, not a resolvable Hyndle name.