Topic: Pollard's kangaroo ECDLP solver - page 56. (Read 58537 times)
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
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?
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
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.
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.
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.
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 
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 ?
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.
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 ?
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
sorry I use wrong word communication
key is on range puzzle
I mean you need to scan by use kangaroo jump too all area on keyspace but it is too wide
if need to focus on key position (no way to do) it have only random keyspace on keyspace to scan, may be it is wrong way to do this
yep, forget that I said help to not confused
see all puzzle that solve already that tell to know key is on bits/keyspace
What are you talking about that the best method is to bruteforce?
Do you still not understand how much faster Kangaroo is versus bruteforce/bitcrack??
Kangaroo the best is fast better than bitcrack and other medthod
now most I use is Kangaroo
but puzzle have pubkey leave only 9 address, and other 78 puzzle no pubkey
when solve all pubkey puzzle out, most puzzle leave no pubkey may be use bitcrack if not have other method can solve
There is no random keyspace; the keyspace is known.
I mean random to small keyspace on that keyspace for scan What you are looking for is some quick way to find #120 with one GTX 1050 card...it doesn't exist. But instead of running tests and trying this and that, start on #120; work on it when you can.
yes, it doesn't existno way to calculate reverse, all method still using random method
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 ?
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.
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 ?
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
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?
No.
I looking to way can calculate or can focus to keyspace nearly key but not found the way
now you can only random keyspace and hop to lucky
best method is bruteforce
Do you still not understand how much faster Kangaroo is versus bruteforce/bitcrack??
There is no random keyspace; the keyspace is known.
What you are looking for is some quick way to find #120 with one GTX 1050 card...it doesn't exist. But instead of running tests and trying this and that, start on #120; work on it when you can.
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 ?
https://privatekeys.pw/puzzles/bitcoin-puzzle-tx
Puzzle 64 - Keyspace 8000000000000000...ffffffffffffffff ?
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?
No.
I looking to way can calculate or can focus to keyspace nearly key but not found the way
now you can only random keyspace and hop to lucky
best method is bruteforce
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?
He used a deterministic wallet.
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?
Sorry for the stupid question.
But how can I import private key found by Pollard's kangaroo ECDLP solver? E.g. 0x60F4D11574F5DEEE49961D9609AC6
Electrum does not recognize it.
But how can I import private key found by Pollard's kangaroo ECDLP solver? E.g. 0x60F4D11574F5DEEE49961D9609AC6
Electrum does not recognize it.
Make it size of 256 bits.
0000000000000000000000000000000000060F4D11574F5DEEE49961D9609AC6
and put it in wallet details as example on www.bitaddress.org
Don't input your private key on a website. This is a security best practice.
While there doesn't exist a convenient program that you can run offline and convert a hex private key with it, there does exist scripts like this one you can run in a Python shell (vouching for this one in particular because I myself am using it in my code).
Sorry for the stupid question.
But how can I import private key found by Pollard's kangaroo ECDLP solver? E.g. 0x60F4D11574F5DEEE49961D9609AC6
Electrum does not recognize it.
But how can I import private key found by Pollard's kangaroo ECDLP solver? E.g. 0x60F4D11574F5DEEE49961D9609AC6
Electrum does not recognize it.
Make it size of 256 bits.
0000000000000000000000000000000000060F4D11574F5DEEE49961D9609AC6
and put it in wallet details as example on www.bitaddress.org
Thanks!
Sorry for the stupid question.
But how can I import private key found by Pollard's kangaroo ECDLP solver? E.g. 0x60F4D11574F5DEEE49961D9609AC6
Electrum does not recognize it.
But how can I import private key found by Pollard's kangaroo ECDLP solver? E.g. 0x60F4D11574F5DEEE49961D9609AC6
Electrum does not recognize it.
Make it size of 256 bits.
0000000000000000000000000000000000060F4D11574F5DEEE49961D9609AC6
and put it in wallet details as example on www.bitaddress.org
Jump to: