Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
...follow-up from my last post:
These are two of his test values (the last two in the list):
The one labeled "target" does appear to be, in fact, the compressed public key for puzzle #40... However, the one just above that is labeled "+ 549755814000", but when I convert it to a BigInt it's *lower* than the actual public key as BigInt (despite the fact that he supposedly got it by *adding* 549755814000 to the public key)...
So, either this test/example data is all wrong, or I've **completely** misunderstood it... Because when *I* add 549755814000 to the public key (and then convert it back to hex) I get:
...and those are almost exactly the same except for the last 12 chars, which is exactly what I would expect to get.
So, what am I missing? Or am I doing it correctly, and it's the example data that's wrong...?
Please someone help me here, this is driving me crazy
Edit: This was posted while I was writing the above:
Thanks for this, I took a quick look and I think my brain's just too fried for the day for me to understand what they're saying, expecially since they don't appear to be about keyhunt's "xpoint mode" specifically... I'll take a closer look later, or tomorrow, but in the meantime if someone can just answer the above questions directly I would greatly appreciate it...
These are two of his test values (the last two in the list):
Code:
038d3711fd681e26c05b2f0cd423fa596e15054024e40add24a93bfa0c630531f1 # + 549755814000
03a2efa402fd5268400c77c20e574ba86409ededee7c4020e4b9f0edbee53de0d4 # target
03a2efa402fd5268400c77c20e574ba86409ededee7c4020e4b9f0edbee53de0d4 # target
The one labeled "target" does appear to be, in fact, the compressed public key for puzzle #40... However, the one just above that is labeled "+ 549755814000", but when I convert it to a BigInt it's *lower* than the actual public key as BigInt (despite the fact that he supposedly got it by *adding* 549755814000 to the public key)...
So, either this test/example data is all wrong, or I've **completely** misunderstood it... Because when *I* add 549755814000 to the public key (and then convert it back to hex) I get:
Code:
03a2efa402fd5268400c77c20e574ba86409ededee7c4020e4b9f0edbee53de0d4 # target
03a2efa402fd5268400c77c20e574ba86409ededee7c4020e4b9f0ee3ee53de144 # + 549755814000
03a2efa402fd5268400c77c20e574ba86409ededee7c4020e4b9f0ee3ee53de144 # + 549755814000
...and those are almost exactly the same except for the last 12 chars, which is exactly what I would expect to get.
So, what am I missing? Or am I doing it correctly, and it's the example data that's wrong...?
Please someone help me here, this is driving me crazy
Edit: This was posted while I was writing the above:
Here's https://bitcointalk.org/index.php?topic=5347863.0 and https://bitcointalk.org/index.php?topic=5218972.680
there are also more topics on this that you can find if you search for them.
Also in this topic you can a python script by Etar for public key division.
there are also more topics on this that you can find if you search for them.
Also in this topic you can a python script by Etar for public key division.
Thanks for this, I took a quick look and I think my brain's just too fried for the day for me to understand what they're saying, expecially since they don't appear to be about keyhunt's "xpoint mode" specifically... I'll take a closer look later, or tomorrow, but in the meantime if someone can just answer the above questions directly I would greatly appreciate it...