Chains

Every chain answers the same fields and the same assertAddress. What changes is the encoding underneath and the small decisions that make a check honest: which version bytes are mainnet, whether a checksum is verified or only decoded past, what a testnet form looks like. Those decisions are the part nobody writes down, so each page here does.

Families

EVM is fourteen chains with one address format, one coin type and a chainId each. UTXO is twelve chains and six encodings: Bitcoin, Litecoin and Bitcoin Gold share the SegWit rules under different prefixes, Pepecoin, Dogecoin, Bitcoin SV and Dash are Base58Check only, Bitcoin Cash and eCash are CashAddr under their own prefixes, Cardano is CIP-19 over Bech32 plus Byron's CBOR, Decred writes two version bytes, Zcash has four address forms and scrambles the newest one with F4Jumble. Move is Aptos and Sui with 64 hex digits or a single digit short form. The other eight, Solana, Stellar, XRP Ledger, TON, TRON, Octra, Arweave and Monero, are families of one, each with its own encoding and its own class.

What every page says

• The record at the top is read off the class in your browser, so it can't drift from the code. The full chains_lookup answer sits behind its last row.
• The address section names the forms the validator accepts, what it decodes and verifies, and what it leaves alone. A checksum that isn't verified is said out loud.
• The spellings line is every input getChain resolves to that chain: the key, the display name and the aliases.