bitcoin-data

Tag: addresses

3 datasets

ASMap files for Bitcoin Core

Maps from IP address ranges to autonomous system numbers, encoded for Bitcoin Core's asmap option, with one filled and one unfilled binary file per run, organised by year, plus a copy of the latest map at the repository root. Each map is created collaboratively by several participants from RPKI, IRR and routing data using kartograf, and verified and PGP-attested before merging. Useful for diversifying peer selection by network operator rather than by IP prefix and for studying how Bitcoin nodes are distributed across autonomous systems; reproducing a map requires the kartograf version used at the time.

getrawaddrman exports

Daily exports of the address manager of Bitcoin Core nodes via the getrawaddrman RPC, one JSON file per node with every known address and its metadata, with history in the git log. A scheduled job fetches the exports from the peer.observer nodes and commits them. Useful for studying address propagation and addrman churn; the nodes are a small sample with their own connectivity.

Mining pools

Known Bitcoin mining pools with their coinbase tags and coinbase output addresses, one JSON file per pool, for mainnet and signet. Maintained by hand from pool announcements and observed coinbases, with combined files generated for downstream tools. Useful for attributing blocks to pools; attribution is heuristic, and pools change tags, addresses and infrastructure.