Bitcoin Network Transaction Inv Data with Java Timestamp and Originator Id

The data is a gz compression of a csv file with the following layout:

<timestamp in ms>,<originator id as sha-256 hash in hexadecimal string representation>, <hash of BTC Transaction in hexadecimal string representation>

Example lines:

1547779473468,6cf1100aaccec75da23995512fc7c7a5b6e25224f5903af011e78691c03d0455,a73578820a41aa6180621bcd90af1997c88794b33d8db2f004ee37c3e09b10ec
1547779473468,6cf1100aaccec75da23995512fc7c7a5b6e25224f5903af011e78691c03d0455,0beb35a4338b026fb4ceb0d215d372f67dfb0c73f1e21157e03dde2fbc6b94ee

The data was gathered with a modified version of bitcoinj 0.14.7. The modification consisted of:

• Blinding Originator IP+Port by hashing with a key generated at application startup
• Logging every Transaction Inv message to a file

The application running the modified library just consisted of creating a Peer Pool of at most 6000 connections and limiting broadcasting to require 100000 connections, set via bitcoinj parameters.

The data of crawler-82GB.gz was gathered between 17.01.2019, 15:30 and 18.01.2019, 03:00 at Ulm University in Ulm, Germany. The data of crawler-01-02-2019-09-54-59-ULM.csv.gz was gathered on 01.02.2019 at Ulm Iniversity in Ulm, Germany as well.

The data of crawler-24.01.2019-*.gz was gathered between 24.01.2019, 10:00 and 25.01.2019 10:00 on Microsoft Azure instances. The selected region of Azure is indicated in the filename: UK, South; US, East; Southeast Asia.

The datasets of crawler-06.02.2019-*-SIMUL.csv.gz were gathered with the same runtime key so ID's can be linked within the datasets. Locations again are Ulm University, Germany, and Azure UK, South (GBS); US, East (USA); Southeast Asia (SEA).

ETH-crawler-20+21.02.2019.csv contains a similar collection of the Ethereum network for comparisson.