Chains
Dash
Base58Check under 0x4c and 0x10, 25 bytes, no Bech32. Its own genesis, so unlike the Bitcoin forks it gets a CAIP-2 reference.
Chain / UTXO
Dash
"dash""Dash"
- Symbol
- DASH · 8 decimals
- Coin type
- 5
- CAIP-2
- bip122:000…e637
- Checks
- address · txid
fields set 7 / 9
Network
- CAIP-2
bip122:00000ffd590b1485b3caadc19b22e637 - Magic
bf0c6bbd - PoW
x11 - RPC
none - Explorerinsight.dash.org/insight
Access
- Create
create("dash") - Resolve
getChain("dash") - CLI
chains info dash - Tryplayground with a sample address
Address format
Base58Check only. X… is version 0x4c, 7… is 0x10, 25 bytes either way with the checksum verified. That's the whole of Dash Core's DecodeDestination: it tries base58, checks the two prefixes, and gives up. Dash never took SegWit, so there's no Bech32 branch to check.
Testnet moves both bytes, 0x8c writes y… and 0x13 writes 8…, and both fail here. No other chain in the registry uses 0x4c or 0x10, so identify names Dash alone for a mainnet address.
The chain started from its own genesis block in 2014, not from a Bitcoin fork. So the CAIP-2 reference is plain BIP-122: the first 32 hex digits of the genesis hash that chainparams.cpp asserts.
import { getChain } from "@agntn/chains";
const chain = getChain("dash");
chain.assertAddress("XjszN1jZJthEoaQDhGthRkaHL9AqaG3Vzw"); // returned unchanged
chain.bip44; // 5
chain.caip2; // "bip122:00000ffd590b1485b3caadc19b22e637"
Spellings
dash, Dash. The key is the ticker too, so there's no alias to learn.