Search content
Sort by
Showing 12 of 12 results by avw
It looks like it can work random in the specified keyspace:
https://github.com/pikachunakapika/BitCrack/issues/13
https://github.com/pikachunakapika/BitCrack/issues/3
Try "--keyspace START:END" and "-r" flags together
https://github.com/pikachunakapika/BitCrack/issues/13
https://github.com/pikachunakapika/BitCrack/issues/3
Try "--keyspace START:END" and "-r" flags together
Well I tried with -o file command and without and no file was saved when the key was found, then I tried the same in the latest version and it worked perfectly.
When I tried on Windows to run the original bitcrack, it saved output file in windows/system32.Try naming the file non-standard way, run bc, and then searching for the file in system.
This version does not save key text file at all, just tested it, it's broken.
Maybe bitcrack writing output file to the wrong directory where you're looking?Here it is necessary to load completely (green button " Clone or download ") all in ZIP archive, and then to open archive on the computer?
This is the source code, you need to compile it in executable file (section "Building in Windows/Linux")Whether and there is a combined variant of use of functions " - keyspace " and " -r, - randoom ", i.e. that worked so:
For example - we write -- keyspace 100000000000:500000000000 and -- random OR -- random 100000000000:500000000000 then The search is made only in a range 100000000000:500000000000, but casual (random like a flea or a kangaroo ) by jumps?
-r, --randomFor example - we write -- keyspace 100000000000:500000000000 and -- random OR -- random 100000000000:500000000000 then The search is made only in a range 100000000000:500000000000, but casual (random like a flea or a kangaroo ) by jumps?
Each point will start in random KEYSPACE
Description does not specify this function, so it is only in this fork - https://github.com/pikachunakapika/BitCrack
Why would you want to search random key space?
Someone mentioned in this topic(OP?) that there is a possibility, but I have not found..At first glance, a random start in a given range seems more promising than a long straight road.
Something like Vanitygen, where the number changes every 1000000 passed keys
as we already know bitcoin puzzle wallets are randomly chhosed by the creater
how do you know that for sure?who has a successful experience of bruteforce attack on private keys?
Nobody.also ran some checking on the old style electrum seeds with a "modified" word list...
What is "old style" different from the new?- The transaction originally funding this brainwallet split 1 BTC into neat sets of 0.001 and 0.005 BTC. Could other outputs from this transaction - there are 101 in total - also be brainwallets, or some other kind of special address? Some are still unspent, 7.5 years later.
You can see that addresses are arranged alphabetically, sorted by first two letters (first is always lowercase).Looks like addresses were generated by vanitygen.