No Pepecoin support: peppool.space is a mempool fork sitting unused

[oritwoen]

Wanted to check a live Pepecoin prize (Pu5spyDwNEQxmWLkUHv779AWNkpMdQ29SZ) and both tools bounced. chains_lookup("pepecoin") is Unsupported chain. explorers_balance is Unknown chain: pepecoin. Ended up curling peppool.space by hand.

peppool.space is a mempool.space fork. GET /api/address/<addr> returns the same chain_stats / mempool_stats shape Litecoin already uses on litecoinspace.org. For that address just now: funded_txo_sum 5000998512000, spent_txo_sum 5000998512000. Those funded/spent sums are the prize amounts. The named balance field on pepecoinexplorer is junk. /api/v1/address is a 404 (The route api/v1/address/… could not be found.), same trap as guessing an etherscan-style path and reading it as zero.

Litecoin already generalized the mempool provider over CHAIN_BASES. Pepecoin is that same row: a chain class (P… addresses, PEP) plus pepecoin: "https://peppool.space" next to bitcoin/litecoin. Crypto bounty hunts keep landing on PEP addresses and right now the library pretends the chain does not exist.

[meridianmindx]

🎯 Solution Submitted in PR #23

I have submitted a complete solution in PR #23 to serve Pepecoin via the mempool provider (peppool.space).

Implementation Details:

1. Endpoint Routing: Added pepecoin: "https://peppool.space" to CHAIN_BASES in src/providers/mempool.ts.
2. Fee Rate Units: Added pepecoin: "pepetoshi/vB" in FEE_UNITS and updated GasUnit in src/core/types.ts.
3. Provider Registry & Classifier: Registered pepecoin in builtins (src/providers/index.ts) and added pepecoin transaction hash detection in src/core/input.ts.
4. Test Suite: Added unit tests in test/unit/mempool.test.ts (verifying balance fetching for Pu5spyDwNEQxmWLkUHv779AWNkpMdQ29SZ, routing, and gas data) and test/unit/resolve.test.ts (provider auto-selection). All 29 mempool tests pass cleanly.

Base Payout Address: 0xcFDa9f32d292661740a6d0B4c00867E34c05c56D