Pollard's kangaroo ECDLP solver

[WanderingPhilospher]

Does this mean that the puzzle transactions are not in the keyspaces that privatekeys.pw shows? but could be anywhere?

https://privatekeys.pw/puzzles/bitcoin-puzzle-tx

Puzzle 64 - Keyspace 8000000000000000...ffffffffffffffff    ?

No, do not pay attention to fxsniper's post.

The puzzles are in the bits/keyspace related to the amount.  

Like you said, #64 (.64 BTC) is in the 64 bit range: 8000000000000000:FFFFFFFFFFFFFFFF

Thank you for the clarification. As the public key is not available for some of these puzzle transactions some will need to be brute-forced using the base58-check address right?

Unless we know the public key kangaroo cant help as much faster as it is.

Correct, most need to be brute forced.  Most programs take the input as base58 address but like Bitcrack and Vanity Search, they convert the base58 into RIPEMD 160 and search for that; a little quicker. Vanity Search can also search for string if you don't enter the full address.

[1715197406]

1715197406

[1715197406]

1715197406

[1715197406]

1715197406

[1715197406]

1715197406

[NotATether]

I want to add a HEX-to-Base58 converter to Kangaroo because it will make importing the private and public keys easier. When I have free time from work though. I discovered a nice web IDE at https://gitpod.io that will enable me to make code changes quickly without the overhead of installing software

[unclevito]

On all 4 of my computers when i try to start a search(cpu only at the in.txt point) I get the following error ParsePublicKeyHex: (Error invalid public key specified (Not lie on elliptic curve)
in.txt, error line 2: 02CEB6CBBCDBDF5EF7150682150F4CE2C6F4807B349827DCDBDD1F2EFA885A2630. I have tried multiple public keys on these computers with the same error. I have to start the search by using a different computer and then transfer the save.work to the other computers. Also I have tried compiling the program on each computer but still get the same error.

[a.a]

Well if it starts with 02 then it is a compressed key. So when you uncompress it you will get x and y coordinates. You could put the x argument into sha256k1 and check if you get the right y-ordinate. If your calculated y is not the same as the y of the uncompressed pubkey, then you have your answer.

[unclevito]

Sorry I am not that advanced to do what you suggest. Why does 1 computer work and the other 4 do not. That is my issue. same in.txt file so if it workss on 1 with intel cpu's  it should work on the other 4. i will try to uncompress the public key and try it. thanks

[NotATether]

Is there any way to calculate the probable keyspace range of an address? Looking at the puzzle page the only correlation seems to be the balance. How was the keyspace range determined?

He used a deterministic wallet.

There is no linear keyspace relationship between HD wallet parents and children.

Thanks for the reply and answer. As being HEX deficient in knowledge does that mean you need the PK inputted to get the keyspace or can you put in the address as a watch only and get the keyspace. Then all these puzzles were generated from a wallet that used seed phrases if they were generated with a  deterministic wallet, is that correct?

Kangaroo does not work with seed phrases and HD wallets at all, it tries to guess a private key from a possible start and end private key. There is no way to guess a keyspace from the address.

Sorry I am not that advanced to do what you suggest. Why does 1 computer work and the other 4 do not. That is my issue. same in.txt file so if it workss on 1 with intel cpu's  it should work on the other 4. i will try to uncompress the public key and try it. thanks

Then it's your in.txt that's the problem not the program itself. Where did you get this public key from, a block explorer or randomly generated?

[unclevito]

That is the public key for puzzle 120, same number on the blockchain and published in your source code too (puzzle32.txt). Also no matter what public key I put in i get the same error. The error can't be in the in.txt file. I have made new ones for each computer and copied the one from the computer that does not get the error. Required text encoding for the in.txt file? All my computers save text in UTF-8

[_Counselor]

That is the public key for puzzle 120, same number on the blockchain and published in your source code too (puzzle32.txt). Also no matter what public key I put in i get the same error. The error can't be in the in.txt file. I have made new ones for each computer and copied the one from the computer that does not get the error. Required text encoding for the in.txt file? All my computers save text in UTF-8

You can try run kangaroo -check to make sure that basic calculations performing without errors.
If you see any errors, than something wrong with your hardware.

[fxsniper]

That is the public key for puzzle 120, same number on the blockchain and published in your source code too (puzzle32.txt). Also no matter what public key I put in i get the same error. The error can't be in the in.txt file. I have made new ones for each computer and copied the one from the computer that does not get the error. Required text encoding for the in.txt file? All my computers save text in UTF-8

in.txt  just use notpad on windows

I think you put  puzzle32.txt all in use, that is wrong
you need to split each set of puzzle to new one in.txt   it can you any name

in120.txt
in121.txt
in122.txt
puzzle120.txt
(somting like that)

Don't put new line on the end bottom line too

structure simple just 3 line
1 start keyspace search
2 end keyspace search
first public key search

[unclevito]

No I did not use puzzle32.txt LOL. Here is what my in.txt files look just like this  125 

10000000000000000000000000000000
1FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
0233709EB11E0D4439A729F21C2C443DEDB727528229713F0065721BA8FA46F00E

It is nothing to do with the in.txt file. Maybe I need to update the intel opencl for the cpu's. it can't be the same hardware issue for 4 different computers. if it was just 1 computer then maybe

[WanderingPhilospher]

No I did not use puzzle32.txt LOL. Here is what my in.txt files look just like this  125 

10000000000000000000000000000000
1FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
0233709EB11E0D4439A729F21C2C443DEDB727528229713F0065721BA8FA46F00E

It is nothing to do with the in.txt file. Maybe I need to update the intel opencl for the cpu's. it can't be the same hardware issue for 4 different computers. if it was just 1 computer then maybe

Which compiled release version are you using? Or did you compile/build on linux?

[unclevito]

I have compiled them with VS2019. I have 1.5, 2.2 and 2.3. On one computer they do not have an issue. 4 other computers have the same issue. i have to make the work file on the one and copy it to the others. I think I will try to update the intel cpu software/drivers in the morning for those.

[WanderingPhilospher]

I have compiled them with VS2019. I have 1.5, 2.2 and 2.3. On one computer they do not have an issue. 4 other computers have the same issue. i have to make the work file on the one and copy it to the others. I think I will try to update the intel cpu software/drivers in the morning for those.

Download the precompiled 2.1 version and test it.

[NotATether]

No I did not use puzzle32.txt LOL. Here is what my in.txt files look just like this  125  

10000000000000000000000000000000
1FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
0233709EB11E0D4439A729F21C2C443DEDB727528229713F0065721BA8FA46F00E

It is nothing to do with the in.txt file. Maybe I need to update the intel opencl for the cpu's. it can't be the same hardware issue for 4 different computers. if it was just 1 computer then maybe

If you are trying to search from the "1FF..." number to "10000...", because you appear to have the bigger number on top, the "1FF" should be on the first line followed by "10000...".

Also what model is your CPU, you need to have SSSE3 on it to work so at least Core 2.

[unclevito]

it is an illusion of the font the webpage uses
10000000000000000000000000000000 = 21267647932558653966460912964485513216
1FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF = 42535295865117307932921825928971026431 double the top line. All my cpu's are I-3 quad core except one which is 12 core Xeon L5638

[NotATether]

OK, to be clear, which fork of Kangaroo are you getting this error on? There's the original one by Jean_Luc and there's also my Kangaroo-256 fork.

[unclevito]

2.1, 2.2 and your 2.3. I am going to try the precompiled 2.2, 2.1 later. But my guess it is not the program and definitely not the in.txt file but possibly the intel drivers/opencl which I am going to update also later. One computer works well with the in.txt file and if the move the complied program to the other computers or compile them on their own I still get the error. if it was the program it should not work on any.

[Robert_BIT]

Sad to see there's no compiled .exe for the Kangaroo-256 fork. Compiling from the source throws a ton of errors, same with Jean_Luc's original version. But at least there is a working .exe for that one. I hope the dev finds time to compile the -256 fork on a Win machine   

[a.a]

What is the url of the fork?

[NotATether]

What is the url of the fork?

https://github.com/ZenulAbidin/Kangaroo-256