Collection of public Bitcoin related datasets.
Datasets about Bitcoin blocks and block headers.
Bitcoin blocks with valid proof of work that fail a named consensus rule, one JSON record per header with the failure reason, evidence and observations. Records come from the P2P network, merge-mined chains and archived block explorers, and CI verifies each record's proof of work and evidence. Useful for studying consensus failures and historical incidents; blocks only reported as invalid are kept in a separate file.
Stale Bitcoin blocks and headers observed on the network, one CSV row per block with height, hash and raw header, plus full blocks where available. Node operators contribute their chain tips from Bitcoin Core's getchaintips RPC, supplemented by fork monitors and block explorer archives. Useful for stale- block rates and propagation studies; listed blocks are not verified to be fully consensus-valid.
Datasets about Bitcoin transactions and the mempool.
Mined Bitcoin transactions that violate Bitcoin Core's standardness policy, one CSV row per transaction with height, mining pool, reason, txid, size and fee details. Blocks are replayed through a Bitcoin Core test node to find transactions its policy would reject. Useful for studying which pools mine non-standard transactions and why; results depend on the policy of the Bitcoin Core version used.
Datasets about the Bitcoin peer-to-peer network: nodes, addresses, propagation.
The node database of achow101's Bitcoin DNS seeder as a text dump, one line per known address with reachability over several time windows, last-seen time, height, services, version and user agent. Written continuously by the dnsseedrs crawler behind the seeder, which asks nodes for addresses and keeps retrying each one. Useful for node counts per network and software adoption; a single live snapshot from one vantage point, without history.
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.
Daily snapshots of the peers connected to KIT's Bitcoin monitoring nodes, one JSON file per day with each peer's services, version, user agent, autonomous system, coarse location, relay statistics and latency. The monitor connects to reachable nodes and records what they relay, following the group's published methodology. Useful for studying the node population and propagation over many years; peer IP addresses are anonymised.
The node database of Will Clark's Bitcoin DNS seeder seed.bitcoin.fish.foo as a text dump, one line per known address with reachability over several time windows, height, services, version, user agent and retry statistics. Written continuously by a dnsseedrs crawler behind the seeder. Useful as an independent vantage point, since this seeder is not hardcoded in Bitcoin Core; a single live snapshot without history.
Exports of reachable Bitcoin nodes from the Bitnod.es node explorer, one CSV file per day with each node's address, port, country, ISP, services, protocol version, user agent and block height, covering IPv4, IPv6, Tor and I2P addresses. The site runs the bitnodes crawler and publishes a cumulative last-seen export per day. Useful for node counts by country, provider and software version; only listening nodes are included.
Timestamps at which blocks arrived at various Bitcoin nodes, one CSV file per node with height, hash and millisecond arrival time. Contributors extract the timestamps from their Bitcoin Core debug logs with the included script, and CI checks them against the block header time. Useful for measuring block propagation delay; coverage differs by node and period.
Snapshots of reachable Bitcoin nodes from a revival of the bitnodes.io crawler, each a JSON document listing every node with version, user agent, services and height across IPv4, IPv6, Tor, I2P and CJDNS, with monthly archives adding geolocation and ASN. The crawler recursively requests addresses from nodes and publishes snapshots through a rate-limited public API and an archive page. Useful for node counts by network, country and software; only listening nodes are counted.
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.
Daily time series on the health of Bitcoin's P2P network: reachable nodes by network type, unique and long-term reachable node estimates, and the quality of addresses served by each DNS seed. Produced by virtu's p2p-metrics- exporter, which crawls the network and queries the DNS seeds. Useful for tracking node counts and DNS seed quality over time; only listening nodes are counted.
Datasets about mining pools, hashrate and coinbase data.
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.
Datasets about Bitcoin software development: repositories, issues, pull requests.
A backup of all issues, pull requests, reviews and comments of the bitcoin- core/gui GitHub repository, where Bitcoin Core GUI changes are developed, one JSON file per issue and pull request as returned by the GitHub API. An automated job refreshes the backup, and a browsable mirror is rebuilt from it. Useful for keeping the development history available independently of GitHub; items GitHub hides or that failed to fetch are listed in state.json.
A backup of all issues, pull requests, reviews and comments of the bitcoin- core/secp256k1 GitHub repository, the libsecp256k1 elliptic curve library used by Bitcoin Core, one JSON file per issue and pull request as returned by the GitHub API. An automated job refreshes the backup, and a browsable mirror is rebuilt from it. Useful for keeping the development history available independently of GitHub; items GitHub hides or that failed to fetch are listed in state.json.
A backup of all issues, pull requests, reviews and comments of the bitcoin/bips GitHub repository, the Bitcoin Improvement Proposals, one JSON file per issue and pull request as returned by the GitHub API. An automated job refreshes the backup, and a browsable mirror is rebuilt from it. Useful for keeping the development history available independently of GitHub; items GitHub hides or that failed to fetch are listed in state.json.
A backup of all issues, pull requests, reviews and comments of the bitcoin/bitcoin GitHub repository, the main Bitcoin Core repository, one JSON file per issue and pull request as returned by the GitHub API. An automated job refreshes the backup, and a browsable mirror is rebuilt from it. Useful for keeping the development history available independently of GitHub; items GitHub hides or that failed to fetch are listed in state.json.
Datasets about the Lightning Network: channels, gossip, routing.
Lightning Network gossip messages as sent and received by instrumented LDK nodes, with microsecond timestamps per message, peer and direction, published as monthly Parquet archives. The collectors connect to peers chosen across network communities and export their captures to Zenodo. Useful for studying gossip propagation, fanout and peer sync behaviour; messages sent by collectors are mostly replies to sync requests, not relays.
Lightning Network gossip history: channel_announcement, channel_update and node_announcement messages as raw bzip2-compressed message streams, one file per snapshot. Extracted after deduplication from the gossip_store files of the authors' c-lightning nodes, with checksums and a reader snippet in the README. Useful for reconstructing the network topology and channel policies at any point in time; gossip is lossy by design, so the collection is best effort.