3 ms·
It's all very adhoc. I used gdb to dump the bitcoind memory, I'm using https://github.com/matja/bitcoin-tool https://github.com/matja/bitcoin-tool to output hu
by jstanley 9y ago
It's all very adhoc.
I used gdb to dump the bitcoind memory, I'm using https://github.com/matja/bitcoin-tool https://github.com/matja/bitcoin-tool to output human-readable addresses, I'm using (a modified version of) https://github.com/tenthirtyone/blocktools https://github.com/tenthirtyone/blocktools to parse the blockchain files, and some custom scripts to extract addresses from the scriptpubkeys and compare them against my list of addresses taken from the bitcoind memory.
- StavrosK 9y agoI see, thanks. Wouldn't it be easier to communicate with bitcoind via the RPC interface?
- jstanley 9y agoYes but that is orders of magnitude too slow. It would be fine if bitcoind had an address index, but it does not. I need to setup a bitcore node one of these days...
- StavrosK 9y agoNot only that, it doesn't even support looking up arbitrary addresses, I've just found. I'm looking for an alternate method.
- ryan-c 9y agoI extract them from bitcoind's rpc interface by dumping blocks, but i started that process years ago. It'd take several months to dump everything from scratch at this point.