[BOUNTY] for devloping/writing a script/code/program to dump all publickeys

[amaclin]

Yes, i need those pubkeys from outputs & inputs, only uncompressed , no pay to hash160 or multisig , only the available known pubkeys, for example :

OK, I'll try to do it today. But why do you need only uncompressed?
There are more compressed pubkeys 02xxxxx and 03xxxxx in blockchain

If you can ( if its possible ) uncompress them it would be great!

Public keys should not be converted!
For example:

public key for address 1JwSSubhmg6iPtRjtyqhUYYH7bZg3Lfy1T:

Code:

0478D430274F8C5EC1321338151E9F27F4C676A008BDF8638D07C0B6BE9AB35C71A1518063243ACD4DFE96B66E3F2EC8013C8E072CD09B3834A19F81F659CC3455

and compressed public key for address 1C7zdTfnkzmr13HfA2vNm5SJYRK6nEKyq8

Code:

0378D430274F8C5EC1321338151E9F27F4C676A008BDF8638D07C0B6BE9AB35C71

both these public keys (and addresses) are derived from one private key

Code:

C4BBCB1FBEC99D65BF59D85C8CB62EE2DB963F0FE106F483D9AFA73BD4E39A8A

[XaiZou]

Yes, i need those pubkeys from outputs & inputs, only uncompressed , no pay to hash160 or multisig , only the available known pubkeys, for example :

OK, I'll try to do it today. But why do you need only uncompressed?
There are more compressed pubkeys 02xxxxx and 03xxxxx in blockchain

If you can ( if its possible ) uncompress them it would be great!

Public keys should not be converted!
For example:

public key for address 1JwSSubhmg6iPtRjtyqhUYYH7bZg3Lfy1T:

Code:

0478D430274F8C5EC1321338151E9F27F4C676A008BDF8638D07C0B6BE9AB35C71A1518063243ACD4DFE96B66E3F2EC8013C8E072CD09B3834A19F81F659CC3455

and compressed public key for address 1C7zdTfnkzmr13HfA2vNm5SJYRK6nEKyq8

Code:

0378D430274F8C5EC1321338151E9F27F4C676A008BDF8638D07C0B6BE9AB35C71

both these public keys (and addresses) are derived from one private key

Code:

C4BBCB1FBEC99D65BF59D85C8CB62EE2DB963F0FE106F483D9AFA73BD4E39A8A

oh yes, so i need both cmpr. and ucmpr. , no need for mutltisig. thanks

[waldistons]

Using RPC approach will take you ~3-4 weeks. I'm currently farming just addresses used, my app is runing almost a week and i'm 5 days away to block 300000. (the newer the block, the more transactions in block)

[XaiZou]

Using RPC approach will take you ~3-4 weeks. I'm currently farming just addresses used, my app is runing almost a week and i'm 5 days away to block 300000. (the newer the block, the more transactions in block)

You can use blockparser to dump all bitcoin addresses down to the last Satoshi + the 0 balance used addresses within 30 min.

[waldistons]

Compute and print the balance for all keys ever used in a TX since the beginning of time (30 seconds)

I call those 30 seconds bullshit and let me explain why:

1) current blockchain size is 43.5 GB (all blk*.dat files)
2) even keeping blockchain on ssd, most ssd disks have THEORETHICAL read speed 500 MB/s
3) let's assume they work with max theorethical speed: 500 MB/s * 30 seconds = 15 GB will be read

UNLESS:
a) code doesn't read whole blocks and parses only small part of block size
b) raid of SSD disks, can give couple GB/S read speeds.

Please correct me if I'm wrong.

[XaiZou]

Compute and print the balance for all keys ever used in a TX since the beginning of time (30 seconds)

I call those 30 seconds bullshit and let me explain why:

1) current blockchain size is 43.5 GB (all blk*.dat files)
2) even keeping blockchain on ssd, most ssd disks have THEORETHICAL read speed 500 MB/s
3) let's assume they work with max theorethical speed: 500 MB/s * 30 seconds = 15 GB will be read

UNLESS:
a) code doesn't read whole blocks and parses only small part of block size
b) raid of SSD disks, can give couple GB/S read speeds.

Please correct me if I'm wrong.

who said 30 sec 

[waldistons]

Quote was from original readme file

[XaiZou]

Quote was from original readme file

ah, that readme file is old i think. 

[unhappyuser]

Oh, that one is not solved yet?... I can try make an another callback for znort blockparser, if this will be good for you.

[XaiZou]

Oh, that one is not solved yet?... I can try make an another callback for znort blockparser, if this will be good for you.

Great, ill be waiting!

[unhappyuser]

Great, ill be waiting!

But, please... why you are not accepting a knightdk solution? Are you tried to use more RPC threads and point bitcoind to unresponsive proxy address? Maybe you can get better results.

[XaiZou]

Great, ill be waiting!

But, please... why you are not accepting a knightdk solution? Are you tried to use more RPC threads and point bitcoind to unresponsive proxy address? Maybe you can get better results.

Yes, im using rpcthreads=1000 and the connection is direct no proxy ( all localhost ) but it is very slow.

Maybe you can play with blockparser rawdump.cpp , transaction scripts code is there. but need some cleanup from other unwanted things.

[achow101]

Great, ill be waiting!

But, please... why you are not accepting a knightdk solution? Are you tried to use more RPC threads and point bitcoind to unresponsive proxy address? Maybe you can get better results.

Yes, im using rpcthreads=1000 and the connection is direct no proxy ( all localhost ) but it is very slow.

Maybe you can play with blockparser rawdump.cpp , transaction scripts code is there. but need some cleanup from other unwanted things.

Yeah, I know my solution was very very slow. I will update it to do multiple threads and see if that works any faster. It was running on a single thread.

[achow101]

Here is another version of mine. It still requires txindex but this time it will do multithreading to hopefully run faster.

usage:

Code:

Tool which scrapes the entire blockchain for all of the pubkeys of all transactions
Requires bitcoind (or Bitcoin Core with daemon enabled) and txindex=1 to be set in Bitcoin.conf
Usage: pubkeyscraper <rpcuser> <rpcpassword> [threads] [rpcport] [rpcurl]
<rpcuser>		Required. User of the Bitcoin-RPC server set in bitcoin.conf
<rpcpassword>		Required. Password of the Bitcoin-RPC server set in bitcoin.conf
[threads]		Optional. Number of threads to run, should be the same as the number of rpcthreads of the Bitcoin-RPC server. Default 4.
[rpcport]		Optional. Port of the Bitcoin-RPC server set in bitcoin.conf. Default is 8332
[rpcurl]		Optional. URL or IP address of Bitcoin-RPC server. Default is http://127.0.0.1

Download: https://drive.google.com/file/d/0Bxw3ip9QfNOUY3EwS0Z3RUxqanc/view?usp=sharing

[btc_enigma]

I am writing a much faster version that reads blocks from disk ... using bitcoinabe and bitcointools. Please wait for my submission before releasing bounty

-Thanks

[btc_enigma]

Here is the script https://github.com/shivaenigma/bitcoin-abe

Directly reads blocks from bitcoin data directory. Prints some debug information on console like current block hash and 'Found x public keys' . You can redirect stdout to /dev/null for speed up

My bitcoin address to claim bounty is in my profile

-  Thanks

[photon_coin]

many have done this & a while ago there was a website with them,

not sure of the purpose since it is a long list

suggested reading :

bitcoin wiki & http://crypto.stackexchange.com/questions/1170/best-way-to-reduce-chance-of-hash-collisions-multiple-hashes-or-larger-hash

[btc_enigma]

XaiZou have you tried to out the script ?  Waiting for a response

[btc_enigma]

Typical of a new member , announcing bounty and then disappearing !  Should have asked for an escrow . What a sham !

 I will wait for a day ... else I will give XaiZou a negative trust and ask moderator to ban the userid

[unhappyuser]

I think there is must be a rule where user at least must sign a message using private BTC address which contains enough funds for covering an announced bounty...