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
Topic: BitCrack - A tool for brute-forcing private keys - page 85. (Read 77647 times)
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.
Tried and no textfile was found in system32. I really wish someone can add -r to the latest version.
Got it to work but it seems it just randomly searching in 252-256 space, so it is not 'really' random.
If to add function " -r, - randoom " in last version, it is desirable to make two variants it is functions:
1 - " -r, - randoom " - the search by casual jumps in all space is made;
2 - " -r START:END, - randoom START:END " - the search by casual jumps in the given (desirable) space is made
OR
1 - if not the function - keyspace - is given then the search by casual jumps in all space is made;
2 - if the function - keyspace - is specified then the search by casual jumps only in the specified space is made;
1 - " -r, - randoom " - the search by casual jumps in all space is made;
2 - " -r START:END, - randoom START:END " - the search by casual jumps in the given (desirable) space is made
OR
1 - if not the function - keyspace - is given then the search by casual jumps in all space is made;
2 - if the function - keyspace - is specified then the search by casual jumps only in the specified space is made;
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.
Tried and no textfile was found in system32. I really wish someone can add -r to the latest version.
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?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.
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
https://github.com/pikachunakapika/BitCrack This version does not save key text file at all, just tested it, it's broken. Can someone add -r to the latest Bitcrack version, please?
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
Can OP please add random (-r) function in the latest version of bitcrack?
Cheers
This version: https://github.com/pikachunakapika/BitCrack
Does not save private keys in txt at all, it is broken.
Cheers
This version: https://github.com/pikachunakapika/BitCrack
Does not save private keys in txt at all, it is broken.
Here it is necessary to load completely (green button " Clone or download ") all in ZIP archive, and then to open archive on the computer?
in this fork - https://github.com/pikachunakapika/BitCrack
***
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?
in this fork - https://github.com/pikachunakapika/BitCrack
***
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?
Description does not specify this function, so it is only in this fork - https://github.com/pikachunakapika/BitCrack
If not I am mistaken took software clBitCrack.exe from this page - https://github.com/brichard19/BitCrack/releases
It absolutely other version software clBitCrack.exe?
In her there is no function "-r --randoom" ?
It absolutely other version software clBitCrack.exe?
In her there is no function "-r --randoom" ?
I tried running on my laptops ( AMD A6-3420M APU with HD Graphics AMD Radeon HD 6520G ) - getting an error.
You sure are using this fork of software?
Quote from: Telariust
(...)This fork https://github.com/pikachunakapika/BitCrack
Code:
-r, --random
Each point will start in random KEYSPACE
Code:
-r, --random
Each point will start in random KEYSPACE
This function
-r, --random
Each point will start in random KEYSPACE
must work in software clBitCrack.exe ?
I tried running on my laptops ( AMD A6-3420M APU with HD Graphics AMD Radeon HD 6520G ) - getting an error.
-r, --random
Each point will start in random KEYSPACE
must work in software clBitCrack.exe ?
I tried running on my laptops ( AMD A6-3420M APU with HD Graphics AMD Radeon HD 6520G ) - getting an error.
Telariust, thank you very much 
https://imgur.com/CoFCSa7
Is this 2123626 million or 2,123,626?
I'm using a Vega 64 with "clBitCrack.exe -b 500 -t 256 -p 1024 -c -u"
? 2123626 Mkey/s . this is unrealistic speed. looks like a bug.guys how much gives vega56?
Why not add the ability to search by ripemd160 [...] to speed up
ripemd160(base16) <--> btcaddr(base58) <--> Int/Dec(base10) <--> Hex(base16) <--> Binary(base2)it's the same thing, just the bases are different, converting
Why not add the ability to search by [...] known public key to speed up
Matching against pubkey would be handy (if it doesn't already do this?)
..because main target(puzzle) assumes a public key unknown (only its ripemd160 hash is known).and if pubkey is known then sequential key search in a limited space (which uses bitcrack) is the stupidest and slowest way to search compared to baby-step-gigant-step algo and pollard-rho/kangaroo algo
when BitCrack compute 10M keys, its checked 10M keys
when BSGS/Pollard compute 10M keys, its checked (10M)^2 = 100000000M keys (!!!..undestand?)
And which bitcrack version supports random key space function ?
This fork https://github.com/pikachunakapika/BitCrackCode:
-r, --random
Each point will start in random KEYSPACE
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
almightyruler - It is clear, THANKS!
Jump to: