I understand that it goes upto hash160 function only but public keys are generated at very starting stages so writing private keys and public keys is possible.
Is there any implementation of same in python or c or any low level language like brainflayer had. So it can be modified accordingly. Brainflayer speed for incremental private keys is less than 500k/s . Or if anyone knows any such private key public key database already built for some keyspace .
Hi guys ,
Can this tool or any modification of this be modified to write all private keys and respective uncompressed private keys and addresses) in range 1 to 56BC75E2D630FFFFF as a csv file . Since it generates 700 to xxxx million keys /s in some of its versions , so it will take many years on a single machine. But still looking for solutions. Writing regular outputs will consume too much time
So better it will save several millions or billions in some sort of memory operation and then write them once , till then next batch will find its space in memory to be written again.
Can this tool or any modification of this be modified to write all private keys and respective uncompressed private keys and addresses) in range 1 to 56BC75E2D630FFFFF as a csv file . Since it generates 700 to xxxx million keys /s in some of its versions , so it will take many years on a single machine. But still looking for solutions. Writing regular outputs will consume too much time
So better it will save several millions or billions in some sort of memory operation and then write them once , till then next batch will find its space in memory to be written again.
If I understand you correctly, you are saying that Bitcrack should write the address of each private key it finds to a file?
How would that speed up key searching? Bitcrack doesn't even encode addresses anyway (it only decodes them to RIPEMD160 hash at the beginning of a search) so modifying it to make an address out of every address it finds will slow it down.
I agree with write to file make bitcrack slowly
both technic open file and write file each key or collector on memory and write one same work slow
(write to file use low memory and write one use large memory too)
if you need write to file on this case it no need to use bitcrack just use any python script write to file it fast same your want both random and running number
I try already like python write file private key 1 million per 4 minute (up to harddisk or SSD storage)
if you want to collect private key is use a log of storage to keep it too. plan text file is very small but when have billions trillion line use some space
64 billion private key data use 4TB disk, how many you need to keep
most decide to scan and let it go
) is available at 
It stands at 7.5MB large, not bad for a fatbinary with nine different arch versions in it. However this also gives me the misaligned address error on my T4, but now that I have it here I can finally diagnose it.
Waiting your results with excitement 
it was 