Chains

Dogecoin

Base58Check under 0x1e and 0x16, 25 bytes, no Bech32. The script version is the one Pepecoin kept, so a 9 or A address fits both chains.
IDdogecoin31 / 36utxo · DOGE
Chain / UTXO

Dogecoin

"dogecoin""doge""Dogecoin"

Symbol
DOGE · 8 decimals
Coin type
3
CAIP-2
bip122:1a9…fe82
Checks
address · txid
fields set 7 / 9

Network

CAIP-2bip122:1a91e3dace36e2be3bf030a65679fe82
Magicc0c0c0c0
PoWscrypt
RPCnone
Explorerblockchair.com/dogecoin

Access

Createcreate("dogecoin")
ResolvegetChain("doge")
CLIchains info doge
Tryplayground with a sample address

Address format

Base58Check only. D… is version 0x1e, 9… and A… are 0x16, 25 bytes either way with the checksum verified. There's no Bech32 branch: SegWit sits in the node's deployment table with its timeout set to zero, so it never switched on and no witness address exists to check.

0x16 is also Pepecoin's script version, because Pepecoin forked Dogecoin and kept it. The same 25 bytes are an address on both chains, and identify names both for a 9… or A… instead of guessing. A D… address is Dogecoin's alone.

ts
import { getChain } from "@agntn/chains";

const chain = getChain("doge");
chain.assertAddress("DH5yaieqoZN36fDVciNyRueRGvGLR3mr7L"); // returned unchanged
chain.bip44; // 3
chain.caip2; // "bip122:1a91e3dace36e2be3bf030a65679fe82"

Spellings

dogecoin, doge, Dogecoin. The key is dogecoin, the rest resolve through getChain.