Note: This is a fork of rusty-blockparser
Dump bitcoin signatures and original messages
- Added
sigdump
callback
All you need is Rust, which can be installed using rustup.
cargo build --release
It is important to build with --release
, for better performance!
cargo run --release -- sigdump --help
USAGE:
rusty-blockparser sigdump <dump-folder> <bitcoin-folder>
FLAGS:
-h, --help Prints help information
-V, --version Prints version information
ARGS:
<dump-folder> Folder to store csv files
<bitcoin-folder> Path to the .bitcoin folder
To dump all ecdsa signatures and original messages from the Bitcoin chain, do the following.
First install Bitcoin core and run it with transaction indexing enabled:
bitcoin-qt -txindex=1
During the first run, make sure to note where the bitcoin folder is.
By default, it will be in ~/.bitcoin
.
Make sure to disable chain pruning when asked. There may be a checkbox to disable on first run of bitcoin-qt
.
To dump signatures and messages that were synced so far,
using the bitcoin folder and to dump them in the dump folder,
use the sigdump
callback as in the following example:
$ cargo run --release -- sigdump ./dump-folder ~/.bitcoin
[8:41:53 UTC] INFO - main: Starting rusty-blockparser v0.8.1 ...
[8:41:53 UTC] INFO - index: Reading index from /home/nils/.bitcoin/blocks/index ...
[8:41:53 UTC] INFO - index: Got longest chain with 1 blocks ...
[8:41:53 UTC] INFO - blkfile: Reading files from /home/nils/.bitcoin/blocks ...
[8:41:53 UTC] INFO - parser: Parsing Bitcoin blockchain (range=0..) ...
[8:41:53 UTC] INFO - callback: Using `sigdump` with dump folder: ./dump-folder ...
[8:41:53 UTC] INFO - parser: Done. Processed 1 blocks in 0.00 minutes. (avg: 1 blocks/sec)
[8:41:53 UTC] INFO - callback: Done.
Dumped all 1 blocks:
-> transactions: 1
-> inputs: 1
-> outputs: 1
[8:41:53 UTC] INFO - main: Fin.
A CSV file will be created in the dump folder. This output file will contain, on each line:
r;s;pubkey;txid;message_hash;block_time