Skip to content
Logo

Protected wallet identifiers

Hyndle does not allow a literal blockchain address or payment request to become an ownable name. This prevents an attacker from registering an address-shaped identity that could be mistaken for the original payment destination.

What is rejected

The policy covers validated formats for the networks Hyndle supports or plans to support:

  • 20-byte Ethereum and EVM addresses
  • Bitcoin Base58Check, SegWit, and Taproot addresses
  • Bitcoin Lightning invoices, offers, and LNURL values
  • 32-byte Solana public addresses
  • Tron Base58Check addresses
  • TON user-friendly addresses
  • XRP Ledger classic and X-addresses
  • NEAR implicit accounts
  • canonical Aptos account addresses
  • Tezos implicit and originated accounts
  • Hedera account identifiers

Wallet secrets such as private-key-shaped values, WIF keys, extended private keys, secret-key arrays, and recovery-phrase-shaped input are also rejected.

Exact validation, not prefix blocking

Hyndle does not reject a name merely because it starts with familiar characters. A candidate must satisfy the relevant address codec, length, network, and checksum rules where that format provides a checksum.

Examples of ordinary names that remain valid under the wallet-identifier policy:

0xhello
1bitcoin
bc1fan
tronix
tonality
anything.you.want

A valid address embedded inside a dotted name is still rejected. This prevents wrappers such as pay.<wallet-address> from bypassing the policy.

Security boundaries

The server checks the raw, case-preserving input before normalizing a name. This matters because Base58 and other address encodings can be case-sensitive.

Checks run during availability lookup, reservation creation, payment-intent issuance, administrative approval, and mint-authorization issuance. Users must never paste private keys or recovery phrases into a name field.

Resolver precedence

Applications should process input in this order:

  1. Test whether the value is a valid literal address for a supported network.
  2. If valid, handle it directly as an address.
  3. Only attempt Hyndle resolution when literal-address validation fails.

This rule prevents a wallet from interpreting a real address as an ownable name.