Chains
Pepecoin
Base58Check under 0x38 and 0x16, 25 bytes, no Bech32. The native PEP coin, not an ERC-20 token of the same name.
Chain / UTXO
Pepecoin
"pepecoin""pep""Pepecoin"
- Symbol
- PEP · 8 decimals
- Coin type
- 3434
- CAIP-2
- bip122:379…e9a0
- Checks
- address · txid
fields set 7 / 9
Network
- CAIP-2
bip122:37981c0c48b8d48965376c8a42ece9a0 - Magic
c0a0f0e0 - PoW
scrypt - RPC
none - Explorerpeppool.space
Access
- Create
create("pepecoin") - Resolve
getChain("pep") - CLI
chains info pep - Tryplayground with a sample address
Address format
Base58Check only. P… is version 0x38, 9… and A… are 0x16, 25 bytes either way with the checksum verified. There's no Bech32 branch: the fork inherited Dogecoin's SegWit deployment, which timed out, so there's nothing to check. 0x16 is Dogecoin's script version too, and it stays because Pepecoin has no other one, so identify names both chains for a 9… or A….
This is the native PEP coin with eight decimals. An ERC-20 token called PEPE on Ethereum is a different thing with a different address format, and this class doesn't describe it.
import { getChain } from "@agntn/chains";
const chain = getChain("pep");
chain.assertAddress("PftB3JYp6r3PPkiLPoPoT6vdS77NR4mhyb"); // returned unchanged
chain.type; // "utxo"
chain.caip2; // "bip122:37981c0c48b8d48965376c8a42ece9a0"
Spellings
pepecoin, pep, Pepecoin. The key is pepecoin, the rest resolve through getChain.