Address formats¶
Reference for chain-specific address formats accepted by Routes for destinations and deposit addresses.
Scope
This page documents address syntax rules for common chain families. It is not an exhaustive support list. Discover currently supported assets via GET /assets, and treat execution-time availability errors (asset_not_supported, forbidden_asset, not_available) as the final authority.
Supported chains¶
| Chain | Address format | Example | Memo / Tag | Notes |
|---|---|---|---|---|
Bitcoin (btc) |
bech32 (bc1...) |
bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq |
No | P2WPKH and P2WSH accepted |
Ethereum / EVM (evm:<chain_id>) |
0x + 40 hex chars, lowercase |
0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48 |
No | EIP-55 checksums accepted but stored lowercase |
Solana (solana) |
Base58 | 7xKXtg2CW87d97TXJSDpbD5jBkheTqA83TZRuJosgAsU |
No | Case-sensitive |
XRP Ledger (xrpl) |
r-address (base58) | rMxCKbEDwqr76QuheSUMo8s8yrJzPAfBYp |
Tag (policy-dependent) | Tag is protocol-optional, but many receiving platforms require it |
Zcash (zec) |
t-address | t1Rv4exT7bqhZqi2j7xz8bUHDMxwosrjADU |
No | Transparent addresses only |
Bitcoin Cash (bch) |
CashAddr | bitcoincash:qr... |
No |
Notes¶
- EVM addresses are canonicalized to lowercase by Routes. Mixed-case (EIP-55) checksummed addresses are accepted on input but stored and returned in lowercase.
- Solana addresses are case-sensitive base58. Do not lowercase them.
- XRPL destination tags are integers. Pass them in the
tagfield — do not embed them in the address string. Tags are protocol-optional on XRPL, but often required by custodial receiving platforms. - Address validation occurs at destination registration time. Invalid addresses are rejected with
400 invalid_parameter.