Kelvin555
Jr. Member
Offline
Activity: 57
Merit: 1
|
 |
September 20, 2024, 08:10:49 AM |
|
- So far nobody complained his hard search was exploited by bots or someone taking a shortcut. Regardless of shame, if you hate the bots, you'd call'em out.
Maybe because the person who is supposed to complain is dead, we have seen some people complain in this thread how they have lost their jobs and families because they have dedicated all their time to this puzzle challenge, some have even spent a huge amount of money on this puzzle challenge and the only hope they are hanging on to is that they will find the private key.... when they finally find it and someone steals it from them and even mock them, what do you think will happen ? Someone playing with us. p53 - 09.04 p56 - 09.08 p62 - 09.08 p64 - 09.10 p66 - 09.12
p67 - 09.14.2026
This is why p66 transaction went through the mempool. It was automated and scheduled a long time ago.
This defeats the main reason the creator had in mind when he created the challenge in the beginning, how can he know that the community is able to crack 66bits range wallet in 3years time if he scheduled the withdrawal in 2 years time.
|
|
|
|
AlanJohnson
Member

Offline
Activity: 185
Merit: 11
|
 |
September 20, 2024, 12:24:07 PM |
|
3Emiwzxme7Mrj4d89uqohXNncnRM15YESs https://www.blockchain.com/explorer/addresses/BTC/3Emiwzxme7Mrj4d89uqohXNncnRM15YESsBecause, likely, he wanted to make the community work on the lower bits, but without the private key. Maybe the solution provided by Kangaroo answered all the questions related to the vulnerability when revealing the pubkey... The funds from those wallets were transferred by one person to a single address. 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. He also didn't even claim the Bitcoin Cash and others on that addresses... Very suspicious 
|
|
|
|
ronin445
Newbie
Offline
Activity: 27
Merit: 0
|
 |
September 20, 2024, 03:33:46 PM |
|
Even thats founder of the puzzle we cannot say anything.. Its attracting more people to join the bruteforce party.
|
|
|
|
albert0bsd
|
 |
September 20, 2024, 04:54:18 PM |
|
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.
|
|
|
|
Marcel.
Newbie
Offline
Activity: 7
Merit: 0
|
 |
September 20, 2024, 05:50:15 PM |
|
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
Jr. Member
Offline
Activity: 85
Merit: 2
|
 |
September 20, 2024, 06:09:34 PM |
|
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
Jr. Member
Offline
Activity: 43
Merit: 1
|
 |
September 20, 2024, 06:13:17 PM |
|
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
Member

Offline
Activity: 1114
Merit: 24
|
 |
September 20, 2024, 08:14:55 PM Last edit: September 21, 2024, 09:45:26 PM by Mr. Big |
|
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 ? )))
|
[
|
|
|
COBRAS
Member

Offline
Activity: 1114
Merit: 24
|
 |
September 20, 2024, 09:15:34 PM |
|
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
Newbie
Offline
Activity: 11
Merit: 0
|
 |
September 20, 2024, 09:56:37 PM |
|
pubkeys was at privkeysite in 2023:  Really? what website? can you give a link please? Thank you
|
|
|
|
COBRAS
Member

Offline
Activity: 1114
Merit: 24
|
 |
September 21, 2024, 12:02:24 AM |
|
pubkeys was at privkeysite in 2023:  Really? what website? can you give a link please? Thank you find tb1qyr2956nky56hqr8fuzepdccejse4mw99lel6sq on this phorum
|
[
|
|
|
Woz2000
Jr. Member
Offline
Activity: 85
Merit: 2
|
 |
September 21, 2024, 12:25:54 AM |
|
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
|
 |
September 21, 2024, 01:48:44 AM Last edit: September 21, 2024, 02:03:32 AM by 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
Jr. Member
Offline
Activity: 44
Merit: 3
|
 |
September 21, 2024, 06:53:24 AM Last edit: September 22, 2024, 06:52:40 AM by 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..   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
Member

Offline
Activity: 185
Merit: 11
|
 |
September 21, 2024, 07:14:26 AM |
|
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
Newbie
Offline
Activity: 5
Merit: 0
|
 |
September 21, 2024, 10:06:06 AM |
|
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.jpegHm, 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
Member

Offline
Activity: 185
Merit: 11
|
 |
September 21, 2024, 10:22:30 AM |
|
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
Copper Member
Legendary
Offline
Activity: 944
Merit: 2283
|
 |
September 21, 2024, 10:45:38 AM Merited by vapourminer (1) |
|
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: 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
Member

Offline
Activity: 185
Merit: 11
|
 |
September 21, 2024, 11:05:34 AM |
|
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: 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
Jr. Member
Offline
Activity: 43
Merit: 1
|
 |
September 21, 2024, 11:38:28 AM |
|
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: 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!!!
|
|
|
|
|