Bitcoin puzzle transaction ~32 BTC prize to who solves it

[teguh54321]

Anyone try find checksum 3 digit prefix instead of adress prefix ?

Any tool that can do that ? 😅

1PWo3JeB9j5asAZX7457hXNUypugyosSfw
f6f5431d25bbe51d5f7633c702ba2608f3163704
Checksum (Hex): 89c9a9c6
Checksum (Decimal): 2311694790
----------------------------------------
1PWo3JeB9j5nh1sKHaudeo82T4GLTXWdyf
f6f5431d25bbe533119c98ad7904b81121ad9631
Checksum (Hex): e135cdce
Checksum (Decimal): 3778399694
----------------------------------------
1PWo3JeB9j6YptaZDx6UaNsmgZRuakjrum
f6f5431d25bbe5840bfb07f2aad41820879502ce
Checksum (Hex): b0793cb8
Checksum (Decimal): 2960735416
----------------------------------------
1PWo3JeB9j6ffmBQZ4tTuWxaByxBvPKVbB
f6f5431d25bbe59099ee9b35fb4a89ac2576371a
Checksum (Hex): 3ef22ffe
Checksum (Decimal): 1056059390
----------------------------------------
1PWo3JeB9jA5WGsbKBo1fsbvZawV81YKgG
f6f5431d25bbe6fb94ccecf0e58b2c8c632e952b
Checksum (Hex): 9d3e02a5
Checksum (Decimal): 2638086821
----------------------------------------
1PWo3JeB9jCVcGHZ8A8RtvvRAuzRYjJ8XM
f6f5431d25bbe7fca2acb33a3eebe9d58992d4c3
Checksum (Hex): bb4fc504
Checksum (Decimal): 3142567172
----------------------------------------
1PWo3JeB9jEJ4Z6LC6f9cKooNViuukaCyG
f6f5431d25bbe8bc47e76e1558ebb52a99986d3d
Checksum (Hex): cd162c23
Checksum (Decimal): 3440782371
----------------------------------------
1PWo3JeB9jEzsR5sR3HcUvfDNP7eQ1cZqv
f6f5431d25bbe9072738674df75ad60e8e6c1e99
Checksum (Hex): eb11a2ad
Checksum (Decimal): 3943801517
----------------------------------------
1PWo3JeB9jFYt1sLaz7QVUpZVHSt1nhP7r
f6f5431d25bbe941e25510cae40bc9c531d13a76
Checksum (Hex): 4fcf19f5
Checksum (Decimal): 1338972661
----------------------------------------
1PWo3JeB9jGBe6DNEAoAmEm12s5qmwhaCj
f6f5431d25bbe985544c01b3b23258960ba70315
Checksum (Hex): bbc8b56c
Checksum (Decimal): 3150493036
----------------------------------------
1PWo3JeB9jH8F1Mor4PbvcqoVwL6DZMp9v
f6f5431d25bbe9e9829ca059af52a2e3d73951b4
Checksum (Hex): 972d9901
Checksum (Decimal): 2536347905
----------------------------------------

Yes i mean not the adress. But matching checksum 3 digit hex  😅🙏

Just another idea , i dont know what will the result....

[Easteregg69]

Try on chat GPT?

You have to know what the question is. Or you get a 42.

[Virtuose]

Good to know:

50,000 BTC now in MARA’s treasury.

Fueled by 57+ EH/s of computational power, reinforcing new foundations for our nation’s digital economy and energy infrastructure.

This is MARA for America in action.

Next target: 75 EH/s by year-end.

https://x.com/MARA/status/1940799202159992835?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1940799202159992835%7Ctwgr%5E54fbd793bdd73c112e5f289ee31ea46a1c9c4f9c%7Ctwcon%5Es1_c10&ref_url=https%3A%2F%2Finvestx.fr%2Factu-crypto%2Fdoge-explose-52-analyse-dogecoin-baleine%2F

[Easteregg69]

I bought a new computer with a bigger screen. things look better now I get all the menu's.

Cheers!

Noted. The banks is still limited on page size. Fixed center. Could learn something from the exchanges. You be scrooling sideways no matter the resolution. 900px.. Fixed!

[stwenhao]

Its easyer to find a Bitcoin Block  than finding the key here.

Well, you can always try to solve some easier puzzle, which requires less grinding, at least for now: https://mempool.space/tx/aba3c2ae442aa20150996ee68f9aa4da83b57a4312891078be0c2e68c50b2801

For example, this address: https://mempool.space/address/bc1qzsjnew5qcn75e4cqdsc6r9v8fjy5ensancqmv2l2n82p0q5f5tlsfu3slz

You need to check only 256 transaction hashes on average, to solve it.

Proof of being spendable in testnet4: https://mempool.space/testnet4/address/tb1qzsjnew5qcn75e4cqdsc6r9v8fjy5ensancqmv2l2n82p0q5f5tls758l9d

Of course, rewards from my puzzle are smaller, because I am not that wealthy. But they are also easier to get, at least at the beginning, when nobody is trying to do that yet.

[Easteregg69]

So it's part of a giveaway or is it a hack job?

Just wondering. Cheers.

It's like thinking about when money don't belongs to anyone. I get some more beers!

[stwenhao]

So it's part of a giveaway or is it a hack job?

It's a giveaway, but it's a different puzzle, than finding N-bit private keys. Coin with "60" in amount is not based on 60-bit key. Instead, everything is based on the size of the signature. The private key is always equal to one. If you use half of the generator, you can easily get a signature, which would take exactly 60 bytes. By mining it, you can make it 59 bytes, then 58 bytes, and so on, and so forth, until you will get the smallest, 9-byte signature, which would end the puzzle, if someone will ever reach it.

Also, I don't know the solution to most coins in my puzzle. Coins are locked just on Proof of Work, measured in the size of the signature. The smaller it gets, the harder it is to mine it. But as long as nobody is trying, it can be done on just a CPU. It will be harder, if more people will start grinding it.

I get some more beers!

Good luck. I expect coins with amounts containing 60, 59, 58, 57, and maybe 56, can be done on CPU quite easily. But later, it gets harder and harder, 256x harder with each next key, because each next signature has to be smaller by one byte.

Satoshi in 2009 mined the Genesis Block with 40-bit leading zeroes, so I guess the first five puzzles are as hard to get, as re-mining that block is. But then, it becomes harder, and GPUs are needed (and later ASICs).

[teguh54321]

Its easyer to find a Bitcoin Block  than finding the key here.

Well, you can always try to solve some easier puzzle, which requires less grinding, at least for now: https://mempool.space/tx/aba3c2ae442aa20150996ee68f9aa4da83b57a4312891078be0c2e68c50b2801

For example, this address: https://mempool.space/address/bc1qzsjnew5qcn75e4cqdsc6r9v8fjy5ensancqmv2l2n82p0q5f5tlsfu3slz

You need to check only 256 transaction hashes on average, to solve it.

Proof of being spendable in testnet4: https://mempool.space/testnet4/address/tb1qzsjnew5qcn75e4cqdsc6r9v8fjy5ensancqmv2l2n82p0q5f5tls758l9d

Of course, rewards from my puzzle are smaller, because I am not that wealthy. But they are also easier to get, at least at the beginning, when nobody is trying to do that yet.

Please ellaborate 🤔

[Silentsinner]

P71..  1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU

found 1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH

Does anyone have any idea how far apart the two might be (64bit?)

63f651bb9c47645cd6  1PWo3JeB9jdv1SaFoJK7SynTq94JFdbagU +64bit
649a3dd0486c96e70b 1PWo3JeB9jdvp56gzG8navJjUMFQxxb997

Hello, I'd prefer to discuss this matter privately. You can open your inbox and write to me if you'd like.
I'm giving you a little hint.
It's either very close or very far away.
The probability of it being very close is between 5-7%.
Example
40 bit - 5-7%
44 bit - 8-10%
48 bit - 6-9%.... If you'd like to discuss it in detail, you can send me a message.

1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH
Hex code start: 60% 5xxx - 30% 7xxx

Hello bibilgin I can't write you a private message

How do you explain to me that the key should start with 60% 5xxx

[teguh54321]

Do anyone here believe the whole puzzle use the same seed ?
Is there posibility that that same seed lead to some similar statistical behaviour among them ?
Just asking , mybe somone deeply observe it ? 😅🙏

[stwenhao]

Please ellaborate 🤔

I think I gave enough clues in many different places, by looking at my history, you can find many detailed explanations. Also, you can look at example transactions, where I moved some coins in testnet4: https://mempool.space/testnet4/tx/8397c2323e3fa099c15be68399346b2b3d223ef8e81e553242763e1a4c60771a

You can analyze it step-by-step, try to validate that transaction from scratch, see, how things are hashed, and then, you should know, how to get my coins, by using Proof of Work.

Now, you can see similar addresses on mainnet: https://mempool.space/tx/aba3c2ae442aa20150996ee68f9aa4da83b57a4312891078be0c2e68c50b2801

If you produce ECDSA signature below N bytes, then you can get some BTCs directly from the puzzle (or testnet4 BTCs, if you want; I advertized it in my signature long enough, and posted about it in many different topics).

In general, when it comes to puzzles, then you don't have to start with the most difficult ones, if you don't know, how to sweep some easier ones. It should be step-by-step journey, like through the staircase.

[QG623]

puzzle #50

[hoanghuy2912]

Do anyone here believe the whole puzzle use the same seed ?
Is there posibility that that same seed lead to some similar statistical behaviour among them ?
Just asking , mybe somone deeply observe it ? 😅🙏

https://ibb.co/DDQtZnwf
like this

[QG623]

💡 Theory about the Deterministic Key in the Bitcoin Puzzles
The creator said:

"Just consecutive keys from a deterministic wallet (masked... to set difficulty)"

So they generated private keys using a simple k = k + 1 scheme.

➡️ If we find the starting key, we can rebuild the entire sequence, and recover all the puzzle private keys → 🎯 Jackpot.

But here's the issue:

Puzzle 1 uses key 1

The previous key would be 0

But private key 0 is invalid in Bitcoin (1 ≤ k < n)

👉 That means key 1 is either the true first key, or just the first accepted one after filtering.
Either way, finding the original key would let us regenerate the whole series.

[Cricktor]

So they generated private keys using a simple k = k + 1 scheme.

You don't understand how key derivation in BIP32 works and your foolish assumptions that puzzle keys have any dependency from one to another is deeply flawed.

Even though key derivation in deterministic wallets is deterministic, it doesn't mean that you can calculate a sequential key solely from knowledge of its predecessor or successor (or any other key).

In a deterministic wallet all keys appear as if they're random. Period! There is no exploitable relation between individual keys, unless you leak a private key and the xpub, but that's another story and stupid user error. Masking them down to a certain bitlength doesn't introduce any new relation.

But you can happily continue to read tea leaves...


Post edit: you can compromise a HD wallet when you leak a private key and the xpub. This doesn't really matter here, as the xpub of this puzzle is not leaked to my knowledge. We also can't verify if saatoshi_rising said the truth or not regarding the origin of the private keys. It won't make sense to me if they lied.

[teguh54321]

Do anyone here believe the whole puzzle use the same seed ?
Is there posibility that that same seed lead to some similar statistical behaviour among them ?
Just asking , mybe somone deeply observe it ? 😅🙏

like this

Image not available 😅🤔

So they generated private keys using a simple k = k + 1 scheme.

You don't understand how key derivation in BIP32 works and your foolish assumptions that puzzle keys have any dependency from one to another is deeply flawed.

Even though key derivation in deterministic wallets is deterministic, it doesn't mean that you can calculate a sequential key solely from knowledge of its predecessor or successor (or any other key).

In a deterministic wallet all keys appear as if they're random. Period! There is no exploitable relation between individual keys. Masking them down to a certain bitlength doesn't introduce any new relation.

But you can happily continue to read tea leaves...

I dont say any direct connection or dependency between them.
I mean some kind of statistical prefix frequency similiarity among huge keyspace around them maybe 😅. I just persue to look it deeper. As i scan lots of statistical bias in several prefix count / frequency in dissected private key keyspace result

[bibilgin]

Hello bibilgin I can't write you a private message

How do you explain to me that the key should start with 60% 5xxx

In the Profile section at the top, go to "Personal Message Options" in the left menu. Check the "Allow newbies to send you PMs." You'll be notified afterward. I can send you a private message.

[hoanghuy2912]

Do anyone here believe the whole puzzle use the same seed ?
Is there posibility that that same seed lead to some similar statistical behaviour among them ?
Just asking , mybe somone deeply observe it ? 😅🙏

https://ibb.co/DDQtZnwf
like this

Image not available 😅🤔

So they generated private keys using a simple k = k + 1 scheme.

You don't understand how key derivation in BIP32 works and your foolish assumptions that puzzle keys have any dependency from one to another is deeply flawed.

Even though key derivation in deterministic wallets is deterministic, it doesn't mean that you can calculate a sequential key solely from knowledge of its predecessor or successor (or any other key).

In a deterministic wallet all keys appear as if they're random. Period! There is no exploitable relation between individual keys. Masking them down to a certain bitlength doesn't introduce any new relation.

But you can happily continue to read tea leaves...

I dont say any direct connection or dependency between them.
I mean some kind of statistical prefix frequency similiarity among huge keyspace around them maybe 😅. I just persue to look it deeper. As i scan lots of statistical bias in several prefix count / frequency in dissected private key keyspace result

Click on the link to see the photo

[Geshma]

do you have code simulating the checksum prefix

[teguh54321]

Do anyone here believe the whole puzzle use the same seed ?
Is there posibility that that same seed lead to some similar statistical behaviour among them ?
Just asking , mybe somone deeply observe it ? 😅🙏

like this

Image not available 😅🤔

So they generated private keys using a simple k = k + 1 scheme.

You don't understand how key derivation in BIP32 works and your foolish assumptions that puzzle keys have any dependency from one to another is deeply flawed.

Even though key derivation in deterministic wallets is deterministic, it doesn't mean that you can calculate a sequential key solely from knowledge of its predecessor or successor (or any other key).

In a deterministic wallet all keys appear as if they're random. Period! There is no exploitable relation between individual keys. Masking them down to a certain bitlength doesn't introduce any new relation.

But you can happily continue to read tea leaves...

I dont say any direct connection or dependency between them.
I mean some kind of statistical prefix frequency similiarity among huge keyspace around them maybe 😅. I just persue to look it deeper. As i scan lots of statistical bias in several prefix count / frequency in dissected private key keyspace result

Click on the link to see the photo

Image not found. Can you re upload ?