Title: Using Kangaroo for WIF solving Post by: PawGo on February 08, 2021, 02:13:23 PM Hello
I would like to share with you my modifications of Jean-Luc's famous Kangaroo program. I adapted it to be used as a 'WIF solver'. In general, there are 2 cases - where stride is large enough not to collide with WIF checksum or when it is more complicated and stride collides. I described it and showed test examples on github: https://github.com/PawelGorny/Kangaroo but I will also rewrite it here. Let's take WIF: 5HrdZxkxnVst8Q3qCLJkeiLe1k4AmSDaAhqQVUYVxVSBkf5VfUu which encodes the private key 0552e025571c01bcda0297c22731d74becbd30d07e4ec355c741825fffc0a672. Decoded WIF shows checksum 524412ca The corresponding public key is 04777c026b8085951da7117395bf269c055f36bf2ddf623281962855edee36d4e73bec2fa87b122 a0f1b2841ef4f7afdec2443f89c151ee2597feac18ae0d62bdf
Now, we may find the first WIF to be tested, it will be 5HrdZxkxnVst8Q11111keiLe1k4AmSDaAhqQVUYVxVSBkf5VfUu. When we decode it, we find the private key which is the beginning of our range: 0552e025571c01bcd9eda59365a2fb3ae0bd7547dfeeeb13d971d848bcbf0467 Now, we must calculate the number of WIFs in our range. Beause we have 5 missing characters, it will be 58^5 = 656356768 (271f35a0 hex) To have the end of range for Kangaroo, we must calculate fake end which is start + range Code: new BigInteger("0552e025571c01bcd9eda59365a2fb3ae0bd7547dfeeeb13d971d848bcbf0467",16).add(new BigInteger("656356768",10)).toString(16) = Because WIFs encodes checksum, we must observe if stride collides with checksum. Fortunately - not, because the last 8 characters (length of checksum) are 0s. We may remove these zeros and get shorter stride. The final configuration file is: Code: 552e025571c01bcd9eda59365a2fb3ae0bd7547dfeeeb13d971d848bcbf0467 Code: $ ./kangaroo -stride af820335d9b3d9cf58b911d87035677fb7f5281 test_af820335d9b3d9cf58b911d87035677fb7f5281.txt
Now, we may find the first WIF to be tested, it will be 5HrdZxkxnVst8Q3qCLJkeiLe1k4Am1111hqQVUYVxVSBkf5VfUu. When we decode it, we find the private key which is the beginning of our range: 0552e025571c01bcda0297c22731d74becbd30cfb218f04dc91299473f61ffde Now, we must calculate the number of WIFs in our range. Beause we have 4 missing characters, it will be 58^4 = 11316496 To have the end of range for Kangaroo, we must calculate fake end which is start + range Code: new BigInteger("0552e025571c01bcda0297c22731d74becbd30cfb218f04dc91299473f61ffde",16).add(new BigInteger("11316496",10)).toString(16) = Unfortunately the stride collides with checksum (last 8 characters are not 0s). It means that for our calculations we must take into account the proper checksum And this is difficult part, because the real checksum is unknown. In our test it is known, but in real-life it could be needed to see how many possibilities there are. For example, in this case, playing with missing characters of WIF we may observe that last 4 characters of checksum are fixed. The first 4 could be changed, BUT the 4th character gets only 4 values. It means that if we want to use this method for real-life problem, we may need to do calculations for 16*16*16*4 checksums (in fact will less operations needed, because many checksums will generate the same private key in addition to the stride). Because stride collides with checksum, we will have to use the full (long) value and pass checksum as a parameter. The final configuration file is: Code: 552e025571c01bcda0297c22731d74becbd30cfb218f04dc91299473f61ffde Code: $ ./kangaroo -stride 2b85840fc1d6a480ae7fa240000 -checksum 524412ca test_2b85840fc1d6a480ae7fa240000_524412ca.txt Title: Re: Using Kangaroo for WIF solving Post by: Coding Enthusiast on February 08, 2021, 02:47:27 PM Interesting approach but what's the speed of something like this?
And how does it perform compared to the simple approach of decoding and computing checksum that only computes SHA256? For example it takes me 3.5 min to check the entire 656 million keys in your first example using checksum (answer is found after 1.1 min) and it is faster if the key was compressed (KwQ4QV73DpTafe_____MfTTgNH2z78JVPqEegga2ovWATXzDVu6U) only 25 seconds. Title: Re: Using Kangaroo for WIF solving Post by: PawGo on February 08, 2021, 03:26:37 PM For these examples - result is instant.
I have made test with 10 missing characters (CPU only, on my dev machine I do not have GPU). Code: 5HrdZxkxn__________keiLe1k4AmSDaAhqQVUYVxVSBkf5VfUu Config file: Code: 0552e02556fb5aeb9aedc2ea64efec8ac200eb71a9653cfaad25d4c2a5b4d5c7 Test: Code: $ ./kangaroo -stride af820335d9b3d9cf58b911d87035677fb7f5281 testBig.txt Not bad, no? ;) 10 missing WIF characters - Less than 11 minutes on old CPU. GPU performance - to be seen. Title: Re: Using Kangaroo for WIF solving Post by: Coding Enthusiast on February 08, 2021, 03:57:14 PM Not bad, no? ;) 10 missing WIF characters - Less than 11 minutes on old CPU. GPU performance - to be seen. That's fantastic. I'll have to go back to check Pollard's kangaroo algorithm again.Title: Re: Using Kangaroo for WIF solving Post by: WanderingPhilospher on February 08, 2021, 05:16:56 PM On a piddly 1060 6GB GPU
Code: Kangaroo v2.2 2070 Super with DP of 14: Code: Kangaroo v2.2 2070 Super with DP of 10: Code: Kangaroo v2.2 Title: Re: Using Kangaroo for WIF solving Post by: abadon666999 on February 08, 2021, 07:55:35 PM hi dev..thanks for your support
I have 3 question 1) 5HrdZxkxnVst8Q11111keiLe1k4AmSDaAhqQVUYVxVSBkf5VfUu. When we decode it, we find the private key which is the beginning of our range: 0552e025571c01bcd9eda59365a2fb3ae0bd7547dfeeeb13d971d848bcbf0467 Can you say me what is procedure for DECODE PRIVATE KEY with 11111 ( 5HrdZxkxnVst8Q11111keiLe1k4AmSDaAhqQVUYVxVSBkf5VfUu ) 2)this code new BigInteger("0552e025571c01bcda0297c22731d74becbd30cfb218f04dc91299473f61ffde",16).add(new BigInteger("11316496",10)).toString(16) = 552e025571c01bcda0297c22731d74becbd30cfb218f04dc9129947400eacee How should it be applied via Linux command? 3)for calculate STRIDE We check where is the most right unknown character - it's position will tell us what is the stride. In our case it is 58^32 = af820335d9b3d9cf58b911d87035677fb7f528100000000 What is procedure or comand for calculate? Thanks Title: Re: Using Kangaroo for WIF solving Post by: PawGo on February 08, 2021, 10:28:03 PM The code extracts are from my helper, written in java - so yes, you would be able to use it under linux.
For decoding WIF you may use BitcoinJ library or just a webpage: https://learnmeabitcoin.com/technical/wif Title: Re: Using Kangaroo for WIF solving Post by: NotATether on February 09, 2021, 07:48:49 AM Unfortunately the stride collides with checksum [...snip] we will have to use the full (long) value and pass checksum as a parameter. Then why make the checksum bits part of the stride in the first place? It doesn't need to be guessable because this part can be derived after the private key is known, so passing the checksum bits makes no sense in this context because it lets the program look for invalid checksums as if it were part of the private key. The easy way to port Kangaroo to look for WIF values is to convert it into a private key hex, and since the public key and therefore base58 public address can be computed from the private key hex, you can mod it to pass a start and end WIF which are then turned into private keys. However you'll still need to directly pass the public key of the address you want to crack because hashing the public key to an address is irreversible. True you could scan the blockchain for the public key corresponding to an address but this only works if there's a transaction associated with it. Title: Re: Using Kangaroo for WIF solving Post by: PawGo on February 09, 2021, 08:06:32 AM Then why make the checksum bits part of the stride in the first place? It doesn't need to be guessable because this part can be derived after the private key is known, so passing the checksum bits makes no sense in this context because it lets the program look for invalid checksums as if it were part of the private key. Because checksum has impact on addition result. Example (in dec): Imagine you have stride 530. And you have checksum 70. If I do like you said, so I will remove 2 last digits of stride, I will have private keys: 5, 10, 15, 20, 25. But if I do the correct addition and then remove 2 last digits, I will have: 600->6, 1130->11, 1650->16, 2180->21, 2710->27. And the problem is that some group of checksums will create the same private keys and some checksums completely different. Title: Re: Using Kangaroo for WIF solving Post by: abadon666999 on February 09, 2021, 08:58:54 AM hi ..i have create 1 file
new BigInteger("0552e025571c01bcda0297c22731d74becbd30cfb218f04dc91299473f61ffde",16).add(new BigInteger("11316496",10)).toString(16) = that i have call sun.java when i run file java java sun.java i have error sun.java:1: error: class, interface, or enum expected new BigInteger("0552e025571c01bcda0297c22731d74becbd30cfb218f04dc91299473f61ffde",16).add(new BigInteger("11316496",10)).toString(16) = ^ 1 error error: compilation failed can you help me please? can you create 1 clear guide...for calculate 1)the end of range for Kangaroo and 2)STRIDE...please Title: Re: Using Kangaroo for WIF solving Post by: NotATether on February 09, 2021, 09:27:06 AM hi ..i have create 1 file new BigInteger("0552e025571c01bcda0297c22731d74becbd30cfb218f04dc91299473f61ffde",16).add(new BigInteger("11316496",10)).toString(16) = This isn't valid Java, you are assigning the result of BigInt().toString(), a String class, the value of... nothing (there's nothing after the equals sign!). And you can't assign anything to this value anyway because it is not an lvalue, something declared like String s = /* ... */ ; Title: Re: Using Kangaroo for WIF solving Post by: abadon666999 on February 09, 2021, 09:38:41 AM thanks for your reply
can you post please the correct file java for calculate the end of range for Kangaroo? can you post file java for calculate STRIDE? Title: Re: Using Kangaroo for WIF solving Post by: PawGo on February 09, 2021, 10:40:12 AM Just a lazy solution:
Code: import java.math.BigInteger; Going back to this version of Kangaroo: I think there is still something wrong with calculations with checksum - for longer ranges (>6 unknown characters) it does not return result, while when there is case without checksum (just a stride) it works good. Title: Re: Using Kangaroo for WIF solving Post by: abadon666999 on February 09, 2021, 10:59:51 AM hi thanks dev for this file...work good
START: 552e025571c01bcd9eda59365a2fb3ae0bd7547dfeeeb13d971d848bcbf0467 END: 552e025571c01bcd9eda59365a2fb3ae0bd7547dfeeeb13d971d848e3de3a07 STRIDE: af820335d9b3d9cf58b911d87035677fb7f528100000000 just 1 last thing i d'like test with 14=number of unknown characters import java.math.BigInteger; public class K { public static void main(String[] args) { BigInteger start = new BigInteger("0552e025571c01bcd9eda5935d619d2f6e92860be1a512c4a71dbee04cacbc67", 16); BigInteger stride = BigInteger.valueOf(58L).pow(32);//depends on the position of most-right unknown character BigInteger range = BigInteger.valueOf(58L).pow(14);//14=number of unknown characters BigInteger end = start.add(range); System.out.println("START: "+start.toString(16)); System.out.println("END: "+end.toString(16)); System.out.println("STRIDE: "+stride.toString(16)); } } is this correct or i must to do other modifications? for example 5HrdZxkxnVst8Q11111111111111mSDaAhqQVUYVxVSBkf5VfUu 14=number of unknown characters 0552e025571c01bcd9eda5935d619d2f6e92860be1a512c4a71dbee04cacbc67 results= START: 552e025571c01bcd9eda5935d619d2f6e92860be1a512c4a71dbee04cacbc67 END: 552e025571c01bcd9eda5935d619d2f6e92860be1a91b21742359640a3afc67 STRIDE: af820335d9b3d9cf58b911d87035677fb7f528100000000 Title: Re: Using Kangaroo for WIF solving Post by: NotATether on February 09, 2021, 04:08:42 PM Just a lazy solution: Code: import java.math.BigInteger; This can be extended to handle a "partial" number of characters known, which is the case where some of the bits are set, by changing 5 to be a decimal number. For example by setting it to 4.5 we can do the equivalent of searching for 4 characters plus the the first 29 base58 values 1-V of the fifth. Or the first character having the last 29 base58 values W-z and 4 whole characters after that (or anything between those two). This will make Kangaroo perform better in the cases where you know one of the characters is in a range but searching all 58 characters is too prohibitive, like when you're already searching a lot of characters. Although doing a fractional exponentiation on a BigInteger is going to be a problem. Ideally you do not want to change this to BigDecimal for performance reasons, and you can't split the decimal into a fraction and do 58^num / 58^denom = 58^num * 58^-denom because BigInteger.pow() raises an exception with a negative exponent. Worst case scenario is that you use the divide(58^denom) method but I have no idea how slow dividing BigInts together is going to be. (Maybe try 58^num * (58^denom).modInverse(m) but set the modulus m to something bigger than 58^denom so we don't do the "mod" part of modInverse. But this only brings benefit if modInverse() is faster than the divide() method. This can easily be ported to other languages provided that their bigint libraries are sane and let you take negative exponents (unlike Java). In particular it's a very useful feature to port to the original Kangaroo itself if Jean_Luc is still around on Github. Title: Re: Using Kangaroo for WIF solving Post by: PawGo on February 09, 2021, 04:26:14 PM Oh, it was just a simple calculator, I would not focus now on it - you may always calculate it manually, it was just a easy piece of code for him.
Anyway, I have started to have doubts if the case witch checksum is doable at all. I must verify carefully because I have a huge increase of used memory (without any result) and I think that the problem is in the fact that checksum may cause the private keys are not 'linear'. I do not have this problem when I do not use checksum, so it must be this... In other words: For virtualprivate key X we recalculate using stride&checksum and receive public key related to realkey X1. For virtualprivate key Y we recalculate using stride&checksum and receive public key related to realkey Y1. If checksum does not have impact, we may get point from X (it will be in fact point from X1), do (Y-X) operations and we should receive point related to Y (in fact Y*stride). But because checksum may have impact on which point we return as a point corresponding to Y, it becomes to be untrue. If checksum have impact, we may have for example situation where point for Y would be point from real private key Y1=Y*stride+1. And we expected to have point from Y*stride. Title: Re: Using Kangaroo for WIF solving Post by: abadon666999 on February 09, 2021, 04:46:32 PM PawGo i have SENT YOU 1 message in bitcointalkforum...please check and contact me on telegram...thanks for your SUPPORT
Title: Re: Using Kangaroo for WIF solving Post by: NotATether on February 09, 2021, 09:01:57 PM Anyway, I have started to have doubts if the case witch checksum is doable at all. I must verify carefully because I have a huge increase of used memory (without any result) and I think that the problem is in the fact that checksum may cause the private keys are not 'linear'. I do not have this problem when I do not use checksum, so it must be this... I dunno, I still feel like you can find a stock WIF to hex converter and put that in Kangaroo without more memory usage, in which case you won't have to worry about the checksum at all and it's like 10x easier than fixing this. Maybe instead of a stride parameter you can make users pass a hexadecimal bit mask to let them choose which bits Kangaroo's going to fill using hops from the search range. But IMHO I think that chopping up the range like this may even cause Pollard's Kangaroo algorithm to give wrong results, because the algorithm is trying to collide wild Kangaroos with the tame one, but has no idea that the resulting value of the kangaroo is going to be split up and sent to different parts of some other numbers. I think this logic might also apply to your stride parameter too since it's equivalent to a bit mask with the lower few bits set to zero, from what I can understand (correct me if I'm wrong). Title: Re: Using Kangaroo for WIF solving Post by: dextronomous on February 09, 2021, 11:52:48 PM Just a lazy solution: Code: import java.math.BigInteger; Going back to this version of Kangaroo: I think there is still something wrong with calculations with checksum - for longer ranges (>6 unknown characters) it does not return result, while when there is case without checksum (just a stride) it works good. how do i run this java. i have a question, does this work with missing chars at the end of the wif, really want to know, stuck on reading here past 2 days. :-[ Title: Re: Using Kangaroo for WIF solving Post by: WanderingPhilospher on February 10, 2021, 01:07:58 AM Just a lazy solution: Code: import java.math.BigInteger; Going back to this version of Kangaroo: I think there is still something wrong with calculations with checksum - for longer ranges (>6 unknown characters) it does not return result, while when there is case without checksum (just a stride) it works good. how do i run this java. i have a question, does this work with missing chars at the end of the wif, really want to know, stuck on reading here past 2 days. :-[ Here is a python script I threw together real quick if you are more familiar with it: Code: #First, enter the start range as start = "starting range like example below" Title: Re: Using Kangaroo for WIF solving Post by: PawGo on February 10, 2021, 07:37:43 AM i have a question, does this work with missing chars at the end of the wif, really want to know, stuck on reading here past 2 days. :-[ No, in fact currently it works good only for missing beginning (first 19-20 characters). But this is when we talk about WIFs. When we talk about pure private key solving, it works well. Which means you my try puzzle #120 with a custom stride if you do not want to wait to long and believe in yours luck ;) Title: Re: Using Kangaroo for WIF solving Post by: dextronomous on August 23, 2022, 03:04:35 PM Hi there PawGo,
could you provide the settings for the program for the 120th with the stride and all. thanks man. Title: Re: Using Kangaroo for WIF solving Post by: BHWallet on September 02, 2022, 04:35:56 PM Just a lazy solution: Code: import java.math.BigInteger; Going back to this version of Kangaroo: I think there is still something wrong with calculations with checksum - for longer ranges (>6 unknown characters) it does not return result, while when there is case without checksum (just a stride) it works good. how do i run this java. i have a question, does this work with missing chars at the end of the wif, really want to know, stuck on reading here past 2 days. :-[ Here is a python script I threw together real quick if you are more familiar with it: Code: #First, enter the start range as start = "starting range like example below" What exactly are we doing with this tool? I am using WP's python script with PawGo's Kangaroo to get the range & stride and it's all working as it supposed to, but I don't understand this tool at all tbh How can I begin solving #120 for example by using it's public key and some random WIF within the range? I don't get it Title: Re: Using Kangaroo for WIF solving Post by: MikeJ_NpC on November 01, 2022, 10:47:28 AM lame question .... how do you convert the WIF lol.. i get all the rest after that
nvm just wif base58 to hex.. :D Title: Re: Using Kangaroo for WIF solving Post by: MikeJ_NpC on November 01, 2022, 02:38:22 PM do you need the public key for this to work? what if you dont have that data?
Title: Re: Using Kangaroo for WIF solving Post by: PawGo on November 01, 2022, 02:42:09 PM Yes, public key is required for Kangaroo method (the same like is for BSGS).
could you provide the settings for the program for the 120th with the stride and all. No magic there, just a normal configuration: Code: 800000000000000000000000000000 if You want to use stride just divide the range, for example if you want to test using -stride 2 the range will be: Code: 800000000000000000000000000000 Title: Re: Using Kangaroo for WIF solving Post by: MikeJ_NpC on November 01, 2022, 07:13:19 PM Yes, public key is required for Kangaroo method (the same like is for BSGS). could you provide the settings for the program for the 120th with the stride and all. No magic there, just a normal configuration: Code: 800000000000000000000000000000 if You want to use stride just divide the range, for example if you want to test using -stride 2 the range will be: Code: 800000000000000000000000000000 Well i had no output on mine.. so that poses a problem ... argh only h160 Title: Re: Using Kangaroo for WIF solving Post by: btc-room101 on November 12, 2022, 02:01:21 PM Hello I would like to share with you my modifications of Jean-Luc's famous Kangaroo program. I adapted it to be used as a 'WIF solver'. In general, there are 2 cases - where stride is large enough not to collide with WIF checksum or when it is more complicated and stride collides. I described it and showed test examples on github: https://github.com/PawelGorny/Kangaroo but I will also rewrite it here. Let's take WIF: 5HrdZxkxnVst8Q3qCLJkeiLe1k4AmSDaAhqQVUYVxVSBkf5VfUu which encodes the private key 0552e025571c01bcda0297c22731d74becbd30d07e4ec355c741825fffc0a672. Decoded WIF shows checksum 524412ca The corresponding public key is 04777c026b8085951da7117395bf269c055f36bf2ddf623281962855edee36d4e73bec2fa87b122 a0f1b2841ef4f7afdec2443f89c151ee2597feac18ae0d62bdf
Now, we may find the first WIF to be tested, it will be 5HrdZxkxnVst8Q11111keiLe1k4AmSDaAhqQVUYVxVSBkf5VfUu. When we decode it, we find the private key which is the beginning of our range: 0552e025571c01bcd9eda59365a2fb3ae0bd7547dfeeeb13d971d848bcbf0467 Now, we must calculate the number of WIFs in our range. Beause we have 5 missing characters, it will be 58^5 = 656356768 (271f35a0 hex) To have the end of range for Kangaroo, we must calculate fake end which is start + range Code: new BigInteger("0552e025571c01bcd9eda59365a2fb3ae0bd7547dfeeeb13d971d848bcbf0467",16).add(new BigInteger("656356768",10)).toString(16) = Because WIFs encodes checksum, we must observe if stride collides with checksum. Fortunately - not, because the last 8 characters (length of checksum) are 0s. We may remove these zeros and get shorter stride. The final configuration file is: Code: 552e025571c01bcd9eda59365a2fb3ae0bd7547dfeeeb13d971d848bcbf0467 Code: $ ./kangaroo -stride af820335d9b3d9cf58b911d87035677fb7f5281 test_af820335d9b3d9cf58b911d87035677fb7f5281.txt
Now, we may find the first WIF to be tested, it will be 5HrdZxkxnVst8Q3qCLJkeiLe1k4Am1111hqQVUYVxVSBkf5VfUu. When we decode it, we find the private key which is the beginning of our range: 0552e025571c01bcda0297c22731d74becbd30cfb218f04dc91299473f61ffde Now, we must calculate the number of WIFs in our range. Beause we have 4 missing characters, it will be 58^4 = 11316496 To have the end of range for Kangaroo, we must calculate fake end which is start + range Code: new BigInteger("0552e025571c01bcda0297c22731d74becbd30cfb218f04dc91299473f61ffde",16).add(new BigInteger("11316496",10)).toString(16) = Unfortunately the stride collides with checksum (last 8 characters are not 0s). It means that for our calculations we must take into account the proper checksum And this is difficult part, because the real checksum is unknown. In our test it is known, but in real-life it could be needed to see how many possibilities there are. For example, in this case, playing with missing characters of WIF we may observe that last 4 characters of checksum are fixed. The first 4 could be changed, BUT the 4th character gets only 4 values. It means that if we want to use this method for real-life problem, we may need to do calculations for 16*16*16*4 checksums (in fact will less operations needed, because many checksums will generate the same private key in addition to the stride). Because stride collides with checksum, we will have to use the full (long) value and pass checksum as a parameter. The final configuration file is: Code: 552e025571c01bcda0297c22731d74becbd30cfb218f04dc91299473f61ffde Code: $ ./kangaroo -stride 2b85840fc1d6a480ae7fa240000 -checksum 524412ca test_2b85840fc1d6a480ae7fa240000_524412ca.txt It has no mean to solve 2**11, or even 2**40 puzzles so what? BTC is 2*256, and you need to do 2**128 to crack real world btc if you can do 2**40, and have a means to do 2**40 on the ball park then that puts you in the game of find a hit that year The problem with the kangaroo BULLSHIT is that real world there are no problem in the 2*20 domain There are two ways to crack BTC 1.) use large bloom filter and find key/address pairs with value, and have search space that is doing 2**40 compares per second 2.) use advanced crypto methods to crack ecdlp256 using known back doors ( this is huge problem in prime number theory, but there tools out there ) Title: Re: Using Kangaroo for WIF solving Post by: yiren38 on January 17, 2023, 02:40:23 PM For these examples - result is instant. Your program cannot work on private keys starting with KI have made test with 10 missing characters (CPU only, on my dev machine I do not have GPU). Code: 5HrdZxkxn__________keiLe1k4AmSDaAhqQVUYVxVSBkf5VfUu Config file: Code: 0552e02556fb5aeb9aedc2ea64efec8ac200eb71a9653cfaad25d4c2a5b4d5c7 Test: Code: $ ./kangaroo -stride af820335d9b3d9cf58b911d87035677fb7f5281 testBig.txt Not bad, no? ;) 10 missing WIF characters - Less than 11 minutes on old CPU. GPU performance - to be seen. Below is an example: 12TjDr6EvjfCCixWxWD7W8fjMiP8ywXQZf 02C6459FFBD29C235EC71D64C3386B203F8AF1C29A368A08378CDF57002C000556 703626BB241407C588CA826F2A5E3E8CFCD3CD912C63B2BBAFF4D323AEC25E62 KzyqQdyZmVcDmqb4atHfBQiBjR8op2mEQdM4xCHNwDsbwupBtR6P ============================================================================ Kz1111111111mqb4atHfBQiBjR8op2mEQdM4xCHNwDsbwupBtR6P 52F941347554093DF22FE246922EEB03F0494A73B23287E4AC9013D44CCC24D8 ============================================================================ configuration-file.txt: 52F941347554093DF22FE246922EEB03F0494A73B23287E4AC9013D44CCC24D8 52F941347554093DF22FE246922EEB03F0494A73B23287E4B28A99F914C7C8D8 02C6459FFBD29C235EC71D64C3386B203F8AF1C29A368A08378CDF57002C000556 ============================================================================ Kangaroo.exe -gpu -o key.txt -stride 4FD9DF9DBF7E28ED5357BA4A062C19C48E628F6AF73B06121 configuration-file.txt unable to find KzyqQdyZmVcDmqb4atHfBQiBjR8op2mEQdM4xCHNwDsbwupBtR6P What did i do wrong? Title: Re: Using Kangaroo for WIF solving Post by: PawGo on January 17, 2023, 03:29:36 PM Your program cannot work on private keys starting with K Below is an example: 12TjDr6EvjfCCixWxWD7W8fjMiP8ywXQZf 02C6459FFBD29C235EC71D64C3386B203F8AF1C29A368A08378CDF57002C000556 703626BB241407C588CA826F2A5E3E8CFCD3CD912C63B2BBAFF4D323AEC25E62 KzyqQdyZmVcDmqb4atHfBQiBjR8op2mEQdM4xCHNwDsbwupBtR6P ============================================================================ Kz1111111111mqb4atHfBQiBjR8op2mEQdM4xCHNwDsbwupBtR6P 52F941347554093DF22FE246922EEB03F0494A73B23287E4AC9013D44CCC24D8 ============================================================================ configuration-file.txt: 52F941347554093DF22FE246922EEB03F0494A73B23287E4AC9013D44CCC24D8 52F941347554093DF22FE246922EEB03F0494A73B23287E4B28A99F914C7C8D8 02C6459FFBD29C235EC71D64C3386B203F8AF1C29A368A08378CDF57002C000556 ============================================================================ Kangaroo.exe -gpu -o key.txt -stride 4FD9DF9DBF7E28ED5357BA4A062C19C48E628F6AF73B06121 configuration-file.txt unable to find KzyqQdyZmVcDmqb4atHfBQiBjR8op2mEQdM4xCHNwDsbwupBtR6P What did i do wrong? Your configuration is correct. I do not know... on my computer it works (but I did not use GPU mode). Maybe that's the problem? I will try to find some time and test it again. How long did you wait? https://i.ibb.co/m8mvgbD/image-2023-01-17-162855726.png (https://ibb.co/xHymdXC) Title: Re: Using Kangaroo for WIF solving Post by: Minase on January 17, 2023, 04:03:59 PM tested this on gpu and it works.
indeed you need to wait longer but it works. make sure your grid size is correct, the search space is small. Title: Re: Using Kangaroo for WIF solving Post by: digaran on April 10, 2023, 12:34:05 PM Hey man I'm back again, as I explained earlier I can't use GPU, because CUDA is not compiled or something, I have a ccap 5 and CUDA 12, but I tried to compile your WIFsolver CUDA few month ago and was unsuccessful. I can't keep coming to you everytime I need compiling, it's not your job but it would mean a lot if it's not a bother to release a compatible version for ccap 5.🤝👍
Lol my cute kangaroos are dying using CPU, I haven't fed them properly with strong GPU computation.😉 You know I was thinking today about something interesting, since you know programming I will share it here to see if we could come up with something. You know that hexadecimal characters are used to set colors on the web, right? I was wondering if it would be possible to develop a tool capable of linking the hexadecimal values of public keys to their actual private keys by color encoding them in synchronization, so for example we could invent an algorithm to find similarities and match them with certain colors, then we could find clues about the private key of a certain public key by encoding the public key using our invention. Imagine integrating that algo with kangaroo or baby step giant step, and then use strides to detect color hues similar to our public/ private key pair. But I guess that would destroy modern cryptography systems if it was possible.😅 |