Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 60.

Tepan

jr. member

Activity: 79

Merit: 1

PROOF #1 RANGE 95

1237940039285380274899124223 -- upper ranges key

868012190417726402719548863 <- actual priv key Huh

848970019642690143254478847 -> scaled for sequence start Shocked

PROOF # 2 RANGE 100

1267650600228229401496703205375 -- upper ranges key

868221233689326498340379183142 <- actual priv key Huh

863825300114114781320059027455 -> scaled for sequence start Shocked

PROOF # 3 RANGE 105

40564819207303340847894502572031 -- upper ranges key

29083230144918045706788529192435 <- actual priv key Huh

25282409603651667990095585083391 -> scaled for sequence start Shocked

this decimal from priv key was used for learn to scaled down the ranges, and i'll make some precision to these math.
sorry if i'm not provide the formula to this.

Just still same, if doin search with CPU, it takes whole time to hit the correct privkey.

mcdouglasx

member

Activity: 239

Merit: 53

New ideas will be criticized and then admired.

I have posted a new idea for searching for pubkeys, I hope it can be of some use to you, greetings.

https://bitcointalksearch.org/topic/ultra-lightweight-database-with-public-keys-for-puzzle-btc-5509916

GR Sasa

member

Activity: 194

Merit: 14

I am assuming, that the creator of the puzzle is very very aware of what is going on here and is between us. I also assume, that puzzle 66 was not solved by anyone, but rather the creator himself did reveal it's private key after it's probably was taken by bots, to see test if bots are actually a threat for solved low-bits puzzles.

So i will not be surprised if we see puzzle 67 also out of no where gets it's private key revealed after sometime by the creator, sooner or later.

Mark my words.

digitalbear

newbie

Activity: 11

Merit: 0

Quote from: GTX1060x2 on September 21, 2024, 10:18:35 AM

Quote from: Baskentliia on September 21, 2024, 09:56:50 AM

Can you share the address of puzzle 67 that starts with bc and 3. I don't know how to find it. Someone previously shared the address for puzzle 66 that starts with bc and 3. Can you share it for puzzle 67 too?

bc1qww2r0wea6mges0nxv2w97zx8pef8dym3x2g8t3
__https://i.imgur.com/reTwOd9.png

For puzzle 67 on website we can see the same address:

Code:

Bitcoin:
W bc1qww2r0wea6mges0nxv2w97zx8pef8dym3x2g8t3
0  0  0

but how can we find the other addresses that have the same private key for bitcoin like we have for puzzle 66 without having the private key?

Code:

Bitcoin:
U 138XxHZGcKM6WyWuYCijLsoCd8K3x4WYjs
0  0  0
S 3PdQoXyQwWmerpt3SbF7Hbh3aukC5w28GP
0  0.00046714  4
W bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn
0  0.00006001  2
T bc1pgchl8k5hhxnlcfd3tmxp8vfk9jks438msjkth5lg93fzmskwy6js0kuqd2
0  0  0

GTX1060x2

newbie

Activity: 9

Merit: 3

Quote from: Baskentliia on September 21, 2024, 09:56:50 AM

Can you share the address of puzzle 67 that starts with bc and 3. I don't know how to find it. Someone previously shared the address for puzzle 66 that starts with bc and 3. Can you share it for puzzle 67 too?

bc1qww2r0wea6mges0nxv2w97zx8pef8dym3x2g8t3
__https://i.imgur.com/reTwOd9.png

Easteregg69

sr. member

Activity: 1579

Merit: 267

You take it to a level where I can't keep up. I be humble. And rich. Stacking sats.

It's a good excuse for not being doing the dishes. I see that now.

Check my status. I merited the most GPU intensive. (Mining rig rentals) I paid for blowing top of the hashrate. Beginners stuff.

Tell Poul we don't die when he gets to that part.

On this one you have to use the thinker. Be the gas man. You have the problem. Find the solution. Root boy in control. In comes the 2 to the three and the one.

Baskentliia

jr. member

Activity: 65

Merit: 1

34Sf4DnMt3z6XKKoWmZRw2nGyfGkDgNJZZ

Can you share the address of puzzle 67 that starts with bc and 3. I don't know how to find it. Someone previously shared the address for puzzle 66 that starts with bc and 3. Can you share it for puzzle 67 too?

kTimesG

member

Activity: 165

Merit: 26

It makes my day every time an intended troll post or unintended wrong statement results in some flame war Grin

AlanJohnson

member

Activity: 122

Merit: 11

Quote from: albert0bsd on September 21, 2024, 07:05:41 AM

Quote from: AlanJohnson on September 21, 2024, 06:51:33 AM

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

Quote from: AlanJohnson on September 21, 2024, 06:51:33 AM

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

OK. I admit i was wrong.

Now i see it was INCOMING tx TO that address. My bad.

albert0bsd

hero member

Activity: 862

Merit: 662

Quote from: AlanJohnson on September 21, 2024, 06:51:33 AM

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

Quote from: AlanJohnson on September 21, 2024, 06:51:33 AM

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

AlanJohnson

member

Activity: 122

Merit: 11

Quote from: albert0bsd on September 21, 2024, 06:40:26 AM

Quote from: AlanJohnson on September 21, 2024, 06:05:34 AM

What are you talking about ?!

No, What are you talking about?

Actually what garlonicon said was correct

Quote from: AlanJohnson on September 21, 2024, 06:05:34 AM

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

hero member

Activity: 862

Merit: 662

Quote from: AlanJohnson on September 21, 2024, 06:05:34 AM

What are you talking about ?!

No, What are you talking about?

Actually what garlonicon said was correct

Quote from: AlanJohnson on September 21, 2024, 06:05:34 AM

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...

Kpot87

jr. member

Activity: 43

Merit: 1

Quote from: AlanJohnson on September 21, 2024, 06:05:34 AM

Quote from: garlonicon on September 21, 2024, 05:45:38 AM

Quote

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? Huh

It was income transaction but in other type of address!!!

AlanJohnson

member

Activity: 122

Merit: 11

Quote from: garlonicon on September 21, 2024, 05:45:38 AM

Quote

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.

garlonicon

copper member

Activity: 944

Merit: 2257

Quote

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

member

Activity: 122

Merit: 11

Quote from: hpsk on September 21, 2024, 05:06:06 AM

Quote from: AlanJohnson on September 21, 2024, 02:14:26 AM

Quote from: benjaniah on September 21, 2024, 01:53:24 AM

Quote from: Marcel. on September 20, 2024, 12: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..

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 ... Shocked

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.

hpsk

newbie

Activity: 5

Merit: 0

Quote from: AlanJohnson on September 21, 2024, 02:14:26 AM

Quote from: benjaniah on September 21, 2024, 01:53:24 AM

Quote from: Marcel. on September 20, 2024, 12: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..

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 ... Shocked

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

Activity: 122

Merit: 11

Quote from: benjaniah on September 21, 2024, 01:53:24 AM

Quote from: Marcel. on September 20, 2024, 12: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..

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 ... Shocked

benjaniah

newbie

Activity: 25

Merit: 3

Quote from: Marcel. on September 20, 2024, 12: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..

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.

albert0bsd

hero member

Activity: 862

Merit: 662

Quote from: COBRAS on September 20, 2024, 04:15:34 PM

pubkeys was at privkeysite in 2023:

Grin

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

Quote from: Woz2000 on September 20, 2024, 07:25:54 PM

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:

Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 60. (Read 245054 times)