Quote from: kTimesG on Today at 12:01:53 AM

Quote from: kTimesG on October 16, 2024, 02:34:36 PM

On Nov. 1st 2024 at 0:00 AM UTC I will post here a BTC P2PKH address (compressed) associated with an 80-bits secure private key.

The address owns 0.005 BTC (~340 $)

Get your tools ready boys.

Here it goes!

Code:

BTC Address(c): 1ECDLP8osCZHBB1LH5PVAUfFegeMgFb52q

minKey = 0x659756abf6c17ca70e0000000000000000000140be6ddd93e441f8d4b4a85653b20b4cdcc5c748207a0daa16191d07a425d8080c276f9412472e0429e61bc355
maxKey = 0x659756abf6c17ca70fffffffffffffffffffff40be6ddd93e441f8d4b4a85653b20b4cdcc5c748207a0daa16191d07a425d8080c276f9412472e0429e61bc355

I'll wait between 20 and 28 hours before the outgoing TX will be pushed.

SHA-256 of correct solve steps (will publish tomorrow at this time):

Code:

a6c39217128593909a1fcc0fd92c07a6f5abd32c36a8e7cf4e91f1a8f0651db0

---

Quote from: albert0bsd on October 31, 2024, 09:00:29 PM

Why not just publish some Signed text message here, anyone can get the public key from it. And the first user to solve it can redeem without worrying.

if you still wan to send the TX, please use 1 sat/vB for that TX get stuck on mempool fees.

The challenge involves correctly extracting pubkey from the raw TX, otherwise it's a no brainer.

What is a good way to set sat/vB such that it's both not stuck but also not urgent, e.g. mined in the block after next one? The challenge is not about "let's see if a 80 bit key can be cracked in less than 6 hours", we already have an answer to that.

it's your "challenge" so do it however you want, which you are doing, but some of your comments make no sense.

You say albert0's way is a no brainer, but I bet people can more easily retrieve a public key from an outgoing tx, then they can from a signed message. Both are easy, but in the questions sent to me, people struggle with knowing about or learning how to, break down a signed message.

What does this mean? You will give the step by step instructions on how to solve, before the outgoing transaction?

Quote

SHA-256 of correct solve steps (will publish tomorrow at this time)

If not, then you have narrowed down the

Quote

I'll wait between 20 and 28 hours before the outgoing TX will be pushed

comment you make to be more like 20-24 hours.

I dunno, lot of info and maybe I am missing some of it or not understanding it all correctly, but with the range, this is, worse case scenario, a less than a 10 minute solve.

I know you say you want to see how people will attack it differently...but I imagine most will overthink it.