It's bullshit (or I compute the addresses wrongly).
It is not bullshit, you just do not understand that for every private key there are two formats for the public key. They are the uncompressed format and the compressed format. From these two formats of the public key you get two different Bitcoin addresses. Private Key: 0000000000000000000000000000000000000000000000000000000000000003 Uncompressed format of the Pubic Key (both the X and Y coordinates of the point on the elliptic curve): 04F9308A019258C31049344F85F89D5229B531C845836F99B08601F113BCE036F9388F7B0F632DE 8140FE337E62A37F3566500A99934C2231B6CB9FD7584B8E672 Bitcoin Address from the uncompressed format of the public key: 1NZUP3JAc9JkmbvmoTv7nVgZGtyJjirKV1Compressed format of the Public Key (the X coordinate only and a sign bit for the Y coordinate): 02F9308A019258C31049344F85F89D5229B531C845836F99B08601F113BCE036F9 Bitcoin Address from the compressed format of the public key: 1CUNEBjYrCn2y1SdiUMohaKUi4wpP326LbNow this will blow your mind:For every Bitcoin Address there are about 2 96 = 79,228,162,514,264,337,593,543,950,336 valid possible Public/Private key pairs! [EDIT: fixed, I did not have my coffee before I wrote the first version of this and it was totally backwards and wrong.] |
|
|
|
Thanks for starting and maintaining this thread. Too bad you did not make it moderated so you could remove all the crap posts. +Merit Note you could switch your "table" in the OP to a fixed width font so it will all line up better by putting it in a "code" block like this: This is a fixed width font
So everything will line up
nicely
Also, to avoid confusion I would remove the word "prize" from your subject and all references in the OP. |
|
|
|
So there is proof of this? It makes sense I just don't see any proof of who owns the bitcoins and don't feel like searching through a huge thread to find a needle in a haystack. Can you actually provide something useful? All I see is random info without anything to back it up except a simple-minded insult?
On this very page. Search for " I am the creator". Simple minded insult? How about your very insulting first post in this thread: So basically stealing someone's Bitcoin? What if you had that 32 BTC and someone stole it from you, what is wrong with you guys? This is such a shitty community that you guys would call someone's own hard-earned Bitcoin a "prize" and even bounty it. You are the reason Bitcoin has such a bad wrap.
In that post you insulted everyone in this thread. At least I am only insulting you: Decimation, too lazy to even read one page of a thread before asking everyone else to do your thinking and reading for you. Yikes, everyone on this forum is so tense and ready to lash out at any moment, maybe its the stress? Yes, I am too lazy to read an entire 60-page thread, I don't think that's outrageous. The OP has literally no information, or link to it. Also, you still don't provide any sort of answer to my question? To me, it seems like you are justifying theft? "It's meant for us to steal", "The corporations are bad, they make so much money anyway", Why would you need to crack something if it belonged to you? Have some perspective for a minute before raging. You started this by ignorantly rage calling everyone thieves. Read the post from the creator of the puzzle. It is on the previous page. Just go back to the previous page. You are lucky. Someone copied his quote there for you. You do not have to read all 60+ pages - just go back one page and read that page. I even told you a string to search for on that page. If you are too lazy to do even that then I have nothing else to say to you. |
|
|
|
So there is proof of this? It makes sense I just don't see any proof of who owns the bitcoins and don't feel like searching through a huge thread to find a needle in a haystack. Can you actually provide something useful? All I see is random info without anything to back it up except a simple-minded insult?
On this very page. Search for " I am the creator". Simple minded insult? How about your very insulting first post in this thread: So basically stealing someone's Bitcoin? What if you had that 32 BTC and someone stole it from you, what is wrong with you guys? This is such a shitty community that you guys would call someone's own hard-earned Bitcoin a "prize" and even bounty it. You are the reason Bitcoin has such a bad wrap.
In that post you insulted everyone in this thread. At least I am only insulting you: Decimation, too lazy to even read one page of a thread before asking everyone else to do your thinking and reading for you. |
|
|
|
The original poster of this thread back in 2015 should go back and change the topic of this title. Because we are getting the same questions asked over and over again and it creates alot of confusion when it says "Puzzle" in the topic while this in fact is not a puzzle.
A puzzle is something that you can solve with a pattern, kind of like solving some mystery.
However the way you solve these private keys is mostly by brute force and its no different than solving for any private key the only difference is that these are low entrophy.
So instead of this being a puzzle its more of a test of human coding skills and available CPU and GPU and FGPA hardware.
Did you PM him? |
|
|
|
okay, if there's no secrets on private keys for bitcoin puzzle wallets,(if choosed randomly)
how it's puzzle wallet then? it's not puzzle, it's just searching for luck for the one random of keys between trillions of keys.
we can't solve , because there;s no secret in it, but we can keep searching and try our luck, is not?
Your question could be answered by reading the very first post in this thread. Do that. Did you do that? I am betting not. Perhaps the title of the thread should really be "Mysterious Bitcoin Transaction" but instead it is "Bitcoin puzzle transaction". |
|
|
|
It is still called "the 32 BTC prize" but the prize is really more than 100 BTC ...
From where you have this calculations?  on 2015-01-15 18:07:14 the total prize was ----------------------------> 32.896 BTC on 2017-04-21 18:08:01 #1 to #52 were spent (-1.378 BTC )--------> 31.518 BTC on 2017-07-11 04:53:52 #161 to #256 where spent (- 20.16BTC) and cases from #53 to #160 where multiplied by 10 --------------------> 115.02 BTC (new prize) At this day, we are left with: 0.62 + 0.64 + 0.66 + 0.67 + 0.68 + 0.69 + 0.71 + 0.72 + 0.73 + 0.74 + 0.76 + 0.77 + 0.78 + 0.79 + 0.81 + 0.82 + 0.83 + 0.84 + 0.86 + 0.87 + 0.88 + 0.89 + 0.91 + 0.92 + 0.93 + 0.94 + 0.96 + 0.97 + 0.98 + 0.99 + 1.01 + 1.02 + 1.03 + 1.04 + 1.05 + 1.06 + 1.07 + 1.08 + 1.09 + 1.10 + 1.11 + 1.12 + 1.13 + 1.14 + 1.15 + 1.16 + 1.17 + 1.18 + 1.19 + 1.20 + 1.21 + 1.22 + 1.23 + 1.24 + 1.25 + 1.26 + 1.27 + 1.28 + 1.29 + 1.30 + 1.31 + 1.32 + 1.33 + 1.34 + 1.35 + 1.36 + 1.37 + 1.38 + 1.39 + 1.40 + 1.41 + 1.42 + 1.43 + 1.44 + 1.45 + 1.46 + 1.47 + 1.48 + 1.49 + 1.50 + 1.51 + 1.52 + 1.53 + 1.54 + 1.55 + 1.56 + 1.57 + 1.58 + 1.59 + 1.60 = 102.66 BTC Thanks for that calculation! 10 brownie points! |
|
|
|
So basically stealing someone's Bitcoin? What if you had that 32 BTC and someone stole it from you, what is wrong with you guys? This is such a shitty community that you guys would call someone's own hard-earned Bitcoin a "prize" and even bounty it. You are the reason Bitcoin has such a bad wrap.
Tap on the matte canteen. Read the topic from the beginning, then come back here, remove your miserable post and beg forgiveness. I have no idea what the phrase means, and no I won't. It's not your money nor do you deserve it. The owner of these Bitcoins spent them to low entropy private keys on purpose in order to test the security of the Bitcoin system. He wants everyone to try and take them. He then issued a spend transaction from some of the addresses in order to test the security of low entropy private keys with spend transaction. He did all of this on purpose in order to test the system. For helping with this test people are being paid for their efforts. This is not stealing it is people being paid for a service. Learn to first read and understand a thread before you dump a steaming pile of your uninformed dumb ass opinion on it. |
|
|
|
For the creator this puzzle, I have some question  What next step after we on this step https://www.youtube.com/watch?reload=9&v=MFatdCqzM9o Because I don't see any more clue on there, are we finis after this step ? and the name this puzzle " The Gold Gate" Let me know if any more step.............. weirdo |
|
|
|
You are off with the numbers.
Security is 128 bit for 256 bit public keys, and 50 bit for 100 bit pk.
So the security headroom is 128-50 = 78 bits.
oops, thanks, and fixed. |
|
|
|
Does not look like a coin as we know them. I think that Facebook is simply creating an electronic means of transfer with and averaged monetary unit similar to an SDR of the IMF. This is a bold move from Facebook that is just steping onto the Insurance, Banking, Transference, Direct Sales and even on the monopoly of governments to create money. I won´t use it if I can avoid it, but being honest, this is a "world takeover" by Zucky and some other Bilderberg´s friends. Once this becomes big enough, they will have a government above all governments, and I am not overstating anything. My guess is that Facebook will abandon this whole thing eventually. Once they fully realize the amount of regulation they are up against: license in every state, different licenses and requirements per country, reporting requirements for all countries, etc. etc. Banking is the most heavily regulated thing that Facebook can try to do. Jumping into this much regulation is not their style. But on the other hand if they can make enough money selling everyone's spending habit information to the highest bidder it may be worth the pain. They have to be able to gather and sell enough private information on their victims "customers" to make it worth dealing with all those regulations. |
|
|
|
that's the puzzle developer wants to see  If now investors in bitcoin learn that a small bunch of intusiasts with the help of improvised means were able to find private keys in 100 bit space ,then what will happen to this whole story if it is seriously engaged in professionals with cool equipment and leading programmers.And I wonder how soon the cost of cryptocurrencies will cost $ 0. Currently not an issue for those that use proper secure random full entropy 256 bit private keys even if the attackers use "cool equipment and leading programmers". These keys still have 128 bits of security even with the current search algorithms. The current record on this thread is 100 bits which leaves 128 - 50 = 78 bits of headroom. Assuming 115 bits is possible then that still leaves 128 - 58 = 70 bits of headroom. If you want your coins to be more secure than that then use a standard 160 bit Bitcoin address and never reuse your Bitcoin addresses. If you want even more security then use a 256 bit Bitcoin address and never reuse your Bitcoin addresses. Finally, if there is a breakthrough and ECDSA is deemed less secure then Bitcoin will simply switch to another algorithm with network consent - which I believe would happen given a known reduction in the security of the ECDSA (as long as the change did not try to sneak in a whole lot of extra baggage with it). |
|
|
|
Step "5" is not a sudden one, there is definitely something behind it! Otherwise if you have a way to recover the private key from four addresses with total amount of 3.7 BTC why wouldn't you do it???
Explained in the thread if you bothered to read it. #80: 0xea1a5c66dcc11b5ad180
#85: 0x11720c4f018d51b8cebba8
#90: 0x2ce00bb2136a445c71e85bf
#95: It wasn't me
#100: Also not me
Three more to go to a new world record. Obviously it is much easier to get the private key when there is a spend transaction on the address. #1 through #61 took a long time whereas #65, #70, #75 and #80 were snatched up pretty soon after the author added the spend transaction to those addresses. I expect #85 will also be snatched up in due time.
As discussed #85, #90, #95, #100, #105, #110 are all within the realm of possibility given enough time and resources. It looks as if #115 would be a new world record so someone with enough equipment and motivation can probably get that one. Beyond that it is very iffy.
It will be interesting to see how far people can/will go on this. |
|
|
|
I don't know why but I'm smelling a big scam.
You are smelling a big scam because you did not bother to read the thread and came in here and dumped a stinking pile of your uninformed opinion on the thread. What you are smelling is not a scam but your own steaming pile of opinion. |
|
|
|
My understanding is there is a bit of a trade off here.
When there is no spend transaction the search method is:
Next Private Key -> Public Key -> Hash -> Bitcoin Address -> Compare Bitcoin Address, repeat until found
Note that due to the hashing functions used the Bitcoin Address is expected within a private key range of only 2160
When there is a spend transaction the search method is:
Next Private Key -> Public Key -> Compare Public Key, repeat until found
Note that the private key range in this case is the full 2256 but there are ways to speed up the process
So, I think full entropy 256 bit private keys are still safe even with multiple spend transactions, but they may be less safe than a 160 bit Bitcoin address from a full entropy 256 bit private key with no spend transactions.
Even better yet is a longer full 256 bit Bitcoin address based on a full entropy 256 bit private key with no spend transactions.
I understand but why can't a HBM2 16GB GPU do this faster than a system with a fast CPU + loads of system RAM. I am not too technical on the details here but I understand that if you know the private key you can easily compute the public key, but not the other way around. So since the search space is small, basically most of the private key starts with 0's then you can easily start a range at the small private keys basically something like " 000000000000000000000000000000000000000000000001A838B13505B26867 " So the GPU would take that and increment it and compute the public key very fast and just compare it to the public key with the funds inside it. What you are describing is the "brute force" method which can be done even faster than you think. Since the PublicKey = PrivateKey * G (where G is an agreed to point on the elliptic curve and * is the defined scalar multiplication operation over the finite field of points on the elliptic curve) you can do the following: 0) Initialize PrivateKey to the start of the range you are interested in 1) Calculate the first PublicKey = PrivateKey * G 2) Compare the PublicKey to the target PublicKey, if they match then you are done and PrivateKey is the private key you are looking for 3) PrivateKey = PrivateKey + 1 4) PublicKey = PublicKey + G (instead of PublicKey = PrivateKey * G because adding the point G to the current PublicKey point is faster than calculating the PublicKey point from PublicKey = PrivateKey * G "from scratch" every time through the loop) 5) Goto step 2) However, people that are doing this search are not using this "brute force" method. They are using a much faster method. This much faster method requires a lot of RAM. This faster method is described in detail in a very large post withing the last few pages of this thread. Check it out. |
|
|
|
|
My understanding is there is a bit of a trade off here.
When there is no spend transaction the search method is:
Next Private Key -> Public Key -> Hash -> Bitcoin Address -> Compare Bitcoin Address, repeat until found
Note that due to the hashing functions used the Bitcoin Address is expected within a private key range of only 2160
When there is a spend transaction the search method is:
Next Private Key -> Public Key -> Compare Public Key, repeat until found
Note that the private key range in this case is the full 2256 but there are ways to speed up the process
So, I think full entropy 256 bit private keys are still safe even with multiple spend transactions, but they may be less safe than a 160 bit Bitcoin address from a full entropy 256 bit private key with no spend transactions.
Even better yet is a longer full 256 bit Bitcoin address based on a full entropy 256 bit private key with no spend transactions.
|
|
|
|
So, right now only this BTC addresses left ? 1Me6EfpwZK5kQziBwBfvLiHjaPGxCKLoJi 0.062 BTC
1NpYjtLira16LfGbGwZJ5JbDPh3ai9bjf4 0.063 BTC
16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 0.064 BTC
13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so 0.066 BTC
1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9 0.067 BTC
1MVDYgVaSN6iKKEsbzRUAYFrYJadLYZvvZ 0.068 BTC
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG 0.069 BTC
1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU 0.071 BTC
1JTK7s9YVYywfm5XUH7RNhHJH1LshCaRFR 0.072 BTC
12VVRNPi4SJqUTsp6FmqDqY5sGosDtysn4 0.073 BTC
1FWGcVDK3JGzCC3WtkYetULPszMaK2Jksv 0.074 BTC
1DJh2eHFYQfACPmrvpyWc8MSTYKh7w9eRF 0.076 BTC
1Bxk4CQdqL9p22JEtDfdXMsng1XacifUtE 0.077 BTC
15qF6X51huDjqTmF9BJgxXdt1xcj46Jmhb 0.078 BTC
1ARk8HWJMn8js8tQmGUJeQHjSE7KRkn2t8 0.079 BTC
15qsCm78whspNQFydGJQk5rexzxTQopnHZ 0.081 BTC
13zYrYhhJxp6Ui1VV7pqa5WDhNWM45ARAC 0.082 BTC
14MdEb4eFcT3MVG5sPFG4jGLuHJSnt1Dk2 0.083 BTC
1CMq3SvFcVEcpLMuuH8PUcNiqsK1oicG2D 0.084 BTC
1K3x5L6G57Y494fDqBfrojD28UJv4s5JcK 0.086 BTC
1PxH3K1Shdjb7gSEoTX7UPDZ6SH4qGPrvq 0.087 BTC
16AbnZjZZipwHMkYKBSfswGWKDmXHjEpSf 0.088 BTC
19QciEHbGVNY4hrhfKXmcBBCrJSBZ6TaVt 0.089 BTC
1EzVHtmbN4fs4MiNk3ppEnKKhsmXYJ4s74 0.091 BTC
1AE8NzzgKE7Yhz7BWtAcAAxiFMbPo82NB5 0.092 BTC
17Q7tuG2JwFFU9rXVj3uZqRtioH3mx2Jad 0.093 BTC
1K6xGMUbs6ZTXBnhw1pippqwK6wjBWtNpL 0.094 BTC
19eVSDuizydXxhohGh8Ki9WY9KsHdSwoQC 0.095 BTC
15ANYzzCp5BFHcCnVFzXqyibpzgPLWaD8b 0.096 BTC
18ywPwj39nGjqBrQJSzZVq2izR12MDpDr8 0.097 BTC
1CaBVPrwUxbQYYswu32w7Mj4HR4maNoJSX 0.098 BTC
1JWnE6p6UN7ZJBN7TtcbNDoRcjFtuDWoNL 0.099 BTC
1KCgMv8fo2TPBpddVi9jqmMmcne9uSNJ5F 0.1 BTC
1CKCVdbDJasYmhswB6HKZHEAnNaDpK7W4n 0.101 BTC
1PXv28YxmYMaB8zxrKeZBW8dt2HK7RkRPX 0.102 BTC
1AcAmB6jmtU6AiEcXkmiNE9TNVPsj9DULf 0.103 BTC
1EQJvpsmhazYCcKX5Au6AZmZKRnzarMVZu 0.104 BTC
1CMjscKB3QW7SDyQ4c3C3DEUHiHRhiZVib 0.105 BTC
18KsfuHuzQaBTNLASyj15hy4LuqPUo1FNB 0.106 BTC
15EJFC5ZTs9nhsdvSUeBXjLAuYq3SWaxTc 0.107 BTC
1HB1iKUqeffnVsvQsbpC6dNi1XKbyNuqao 0.108 BTC
1GvgAXVCbA8FBjXfWiAms4ytFeJcKsoyhL 0.109 BTC
12JzYkkN76xkwvcPT6AWKZtGX6w2LAgsJg 0.11 BTC
1824ZJQ7nKJ9QFTRBqn7z7dHV5EGpzUpH3 0.111 BTC
18A7NA9FTsnJxWgkoFfPAFbQzuQxpRtCos 0.112 BTC
1NeGn21dUDDeqFQ63xb2SpgUuXuBLA4WT4 0.113 BTC
174SNxfqpdMGYy5YQcfLbSTK3MRNZEePoy 0.114 BTC
1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv 0.115 BTC
1MnJ6hdhvK37VLmqcdEwqC3iFxyWH2PHUV 0.116 BTC
1KNRfGWw7Q9Rmwsc6NT5zsdvEb9M2Wkj5Z 0.117 BTC
1PJZPzvGX19a7twf5HyD2VvNiPdHLzm9F6 0.118 BTC
1GuBBhf61rnvRe4K8zu8vdQB3kHzwFqSy7 0.119 BTC
17s2b9ksz5y7abUm92cHwG8jEPCzK3dLnT 0.12 BTC
1GDSuiThEV64c166LUFC9uDcVdGjqkxKyh 0.121 BTC
1Me3ASYt5JCTAK2XaC32RMeH34PdprrfDx 0.122 BTC
1CdufMQL892A69KXgv6UNBD17ywWqYpKut 0.123 BTC
1BkkGsX9ZM6iwL3zbqs7HWBV7SvosR6m8N 0.124 BTC
1PXAyUB8ZoH3WD8n5zoAthYjN15yN5CVq5 0.125 BTC
1AWCLZAjKbV1P7AHvaPNCKiB7ZWVDMxFiz 0.126 BTC
1G6EFyBRU86sThN3SSt3GrHu1sA7w7nzi4 0.127 BTC
1MZ2L1gFrCtkkn6DnTT2e4PFUTHw9gNwaj 0.128 BTC
1Hz3uv3nNZzBVMXLGadCucgjiCs5W9vaGz 0.129 BTC
1Fo65aKq8s8iquMt6weF1rku1moWVEd5Ua 0.13 BTC
16zRPnT8znwq42q7XeMkZUhb1bKqgRogyy 0.131 BTC
1KrU4dHE5WrW8rhWDsTRjR21r8t3dsrS3R 0.132 BTC
17uDfp5r4n441xkgLFmhNoSW1KWp6xVLD 0.133 BTC
13A3JrvXmvg5w9XGvyyR4JEJqiLz8ZySY3 0.134 BTC
16RGFo6hjq9ym6Pj7N5H7L1NR1rVPJyw2v 0.135 BTC
1UDHPdovvR985NrWSkdWQDEQ1xuRiTALq 0.136 BTC
15nf31J46iLuK1ZkTnqHo7WgN5cARFK3RA 0.137 BTC
1Ab4vzG6wEQBDNQM1B2bvUz4fqXXdFk2WT 0.138 BTC
1Fz63c775VV9fNyj25d9Xfw3YHE6sKCxbt 0.139 BTC
1QKBaU6WAeycb3DbKbLBkX7vJiaS8r42Xo 0.14 BTC
1CD91Vm97mLQvXhrnoMChhJx4TP9MaQkJo 0.141 BTC
15MnK2jXPqTMURX4xC3h4mAZxyCcaWWEDD 0.142 BTC
13N66gCzWWHEZBxhVxG18P8wyjEWF9Yoi1 0.143 BTC
1NevxKDYuDcCh1ZMMi6ftmWwGrZKC6j7Ux 0.144 BTC
19GpszRNUej5yYqxXoLnbZWKew3KdVLkXg 0.145 BTC
1M7ipcdYHey2Y5RZM34MBbpugghmjaV89P 0.146 BTC
18aNhurEAJsw6BAgtANpexk5ob1aGTwSeL 0.147 BTC
1FwZXt6EpRT7Fkndzv6K4b4DFoT4trbMrV 0.148 BTC
1CXvTzR6qv8wJ7eprzUKeWxyGcHwDYP1i2 0.149 BTC
1MUJSJYtGPVGkBCTqGspnxyHahpt5Te8jy 0.15 BTC
13Q84TNNvgcL3HJiqQPvyBb9m4hxjS3jkV 0.151 BTC
1LuUHyrQr8PKSvbcY1v1PiuGuqFjWpDumN 0.152 BTC
18192XpzzdDi2K11QVHR7td2HcPS6Qs5vg 0.153 BTC
1NgVmsCCJaKLzGyKLFJfVequnFW9ZvnMLN 0.154 BTC
1AoeP37TmHdFh8uN72fu9AqgtLrUwcv2wJ 0.155 BTC
1FTpAbQa4h8trvhQXjXnmNhqdiGBd1oraE 0.156 BTC
14JHoRAdmJg3XR4RjMDh6Wed6ft6hzbQe9 0.157 BTC
19z6waranEf8CcP8FqNgdwUe1QRxvUNKBG 0.158 BTC
14u4nA5sugaswb6SZgn5av2vuChdMnD9E5 0.159 BTC
1NBC8uXJy1GiJ6drkiZa1WuKn51ps7EPTv 0.16 BTC Are they using same algo with the first 50 one ? The algorithm used to produce the private keys is the same for all addresses. Most likely #95 will be the next one claimed - but it may take a while for that to happen. |
|
|
|
Yes, like I read everything, you can link to a certain post.
You sure a a lazy shit. Sure, I will give you the link for a fee. How much is it worth to you? I will accept BTC for payment. Looks like someone has found some kind of trick or regularity in calculations. Not really
Definitely it can't be luck with stepping 5 No, it is not luck
and and can't be hashing or brute-forcing. no hashing needed on these anymore, faster algorithm available for every fifth one
Just only if pentagon's admin decided to test the most powerful PC in the world with this puzzle address Probably not but, well maybe
https://bitcointalk.org/index.php?topic=1306983.msg51466379#msg51466379https://bitcointalk.org/index.php?topic=1306983.msg51474410#msg51474410 |
|
|
|
Why steping is 5???
Maybe reality collision found?
Please read the thread. Go back a few pages and read forward until you find the answer to your question. |
|
|
|
|
Later today I am going to update all my Trezors so I will report back the update time.
|
|
|
|
|
Show Posts
