Bitcoin puzzle transaction ~32 BTC prize to who solves it

[JavaSandcrawler]

Why not simply AES-256 encrypt the private key and be done with it in, like, 3 lines? No password hashing and so on.

I solved puzzle #66 but I'm very afraid to sweep it. Since no one claimed it yet, they definitely belong to me, right? Here's my proof: the encrypted private key is:

Code:

0x4074a46512e55c9559cb8af86c983bc424d9f2d5fbb3c14b65b1045d21972d219b359a24806826a94c72e9a95ca00dab

First 16 bytes are the IV, then 32 bytes of private key. I removed the padding, since it's 16 bytes of 0x10 (e.g. no bytes in last block).

If anyone steals my prize I will divulge the decryption key.

Or, simply hash it once together with some secret value, you only need to prove you knew the hashed value before anyone else, not to protect the actual data.

Code:

SHA256(privateKey + "some secret value")

Provide decryption keys, you sayd that you solved 66.
-----------
I started looking for the most interesting thing in this 2832 range. it took ~6-8 hours to find
[spoilerhttps://ibb.co/fVgVG72[/spoiler]

Also note that logarithm decimal = 19.666 lol

I suggest that everyone who said that they decided to 66 should be banned, there were quite a few of them.

[kTimesG]

I solved puzzle #66 but I'm very afraid to sweep it. Since no one claimed it yet, they definitely belong to me, right? Here's my proof: the encrypted private key is:

Code:

0x4074a46512e55c9559cb8af86c983bc424d9f2d5fbb3c14b65b1045d21972d219b359a24806826a94c72e9a95ca00dab

First 16 bytes are the IV, then 32 bytes of private key. I removed the padding, since it's 16 bytes of 0x10 (e.g. no bytes in last block).

If anyone steals my prize I will divulge the decryption key.

Or, simply hash it once together with some secret value, you only need to prove you knew the hashed value before anyone else, not to protect the actual data.

Code:

SHA256(privateKey + "some secret value")

Provide decryption keys, you sayd that you solved 66.

I suggest that everyone who said that they decided to 66 should be banned, there were quite a few of them.

It's funny that you didn't see anything wrong there I missed the part that we also need 16 bytes for the encrypted padding block, or else we can put whatever we want in it.

And the other problem is that you don't even need some powerful GPU to solve the 66 priv key once pub is known. Most of the work can be done in advance.

[otterosch]

Heyho, I couldn't find any Info on this. I'm using VanitySearch and it says [compressed] next to the address - is this right? Are the addresses compressed or not?

Ty guys!

[gygy]

Heyho, I couldn't find any Info on this. I'm using VanitySearch and it says [compressed] next to the address - is this right? Are the addresses compressed or not?

Ty guys!

They are compressed.

[kTimesG]

Seems there are 12 satoshi left to grab on the #66 address. Hurry up guys.

TX input:

Code:

1FuckUmT5yBAvozf6gT8GRQVbJ7iBDUnrH

TX outputs:

Code:

1Jvv4yWkE9MhbuwGU66666666669sugEF 0.00000001
1YouAreSoDumbLoL666666666667K5aR4 0.00000002
1WhatWereUThinking6666666662wkqq1 0.00000003
1YouDeserveNothing6666666665sbbBC 0.00000004
1YouEpicFaiLure66666666666688GSDA 0.00000005
1BitchAssLoser66666666666669dBUVg 0.00000006
1AndEveryoneELse666666666669Vnc8C 0.00000007
1ThisisALosingGame6666666667HAZdf 0.00000008
1JustGetAReaLJob666666666665vGKVD 0.00000009
1YoureWastingTimeAndMoney664CVExC 0.00000010
1AndCausingCLimateChange6666HK8Qc 0.00000011
13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so 0.00000012
1Jvv4yWkE9MhbuwGUoqFYzDjRVQHaLWuJd 0.00000013
1FK5PjPNARQmg94n2cNHTo9417kWfXUDBQ 0.00002125

[albert0bsd]

Seems there are 12 satoshi left to grab on the #66 address. Hurry up guys.

Do you send them?

well Looks that those will keep there for some time unless someone whats to waste some 600 to 2000 sats to get those 12 sat out there.

maybe in some hundred years when mining reward is 1 satoshi.

[kTimesG]

Seems there are 12 satoshi left to grab on the #66 address. Hurry up guys.

Do you send them?

well Looks that those will keep there for some time unless someone whats to waste some 600 to 2000 sats to get those 12 sat out there.

maybe in some hundred years when mining reward is 1 satoshi.

Nope, just had the address page open lost in my 50 or so tabs and noticed the latest input TX. My bot was also not running, after weeks of being up I just forgot to restart it... nothing to cry over anyway. I wouldn't wanna be in the solver's shoes though.

[ApePunk]

Seems there are 12 satoshi left to grab on the #66 address. Hurry up guys.

TX input:

Code:

1FuckUmT5yBAvozf6gT8GRQVbJ7iBDUnrH

TX outputs:

Code:

1Jvv4yWkE9MhbuwGU66666666669sugEF 0.00000001
1YouAreSoDumbLoL666666666667K5aR4 0.00000002
1WhatWereUThinking6666666662wkqq1 0.00000003
1YouDeserveNothing6666666665sbbBC 0.00000004
1YouEpicFaiLure66666666666688GSDA 0.00000005
1BitchAssLoser66666666666669dBUVg 0.00000006
1AndEveryoneELse666666666669Vnc8C 0.00000007
1ThisisALosingGame6666666667HAZdf 0.00000008
1JustGetAReaLJob666666666665vGKVD 0.00000009
1YoureWastingTimeAndMoney664CVExC 0.00000010
1AndCausingCLimateChange6666HK8Qc 0.00000011
13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so 0.00000012
1Jvv4yWkE9MhbuwGUoqFYzDjRVQHaLWuJd 0.00000013
1FK5PjPNARQmg94n2cNHTo9417kWfXUDBQ 0.00002125

Read each addresses look like word to finder.

[albert0bsd]

Read each addresses look like word to finder.

Yes they are mocking of the early solver and all of us.

[CY4NiDE]

Heyho, I couldn't find any Info on this. I'm using VanitySearch and it says [compressed] next to the address - is this right? Are the addresses compressed or not?

Ty guys!

How could you not find this information? It's literally in this same page, above your own post.

There are other 4, consecutive posts showing a huge list with every known COMPRESSED pubkey from this puzzle.

[masoudtanhha]

any idea for puzzel 67

[CY4NiDE]

any idea for puzzel 67

Yes.

Wait until someone solves it and then steal the coins with a bot.

[Kamoheapohea]

Read each addresses look like word to finder.

Yes they are mocking of the early solver and all of us.

What a pathetic message to send this way. Really big asshole vibes.
I hope the original creator (Greg Maxwell?) will remove all addresses < 110bit(?) from the puzzle via a private transaction.

[Feron]

66 was solved quickly, no one complains that they were stolen, so it looks like the person who solved 66 took his rightful reward and the bot didn't get anything

[albert0bsd]

66 was solved quickly, no one complains that they were stolen, so it looks like the person who solved 66 took his rightful reward and the bot didn't get anything

I don't think so, nobody will accept that public shame

[kTimesG]

any reason why solver make same transaction amount as creator of puzzle deposited and same two transaction

0.59400000 BTC= -5.94000000BTC , 0.06600000 BTC=-0.66126013 BTC
why same way just little difference due to fee?   SOLVER=CREATER ?

If I give you a 10 $ bill and you go to the store will you pay by giving out the bill, or do you magically transform that paper into 1 cent coins and pay using those? Doesn't sound like you know how BTC works fundamentally. Unspent outputs have a fixed amount attached, consuming same amount is by design...

[COBRAS]

any idea for puzzel 67

Yes.

Wait until someone solves it and then steal the coins with a bot.


Funny, but throw.

[opciga]

The person who created the puzzle is making fun of us

[COBRAS]

with the way the data is stored it does not require a complex decompression system (it is not a compression algorithm) it is a system designed exclusively for searching for public keys, therefore it is handled by the search script as if you put 10 public keys in a text file to give a basic example, as for how many public keys could it store until being affected by the size of the db, well, it will depend on the reading capacity in large files, however in a 1gb file you would have approximately 2,621,400,000,000 pubkeys, you need more gb without losing reading speed, we could adapt a bloom filter .. but this is only an initial version of an idea that can be improved over time.

Any form of processing that uses less input bits than the output bits (or viceversa) is a (de)compression algorithm. I can claim that we can use a single bit to cover 2**256 public keys. 1 = all keys tried, 0 = not all keys tried, but it's not really a public key database. So when you say you can store 100 M public keys using just 655360 bits (80 kB), maybe there's some fine print over that statement, since not even the most optimal possible data structure (some optimal tree of sorts that uses every bit as a node value, and you walk along the tree to read or return some string of bits) can't store 25.6 billion bits of information using only 700k bits. At least not without critical trade-offs like very lossy/wrong results, or extremely slow operations. What's the use-case?

What happens is that you take the idea to your own needs, and you get confused because you are looking for a use to something that you do not know how it is used, in the context of my scripts is that I give the data, now that the same DB does not work For Kangaroo or Bsgs maybe if not, but that does not destroy the main idea.

I think you need take official registered a USA or EU patent to you DB. This will be protect your Idea from stealing and maybe give some money. Then you have a patent, can try sell your method to google, microsft etc.

[madogss]

I think you need take official registered a USA or EU patent to you DB. This will be protect your Idea from stealing and maybe give some money. Then you have a patent, can try sell your method to google, microsft etc.

Agreed this DB will be especially useful for space and medicine with how far AI has come we could use mcdouglasx's db to store a detailed brain scan or a 3d map of a galaxy and train AI on the db so it could piece together the data and we could ask it questions about the data like does this scan have a blood clot or a misfiring neuron or map the most efficient trajectory to this planet and it could answer but instead of taking up petabytes or even exabytes of storage it would take a fraction of that. Of course right now your db is specifically for public keys but its the idea that matters if you could apply it to different areas that would be game changing.