Integration guidelines

Input handling

Preserve the user's raw input long enough to validate case-sensitive wallet formats. Apply canonical Hyndle normalization only after literal-address and protected-identifier checks.

Resolution order

1. Detect a supported literal blockchain address.
2. Use a valid literal address directly.
3. Normalize and resolve a Hyndle name only when address detection fails.

Ownership

Blockchain ownership is authoritative after mint. Read current lifecycle state and the active ownership generation before trusting resolver records.

Network records

EVM-compatible networks can share the same 20-byte address record. Bitcoin, Solana, Tron, TON, XRP Ledger, NEAR, Aptos, Tezos, and Hedera require network-specific records and validation.

Secrets

Never send a private key, recovery phrase, wallet credential, or signing secret to a name-resolution API. Hyndle resolution requires only public names and public address records.

Availability

API and SDK pages marked as unavailable describe planned interfaces, not production services. Integrate only against versions and origins explicitly published as available.