Bitcoin puzzle transaction ~32 BTC prize to who solves it

[Marcel.]

  priv2addr.py 2832ed74f2b5e35ee
  Uncompressed Bitcoin Address: 138XxHZGcKM6WyWuYCijLsoCd8K3x4WYjs

     Compressed Bitcoin Address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

    Uncompressed P2SH Address: 3GsgtYu5N1zZUAvtwwnN1sf9tf7shrJrex

       Compressed P2SH Address: 3LPuXLDK7AGtmHLv5x1Aj7jSzKmD2Dj4Zr

 Uncompressed Bech32 Address: bc1qzawsqu2pgrm7tglggkywujgfgefa56nwnlj6z3

    Compressed Bech32 Address: bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn <-------

looks like someone done some transaction tests a day before moving the balance from 66..

[Woz2000]

Totally agree with you Alberto.

Nobody can prove anything. But some statements are much more stupid and illogical than others.

Hello everyone! I found the key to puzzle 66, but now I have another problem: how to withdraw the funds so that no one can intercept them with a bot?

Clown music here

Do you really think that someone wealthy enough, who can afford not to touch the prize money from 120 and 125 bits, would bother solving the puzzle at all, let alone succeed twice?! It's nonsense to think otherwise in this case.

There is a lot of bitcoin holders that are just waiting to see their holdings increase the value..

showing an address is not evidence of anything.

I can't prove the the puzzle creator not move that balance.
You can't prova the puzzle creator move it...

anything that we write here is pure speculation, is just an opinion of what you or me personally believe.

[Kpot87]

I'm personally not affected by #66 being solved because even though I've been at it for a year or so, I looked through all my theories, all my notes, all my scripts, and not one of them were even close to the solved keyspace/binary/hex/decimal.

I was not so far from this puzzle? around +- 1000000 years ))))in truth i was hear
Pub Addr: 13zb1hQbWVsGTfNXwP3Wtk7rqq3vA6vvfa
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZdhJgPUu3yfb2fwVhmH
Priv (HEX): 0x00000000000000000000000000000000000000000000000270733ED8D4660295

[COBRAS]

  priv2addr.py 2832ed74f2b5e35ee
  Uncompressed Bitcoin Address: 138XxHZGcKM6WyWuYCijLsoCd8K3x4WYjs

     Compressed Bitcoin Address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

    Uncompressed P2SH Address: 3GsgtYu5N1zZUAvtwwnN1sf9tf7shrJrex

       Compressed P2SH Address: 3LPuXLDK7AGtmHLv5x1Aj7jSzKmD2Dj4Zr

 Uncompressed Bech32 Address: bc1qzawsqu2pgrm7tglggkywujgfgefa56nwnlj6z3

    Compressed Bech32 Address: bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn <-------

looks like someone done some transaction tests a day before moving the balance from 66..

you lost now yoir win of next puzzle, if this throe

  priv2addr.py 2832ed74f2b5e35ee
  Uncompressed Bitcoin Address: 138XxHZGcKM6WyWuYCijLsoCd8K3x4WYjs

     Compressed Bitcoin Address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

    Uncompressed P2SH Address: 3GsgtYu5N1zZUAvtwwnN1sf9tf7shrJrex

       Compressed P2SH Address: 3LPuXLDK7AGtmHLv5x1Aj7jSzKmD2Dj4Zr

 Uncompressed Bech32 Address: bc1qzawsqu2pgrm7tglggkywujgfgefa56nwnlj6z3

    Compressed Bech32 Address: bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn <-------

looks like someone done some transaction tests a day before moving the balance from 66..

bro, check pls other puzzles  ? )))

[saeedxxx]

  priv2addr.py 2832ed74f2b5e35ee
  Uncompressed Bitcoin Address: 138XxHZGcKM6WyWuYCijLsoCd8K3x4WYjs

     Compressed Bitcoin Address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

    Uncompressed P2SH Address: 3GsgtYu5N1zZUAvtwwnN1sf9tf7shrJrex

       Compressed P2SH Address: 3LPuXLDK7AGtmHLv5x1Aj7jSzKmD2Dj4Zr

 Uncompressed Bech32 Address: bc1qzawsqu2pgrm7tglggkywujgfgefa56nwnlj6z3

    Compressed Bech32 Address: bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn <-------

looks like someone done some transaction tests a day before moving the balance from 66..

Does it mean that it is solved one year ago?!

[COBRAS]

  priv2addr.py 2832ed74f2b5e35ee
  Uncompressed Bitcoin Address: 138XxHZGcKM6WyWuYCijLsoCd8K3x4WYjs

     Compressed Bitcoin Address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

    Uncompressed P2SH Address: 3GsgtYu5N1zZUAvtwwnN1sf9tf7shrJrex

       Compressed P2SH Address: 3LPuXLDK7AGtmHLv5x1Aj7jSzKmD2Dj4Zr

 Uncompressed Bech32 Address: bc1qzawsqu2pgrm7tglggkywujgfgefa56nwnlj6z3

    Compressed Bech32 Address: bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn <-------

looks like someone done some transaction tests a day before moving the balance from 66..

Does it mean that it is solved one year ago?!

pubkeys was at privkeysite in 2023:

 

wonder about privatekeys website

when i check for any addresss , i get the same addresses from different networks bitcoin gold , bitcoin cash ,,,etc
that has the same private key Huh?

and i wonder how is that possible without knowing the private key from the beginning ??

lets say for puzzle 66
13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

Addresses with the same Private Key :

Bitcoin:
bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn
 0  0  0
Bitcoin Testnet:
miWYJkVaKXJroYbBB8kkrBHEecy5dxNKJP
 0.15650667  0.15650667  15
tb1qyr2956nky56hqr8fuzepdccejse4mw99lel6sq
 0.07957129  0.07957129  15
Bitcoin Cash:
qqsdgkn2wcjn2uqva8sty9hrrx2rxhdc55qw0jqhdh
 0.69
Bitcoin SV:
13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so
Bitcoin Gold:
GLqWRpjYVMUu6uQrPWSVT2QohoADou8QwG
 0.66  0.66  2
btg1qyr2956nky56hqr8fuzepdccejse4mw99rkzv7m
Litecoin:
LNDYGuiRbA7fHEoidhmgJH8fzqjeseATsU
 0  0  0
ltc1qyr2956nky56hqr8fuzepdccejse4mw993r7dnr
 0  0  0
Dogecoin:
D88gYxMEoumtZSJAC9mwa2EWfm6g3uocon
 25.60472599  25.60472599  9
Dash:
XdgRqx4VUD6CBNi9KT6bsnkhcxx4pyNnFr
 0  0  0
Zcash:
t1LsC22pjUpfCd5ATPzbWA5Aq3HZTZXJWuS
Clams:
xBJDuaF4nDMe4pDRp3R3TSMh1jfcBnESxx
 0  0  0

[digitalbear]

pubkeys was at privkeysite in 2023:

 

Really? what website? can you give a link please? Thank you

[COBRAS]

pubkeys was at privkeysite in 2023:

 

Really? what website? can you give a link please? Thank you

find tb1qyr2956nky56hqr8fuzepdccejse4mw99lel6sq on this phorum

[Woz2000]

Check again, the timestamps show the bc1 outgoing transaction was ~41 minutes AFTER the 5.9btc outgoing

  priv2addr.py 2832ed74f2b5e35ee
  Uncompressed Bitcoin Address: 138XxHZGcKM6WyWuYCijLsoCd8K3x4WYjs

     Compressed Bitcoin Address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

    Uncompressed P2SH Address: 3GsgtYu5N1zZUAvtwwnN1sf9tf7shrJrex

       Compressed P2SH Address: 3LPuXLDK7AGtmHLv5x1Aj7jSzKmD2Dj4Zr

 Uncompressed Bech32 Address: bc1qzawsqu2pgrm7tglggkywujgfgefa56nwnlj6z3

    Compressed Bech32 Address: bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn <-------

looks like someone done some transaction tests a day before moving the balance from 66..

[albert0bsd]

pubkeys was at privkeysite in 2023:

 

You don't need the public key to calculate those address... They are some other hash made from the original rmd160 hash

Check again, the timestamps show the bc1 outgoing transaction was ~41 minutes AFTER the 5.9btc outgoing

it was an user on some telegram group:

[benjaniah]

  priv2addr.py 2832ed74f2b5e35ee
  Uncompressed Bitcoin Address: 138XxHZGcKM6WyWuYCijLsoCd8K3x4WYjs

     Compressed Bitcoin Address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

    Uncompressed P2SH Address: 3GsgtYu5N1zZUAvtwwnN1sf9tf7shrJrex

       Compressed P2SH Address: 3LPuXLDK7AGtmHLv5x1Aj7jSzKmD2Dj4Zr

 Uncompressed Bech32 Address: bc1qzawsqu2pgrm7tglggkywujgfgefa56nwnlj6z3

    Compressed Bech32 Address: bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn <-------

looks like someone done some transaction tests a day before moving the balance from 66..

https://talkimg.com/images/2024/09/21/gzrwW.jpeg

Hm, so someone sent 6001 satoshis to 'bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn' almost a year ago (Sept 18 2023)? I think it's safe to say, that whoever sent that 6001 satoshis knew 66's private key. What do you all think?

Edit: No, someone just took 66's wallet address and converted it to bech32, and sent 6001 sats there a year ago, and about 45mins after 66 was solved someone picked up those sats. Thanks Alberto for clarifying.

[AlanJohnson]

  priv2addr.py 2832ed74f2b5e35ee
  Uncompressed Bitcoin Address: 138XxHZGcKM6WyWuYCijLsoCd8K3x4WYjs

     Compressed Bitcoin Address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

    Uncompressed P2SH Address: 3GsgtYu5N1zZUAvtwwnN1sf9tf7shrJrex

       Compressed P2SH Address: 3LPuXLDK7AGtmHLv5x1Aj7jSzKmD2Dj4Zr

 Uncompressed Bech32 Address: bc1qzawsqu2pgrm7tglggkywujgfgefa56nwnlj6z3

    Compressed Bech32 Address: bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn <-------

looks like someone done some transaction tests a day before moving the balance from 66..

Hm, so someone sent 6001 satoshis to 'bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn' almost a year ago (Sept 18 2023)? I think it's safe to say, that whoever sent that 6001 satoshis knew 66's private key. What do you all think?

Something very fishy is going on here ... 

[hpsk]

  priv2addr.py 2832ed74f2b5e35ee
  Uncompressed Bitcoin Address: 138XxHZGcKM6WyWuYCijLsoCd8K3x4WYjs

     Compressed Bitcoin Address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

    Uncompressed P2SH Address: 3GsgtYu5N1zZUAvtwwnN1sf9tf7shrJrex

       Compressed P2SH Address: 3LPuXLDK7AGtmHLv5x1Aj7jSzKmD2Dj4Zr

 Uncompressed Bech32 Address: bc1qzawsqu2pgrm7tglggkywujgfgefa56nwnlj6z3

    Compressed Bech32 Address: bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn <-------

looks like someone done some transaction tests a day before moving the balance from 66..

https://talkimg.com/images/2024/09/21/gzrwW.jpeg

Hm, so someone sent 6001 satoshis to 'bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn' almost a year ago (Sept 18 2023)? I think it's safe to say, that whoever sent that 6001 satoshis knew 66's private key. What do you all think?

Something very fishy is going on here ... 

Sending a transaction doesn't require knowledge of the private key. Anyone can initiate one, so it doesn't provide any meaningful information. I'm not sure what you're trying to get at with your suspicions.

[AlanJohnson]

  priv2addr.py 2832ed74f2b5e35ee
  Uncompressed Bitcoin Address: 138XxHZGcKM6WyWuYCijLsoCd8K3x4WYjs

     Compressed Bitcoin Address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

    Uncompressed P2SH Address: 3GsgtYu5N1zZUAvtwwnN1sf9tf7shrJrex

       Compressed P2SH Address: 3LPuXLDK7AGtmHLv5x1Aj7jSzKmD2Dj4Zr

 Uncompressed Bech32 Address: bc1qzawsqu2pgrm7tglggkywujgfgefa56nwnlj6z3

    Compressed Bech32 Address: bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn <-------

looks like someone done some transaction tests a day before moving the balance from 66..

Hm, so someone sent 6001 satoshis to 'bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn' almost a year ago (Sept 18 2023)? I think it's safe to say, that whoever sent that 6001 satoshis knew 66's private key. What do you all think?

Something very fishy is going on here ... 

Sending a transaction doesn't require knowledge of the private key. Anyone can initiate one, so it doesn't provide any meaningful information. I'm not sure what you're trying to get at with your suspicions.

That tx was confirmed on the blockchain... It is a proof that someone had private key to puzzle 66 year before it was officialy solved.

It's really strange.

[garlonicon]

It is a proof that someone had private key to puzzle 66 year before it was officialy solved.

No, it is not. If you have any address for some compressed public key, then you can safely convert P2PKH into P2WPKH, and it will be standard. For example:

Code:

P2PKH: 1111111111111111111114oLvT2
Script: 76a914000000000000000000000000000000000000000088ac

P2WPKH: bc1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq9e75rs
Script: 00140000000000000000000000000000000000000000

And if you know, that instead of those zeroes in the middle, you have other hex digits, then you can just copy-paste them, and change address type, as you wish. Of course, P2PKH works for both compressed and uncompressed keys, but P2WPKH are standard only for uncompressed ones.

[AlanJohnson]

It is a proof that someone had private key to puzzle 66 year before it was officialy solved.

No, it is not. If you have any address for some compressed public key, then you can safely convert P2PKH into P2WPKH, and it will be standard. For example:

Code:

P2PKH: 1111111111111111111114oLvT2
Script: 76a914000000000000000000000000000000000000000088ac

P2WPKH: bc1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq9e75rs
Script: 00140000000000000000000000000000000000000000

And if you know, that instead of those zeroes in the middle, you have other hex digits, then you can just copy-paste them, and change address type, as you wish. Of course, P2PKH works for both compressed and uncompressed keys, but P2WPKH are standard only for uncompressed ones.

What are you talking about ?!

To make a valid transaction you need a private key. Period.

The transaction we are talking about was made from bech32 address created from the same private key that puzzle 66 address containing funds. And it was created about a year ago from now.

[Kpot87]

It is a proof that someone had private key to puzzle 66 year before it was officialy solved.

No, it is not. If you have any address for some compressed public key, then you can safely convert P2PKH into P2WPKH, and it will be standard. For example:

Code:

P2PKH: 1111111111111111111114oLvT2
Script: 76a914000000000000000000000000000000000000000088ac

P2WPKH: bc1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq9e75rs
Script: 00140000000000000000000000000000000000000000

And if you know, that instead of those zeroes in the middle, you have other hex digits, then you can just copy-paste them, and change address type, as you wish. Of course, P2PKH works for both compressed and uncompressed keys, but P2WPKH are standard only for uncompressed ones.

What are you talking about ?!

To make a valid transaction you need a private key. Period.

The transaction we are talking about was made from bech32 address created from the same private key that puzzle 66 address containing funds. And it was created about a year ago from now.

where did you see outgoing transaction from priv key 66? It was income transaction but in other type of address!!!

[albert0bsd]

What are you talking about ?!

No, What are you talking about?

Actually what garlonicon said was correct

To make a valid transaction you need a private key. Period.

The transaction we are talking about was made from bech32 address created from the same private key that puzzle 66 address containing funds. And it was created about a year ago from now.

What transaction are you talking about?

To send some value to some destination address you don't need its private key, you only need the private key of the source address, not of thr destination one...

[AlanJohnson]

What are you talking about ?!

No, What are you talking about?

Actually what garlonicon said was correct

To make a valid transaction you need a private key. Period.

The transaction we are talking about was made from bech32 address created from the same private key that puzzle 66 address containing funds. And it was created about a year ago from now.

What transaction are you talking about?

To send some value to some destination address you don't need its private key, you only need the private key of the source address, not of thr destination one...

Public key of puzzle 66 is:  024ee2be2d4e9f92d2f5a4a03058617dc45befe22938feed5b7a6b7282dd74cbdd

Compressed bech32 address derived from that key is :  bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn

Now look into block explorer ... in 2023 there was a valid OUTGOING TRANSACTION from that address !!!

[albert0bsd]

Now look into block explorer ... in 2023 there was a valid OUTGOING TRANSACTION from that address !!!

It is not an Outgoing transaction. An outgoing transaction is when that address is used as INPUT.

In the TX that you are mention:

Code:

b0780488cab40d45567a1eac97c2a456b48b216af3e6ecf47f1e5948a07e8c49

The address is bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn is listed as OUTPUT in the 2023 TX.




In the 2024 TX it was an INPUT.... Please learn something before talk

Compressed bech32 address derived from that key is :  bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn

No the address was derived from the Legacy address

Code:

P2PKH: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so
Hash: 20d45a6a762535700ce9e0b216e31994335db8a5

P2WPKH: bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn
Hash: 001420d45a6a762535700ce9e0b216e31994335db8a5

As you see you only need the RMD160 hash of it 20d45a6a762535700ce9e0b216e31994335db8a5 just apend two bytes 0x00 and 0x14 before the original hash see? No public key was needed for that