 Show Posts
|
|
Pages: [1] 2 »
|
I see this thing is still going, has anyone solved any of the puzzles yet? Or has anyone made any type of progress? Can I get a TLDR of the events over the years from the start of the puzzle until now?
Over how many years exactly? 😂, #65 and #120 been solved. Prize has been increased 10 fold, now there is around 1000 bitcoins for us to loot ( yeah right). You forgot one important detaill: puzzle #65 was solved before #64. Idk why!!!  |
|
|
|
Edit: Example of a strange public key: 0400000000000000000000003b78ce563f89a0ed9414f5aa28ad0d96d6795f9c633f3979bf72ae8202983dc989aec7f2ff2ed91bdd69ce02fc0700ca100e59ddf3 0400000000000000000000003b78ce563f89a0ed9414f5aa28ad0d96d6795f9c63c0c686408d517dfd67c2367651380d00d126e4229631fd03f8ff35eef1a61e3c Find their difference, also after that check 69 and 96 as hex, convert them to decimal and compare their values and difference in values, as I have said before this is an ocean, and somehow the designers of EC and the math involved either used magic to come up with these equations, or I am still unable to fathom the infrastructure underneath them all, yet. Do not rely on existing tools, if you can come up with new solutions, share them if they can not be used to endanger coins other than puzzle coins. Otherwise you should not reveal anything if it can be exploited to steal coins from people. That's bullshit mate. These are freaking completely normal VALID public keys and have of course private keys that are connected to the them. There is nothing strange with them or what so ever.... Just because a public key has many zeros does not make it "weird" or "strange". Here's a VALID private key with many zeros. Is it weird? 000000000000000000000000000000000ffff000000000001111111111100000
It's actually interesting to see public keys that follow this pattern. The keys produce the following addresses when they are uncompressed:
./calculatefrompublickey 0400000000000000000000003b78ce563f89a0ed9414f5aa28ad0d96d6795f9c633f3979bf72ae8202983dc989aec7f2ff2ed91bdd69ce02fc0700ca100e59ddf3
address 16qakrWzEAPvDsY1yMdCrkgAWZ6DxpTK4z
./calculatefrompublickey 0400000000000000000000003b78ce563f89a0ed9414f5aa28ad0d96d6795f9c63c0c686408d517dfd67c2367651380d00d126e4229631fd03f8ff35eef1a61e3c
address 14szHdohyNkdE3XdiwUw1wNmuBUamPBXiS
at compressed format they produce the following addresses (and they had an out transaction meaning they have a valid private key)
./calculatefrompublickey 0200000000000000000000003b78ce563f89a0ed9414f5aa28ad0d96d6795f9c63
address 13see6qjfupx1YWgRefwEkccZeM8QGTAiJ
./calculatefrompublickey 0300000000000000000000003b78ce563f89a0ed9414f5aa28ad0d96d6795f9c63
address 1LVAsnUyEtJgZ9HzLfbtiJZuZMzHLX1n6k
|
|
|
|
I think the real question is who withdrew 2600 USD from key 0x01 in under six minutes  I am sure that are bots watching the mempool of probably multiple chains.. If it's done on ETH it should disappear as well. |
|
|
|
Is there gonna be an updated topic saying 900 bitcoin puzzle or what?
I say that we should not make noise, only those of us who are already aware.  Human greed is under the test right now  |
|
|
|
If all it takes is 100k GPUs (and I believe this to be true) then the answer to the time it takes to brute force is not 'Infinity' or 'almost impossible'. There are millions of GPUs in the world. Think about this, the group here and at least one other group has created a pool in the past to crack one of the puzzles. Imagine if this group can find 100k GPU owners to join. Impossible? Not really, imagine a black hat hacker figures a scheme to create a virus that is highly viral. He could in theory infect 500k computers with GPUs and bruteforce the key. Highly unethetical and illegal, but that's not the point. The point is that there are ways to do it. So, can it be done? Fortunately, bruteforcing a key here and there is different from figuring a way to crack any key which would be the holy grail to killing bitcoin or at least forcing a change in the technology. Another point I want to make - some of you have alluded to needing new technology, so something you may want to look at is the distribution of the random number generators used. 1. Imagine if the puzzle creator did use some random number generator, one could in theory figure out the distribution using the already cracked keys and target the main area of distribution. 2. Some of the tools used to crack the key uses random number generators, figure out the distribution and find a way to make it more linear or alter it to match the distribution of the rnd() used by the puzzle creator. I just calcualted how much time does it need to crack puzzle 66 by bruteforcing
The answer is: Infinity OR almost Impossible.
What's insane is, even if someone managed to get 100,000 GPUs, you still would need 3.5 Months to go through all the 66 range. Not to mention electricity cost of the 100,000 GPUs. I think this puzzle is still infeasible. It's worth to mine better than trying to solve this. Or if Satoshi increases the prize again by 10x, so for puzzle 66, 166.6BTC, for puzzle 67, 166.7BTC and so on. THEN it will be worth investing huge mining army to destroy it. Other than that it makes less sense.
What's feasible though is puzzle 125, because of its public key.
Also correct. Btw, i noticed most ppl are intimidated by 66 like i was few weeks ago, but when i studied #125, it got me thinking: ppl will find #66 waaaaaay before #125. The difficulty of 125 is really terrifyingly huge, even with the fact that its public key was exposed. (Take the difficulty of #120 .. and make 32 copies of it. Voila! now you have puzzle #125) What really people are underestimating is the power of luck too. This is easier than mining because there is no variables changing (such as prev block, merkle root, difficulty, etc) . The range to be scanned doesn't change. I am sharing the approach I am using to solve a part of the puzzle. It might help anyone or perhaps guide us to a better solution. I am using Keyhunt made by Albertobsd. ./keyhunt -f 66_67_68_69.txt -m rmd160 -l compress -t 32 -r 30000000000000000:180000000000000000 -R -n 10240
below content of the 66_67_68_69.txt file. 20d45a6a762535700ce9e0b216e31994335db8a5
739437bb3dd6d1983e66629c5f08c70e52769371
e0b8a2baee1b77fc703455f39d51477451fc8cfc
61eb8a50c86b0584bb727dd65bed8d2400d6d5aa
I added a little twist the start / end range with the following criteria start range at 2**66 + 2**63 end range at 2**69 - 2**67 I am confident that at least 3 keys should be present in the range that I mentioned. Anyway, try it at your own risk and I am open if anyone else has a better solution! Happy hunting! |
|
|
|
You guys don't even know that Satoshi is watching this thread secretly. If he isn't watching it, then he wouldn't have funded $15 Million WTF dollars. Because of this, I have officially decided to beg Satoshi every day here on this thread for Bitcoins. Starting from Today, #Day 1 Dear honey Satoshi, you have a lot of money so donate us some  32NYX3o1FDegf6nJiqKLi4DE25LYzSd72BThanks  It's totally understandable why Satoshi's identity was better to stay secret |
|
|
|
Guys I am facing a challenging puzzle of some sort, if you could answer better, else I'll go post it elsewhere!
Can anyone give me the uncompressed public key of the following?
0300000000000000000000001dbc672b1fc4d076ca0a7ad5145686cb6b3cafce31
This is not a valid private key length here you go 0400000000000000000000001dbc672b1fc4d076ca0a7ad5145686cb6b3cafce31fffffffffffff ffffffffffffffffffffffffffffffffffffffffffefffffc2fused secp256k1 lib of iceland2k14 import secp256k1
print(secp256k1.pub2upub('0300000000000000000000001dbc672b1fc4d076ca0a7ad5145686cb6b3cafce31').hex())
|
|
|
|
Only if I knew how to automate this process!
Could you at least share the process, maybe some code somewhere can help you automate it. +1 I am also interested but I think it's just playing with the ripemd160 hash |
|
|
|
Can you share at least two private key from each list to be sure there is a process to begin with? With the speed which I am progressing, you'd need to wait 40,000 years before I can get a single private key for one of the addresses, and that would be the address for #66, given everybody know exactly where to look.🤣 This is so inspiring! Thank you! |
|
|
|
WOW, guys look what I found, seek and you shall find; 13zb1hQbWVsc2S7ZTZnP2G4undNPCTfqJZ
13zb1hQbWVsc2S7ZTZnP2G4undNP7kEP7M
13zb1hQbWVsc2S7ZTZnP2G4undNNwgQut1
13zb1hQbWVsc2S7ZTZnP2G4undNNvZeouk
13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so
13zb1hQbWVsc2S7ZTZnP2G4undNNgMUm4n
13zb1hQbWVsc2S7ZTZnP2G4undNNViSuhK
13zb1hQbWVsc2S7ZTZnP2G4undNNTCnWQi
13zb1hQbWVsc2S7ZTZnP2G4undNNMNtEnp
13zb1hQbWVsc2S7ZTZnP2G4undNNEaaHF4
13zb1hQbWVsc2S7ZTZnP2G4undNPNuwE3h
13zb1hQbWVsc2S7ZTZnP2G4undNPQxu217
13zb1hQbWVsc2S7ZTZnP2G4undNPZxBxnH
13zb1hQbWVsc2S7ZTZnP2G4undNPf3VD6N
13zb1hQbWVsc2S7ZTZnP2G4undNPnJ2jFS
13zb1hQbWVsc2S7ZTZnP2G4undNPsJ7T9P
13zb1hQbWVsc2S7ZTZnP2G4undNPygXueW
13zb1hQbWVsc2S7ZTZnP2G4undNQ59XjMk
13zb1hQbWVsc2S7ZTZnP2G4undNQGH2W2c
13zb1hQbWVsc2S7ZTZnP2G4undNQPnwQJw 1111111111111111111114oLvT2
11111111111111111111BZbvjr
11111111111111111111HeBAGj
11111111111111111111QekFQw
11111111111111111111UpYBrS
11111111111111111111g4hiWR
11111111111111111111jGyPM8
11111111111111111111o9FmEC
11111111111111111111ufYVpS
1111111111111111111127DiY8B
111111111111111111112BEH2ro
111111111111111111112KWC9yd
111111111111111111112MbYeKK
111111111111111111112WhxnQF
111111111111111111112czxoHN
111111111111111111112kmzDG2
111111111111111111112xT3273
1111111111111111111135LjaTk
111111111111111111113BCNaZA
111111111111111111113MEMrbm
111111111111111111113UauxVS
111111111111111111113Vsgn16
111111111111111111113h6eYvj
111111111111111111113iqSWm1
111111111111111111113twUjvB
111111111111111111114gFexwh
111111111111111111114mA2k9d
111111111111111111114ry6XwB
111111111111111111114ysyUW1
111111111111111111115719xWh
111111111111111111115GZoCZK
111111111111111111115Jk6jSN
111111111111111111115Vdmk4z
111111111111111111115bqgQLs
111111111111111111115hA977A
111111111111111111116WGuH8i
111111111111111111116ayzEtU
111111111111111111116iBpJVP
111111111111111111116p9wW39
111111111111111111116xyhaXw
111111111111111111116zvHYMP
1111111111111111111178p8Uvz
111111111111111111117HhpFr4
111111111111111111117MncoQu
111111111111111111117TDMMQQ
111111111111111111118GEJCAf
Only if I knew how to automate this process! Can you share at least two private key from each list to be sure there is a process to begin with? |
|
|
|
I just found 66
well congrats, what are you waiting for to claim the btc? |
|
|
|
Hello there all Congratulations to the solver of the PrivKey #64 PrivKey Hex: 000000000000000000000000000000000000000000000000F7051F27B09112D4 PrivKey WIF: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ6FxoaD5r1kYegmtbaT Pubkey: 03100611c54dfef604163b8358f7b7fac13ce478e02cb224ae16d45526b25d9d4d Address: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN This is amazing, Congrats to the winner! I personally needed this piece of evidence that this puzzle is not a scam. I am gonna try harder this time. |
|
|
|
I just created a cryptocurrency called denaro. I used Python and PostgreSQL. It's a fully working crypto written by 0, it does not operate on any external blockchain like ethereum, it does have his blockchain. It started like "let's see if i can really make it", and it ended that i did it. It can theoretically confirm up to 5 transactions per second, with a maximum block size of 2mb. You can find it on github: https://github.com/denaro-coin/denaro. If you wanna contribute, you're welcome. I also created a telegram bot wallet (@DenaroCoinBot), so feel free to pm me on @gaetano555 and i'll send you some. I have been always looking for a project like this. A blockchain that's built out of a programming language that's widely used and reasonable total supply. Are you satoshi by any chance? |
|
|
|
Hi! I am looking into this challenge and wondering.. Could be the address of some puzzles was generated from an uncompressed public key? from what I know you can't tell if the address is compressed or uncompressed by just looking at it.. or am overthinking it? :/
Overthinking it. If you read back through the history of this challenge, the creator stated they were compressed. And all keys found thus far have been found using compressed format. well I hope so, but I don't remember that I have encountered a statement from the creator of this puzzle that explicitly says the addresses are compressed. I started to question it indeed when I see this challenge laying around for years with no progress.. a lot of questions arises.. maybe a lot of people are doubting it.. anyway, I will spend some time here... |
|
|
|
|
Hi! I am looking into this challenge and wondering.. Could be the address of some puzzles was generated from an uncompressed public key? from what I know you can't tell if the address is compressed or uncompressed by just looking at it.. or am overthinking it? :/
|
|
|
|
Guys, I thought to bring this to attention of everyone since it appears that Pip is no longer able to post in this threat. He posted an update on his reddit thread called "Introducing the 310 BTC Bitcoin Challenge" So I am quoting that below: - Dec 03 2018: I am starting to lose interest in working on this because I get to hear evil people, constantly. They keep complaining how the challenge wasn't designed well and how I did not evenly distribute the prices. How stupid I am because I did not give to charity instead. Yelling and begging at the same time. In comparison I hardly get (friendly) messages from people actually working on this or at least appreciating it. Reddit closed my post, bitcointalk blocked my vpn provider, and there's no fun in reading messages and be called shit every day. I honestly don't think I deserve that?
I started working on the smaller challenges a while ago but I have the feeling nobody appreciates it. I do no longer enjoy working on them after reading all that shit every day. For this reason I cancelled them. I will start working on the next bigger (300 BTC) challenge instead. Yet, you must be patient.
The next one will be thoroughly tested first (and it takes time). It will be way more difficult, yet won't require the same amount of technical computer skills. It'll be a totally different game and hopefully won't be solved as fast as the first one.
Last but not least: please don't forget the 0.31 BTC wallet is yet to be solved!
- Dec 03 2018: 17 minutes after posting the above I got a message saying it doesn't make sense to start the next big challenge if I don't even feel like working on the smaller ones anymore. The writer sounds very mad at me, called me stupid. I didn't even do anything?
Let me clarify this: I honestly don't like the feedback I'm getting lately. It feels like many people are mad at me for no reason. I do not enjoy this situation at all.
I already arranged things for the next big challenge and it's being worked. I won't cancel that one. But depending on the attitude of people this might be the last one too. I didn't expect so much "hate mail" from people without even doing anything.
Good luck!
Pip source: https://www.reddit.com/r/Bitcoin/comments/9kq7it/introducing_the_310_btc_bitcoin_challenge/ |
|
|
|
Ok, I'm working on something but it'll probably lead nowhere ( like most of you ) . So when is the next challenge, someane on discord mentioned a new 300 btc challenge but i can't seem to find it. Does anyone know?
I am working on the 0.31btc I've managed to find the next salted encryption and bruteforce it, however the output file is another encrypted message that I can't seem to understand what to do next. T_T you might get a hint if you hash the output you managed to find and submit it in the link below https://bitcoinchallenge.codes/register-310/ good luck! |
|
|
|
There is a miner written in pure python compatible with rpc getblocktemplate. Feel free to check it out. https://github.com/vsergeev/ntgbtminerIt helped me a lot to understand how mining works. |
|
|
|
So, anyone still working on this, any updates?
I am curious to know that as well. The 0.31 BTC reward is still not claimed yet. I wonder if it's the time for Pip to share some hint(s). |
|
|
|
For anyone who is interested to mine as well. I used the following cpuminer: https://github.com/pooler/cpuminer/releasesHere is a step by step tutorial how to get it up and running (assuming that you have your wallet set and rpc server is active) Step 1Download the latest release which is currently v2.5.0 If your OS is 32bits use the “pooler-cpuminer-2.5.0-win32.zip” file If it’s not use “pooler-cpuminer-2.5.0-win64.zip” Step 2Extract the archive where it’s convenient for you Step 3Create a .bat file where the extracted files are located, we will use “ocean.bat” in this example. Paste the following code: #ocean.bat for minerd
minerd -a sha256d -o 127.0.0.1:4699 --no-getwork --no-longpoll -u rpc_oceans -p 42f2a0be5caae9449f5e2f795 -t nthreads --no-stratum --coinbase-addr myaddress --coinbase-sig mysig --scantime 1800
PAUSE make sure to make the following changes: nthreads to the number of threads if your cpu has 8 threads try “–t 7” myaddress to your address mysig to any value, basically it will appear as the coinbase signature in the blockchain Recommandationdepending on how fast your cpu try to play with –scantime value try values between 300 and 1800 In order to check how it is going see the example below, your balance should be updated if your block was accepted. Rejected block[2018-12-25 16:25:37] thread 2: 89695456 hashes, 13292 khash/s [2018-12-25 16:25:37] accepted: 22/25 (88.00%), 53574 khash/s (booooo) Accepted block[2018-12-25 16:28:36] thread 2: 426710624 hashes, 13442 khash/s [2018-12-25 16:28:36] accepted: 23/26 (88.46%), 53774 khash/s (yay!!!) Couple of tips:Make sure –t argument has a slightly lower value than the number of cores/ threads that you have I do not recommend mining on a laptop for long sessions. Make sure that CPU temperature is less than 65° to avoid damaging your hardware. You can check that with speccy. Wow. Thank you! Glad that I could help. I did a slight change in the code just in the beginning of the first line. I might do further changes in the future. If anyone has a question or facing issues please feel free to share it in this thread. |
|
|
|
|
