Post
Topic
Board Bitcoin Discussion
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
by
kTimesG
on 16/09/2024, 01:22:52 UTC
Me too, I thought whoever found the private key would go through Mara's slipstream, that no one would dare go through mempool directly but how wrong I was.

The thief who stole the coins must have a nice setup, it took his bot 45 seconds to replace the transaction, I assume whether he used BSGS or Kangaroo, it took 30 seconds to find the private key and the remaining 15 seconds for opening and shutting down apps.

kTimesG bragged about having a very fast setup and also started precalculating tames for 66bit, 67bit... Preparations you would only need if you plan to steal the transaction sitting in the mempool.
Every other user that took part in the stealing-bot-script discussions a few pages ago is suspicious.
The thief likely active here but would never confess because of repercussions...and well he would unmask as an asshole  Roll Eyes.

If that was the case it would have taken much less than 45s to replace the original tx, as once you have the key it might take less than 1 second to relay the first replacement.

WTF? Yes, any 66 bit private key can be cracked in less than 1 second and replaced in the next second, if you have some precomputed data which takes somewhere like just a few hours to create, not years. Guess what? The same thing applies to bits 67, 68, 69, etc ... But come on, anyone serious in here already knows this, or at least they should. Maybe it was a manner of tens of seconds or minutes for someone who's still in 2019.

And experimenting for a higher purpose is not "preparing to steal a transaction", it's called progress towards solving higher bits. I think I went through at least 500 versions of precomputed DBs for bits in the 50 80 range, and this just for testing that my own code actually works. One of the reasons I didn't care to leave some bot running, but what went down with 66 is a good reminder that only the universe is greater than human stupidity.