Bitcoin puzzle transaction ~32 BTC prize to who solves it

[natedawg469]

Nobody admitted the find, so private key is unknown.

The private key is 0x6abe1f9b67e114

Code:

Private key : 000000000000000000000000000000000000000000000000006abe1f9b67e114
Public key  : 85a30d8413af4f8f9e6312400f2d194fe14f02e719b24c3f83bf1fd233a8f963 eb400323654cec63999b56f4ba44e8b21ab92d9d697fabe4666df3678585669
 
PrKey WIF c.: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjidyYKE5NcJQZYvknA
Address c.  : db53d9bbd1f3a83b094eeca7dd970bd85b492fa2
Address c.  : 1LzhS3k3e9Ub8i2W1V8xQFdB8n2MYCHPCa

I am assuming that you found out the private key yourself? I mean how did you get this info?

[1714065613]

1714065613

[1714065613]

1714065613

[1714065613]

1714065613

[1714065613]

1714065613

[DiegoPatterson.9909]

Well damn I can't code so there goes that option,Everything else can be ignored if we compare to the ripemd160 hash. Its certainly possible to design an ASIC for this and it might even be profitable for someone to do so in the future.

[arulbero]

The private key is 0x6abe1f9b67e114

Code:

Private key : 000000000000000000000000000000000000000000000000006abe1f9b67e114
Public key  : 85a30d8413af4f8f9e6312400f2d194fe14f02e719b24c3f83bf1fd233a8f963 eb400323654cec63999b56f4ba44e8b21ab92d9d697fabe4666df3678585669
 
PrKey WIF c.: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjidyYKE5NcJQZYvknA
Address c.  : db53d9bbd1f3a83b094eeca7dd970bd85b492fa2
Address c.  : 1LzhS3k3e9Ub8i2W1V8xQFdB8n2MYCHPCa

I am assuming that you found out the private key yourself? I mean how did you get this info?

No, I didn't find the key. I just got this info from this transaction https://blockchain.info/it/tx/ecc8c09284a6f9e6d52cccf7f8f4aef1d0c4a33984375dea4cea70923066078d on blockchain that moved for the first time funds from that address.

[itod]

The private key is 0x6abe1f9b67e114

Code:

Private key : 000000000000000000000000000000000000000000000000006abe1f9b67e114
Public key  : 85a30d8413af4f8f9e6312400f2d194fe14f02e719b24c3f83bf1fd233a8f963 eb400323654cec63999b56f4ba44e8b21ab92d9d697fabe4666df3678585669
 
PrKey WIF c.: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjidyYKE5NcJQZYvknA
Address c.  : db53d9bbd1f3a83b094eeca7dd970bd85b492fa2
Address c.  : 1LzhS3k3e9Ub8i2W1V8xQFdB8n2MYCHPCa

I am assuming that you found out the private key yourself? I mean how did you get this info?

No, I didn't find the key. I just got this info from this transaction https://blockchain.info/it/tx/ecc8c09284a6f9e6d52cccf7f8f4aef1d0c4a33984375dea4cea70923066078d on blockchain that moved for the first time funds from that address.

You lost me here. You were asked about the private key, and you are saying you got it from transaction information?!? What am I missing here?

[arulbero]

No, I didn't find the key. I just got this info from this transaction https://blockchain.info/it/tx/ecc8c09284a6f9e6d52cccf7f8f4aef1d0c4a33984375dea4cea70923066078d on blockchain that moved for the first time funds from that address.

You lost me here. You were asked about the private key, and you are saying you got it from transaction information?!? What am I missing here?

From the transaction I got the public key related to the address 1LzhS3k3e9Ub8i2W1V8xQFdB8n2MYCHPCa.

You can get the private key from a public key only if you know already that the private key lies in a very limited range (in this case from 2^54 to 2^55)

[itod]

No, I didn't find the key. I just got this info from this transaction https://blockchain.info/it/tx/ecc8c09284a6f9e6d52cccf7f8f4aef1d0c4a33984375dea4cea70923066078d on blockchain that moved for the first time funds from that address.

You lost me here. You were asked about the private key, and you are saying you got it from transaction information?!? What am I missing here?

From the transaction I got the public key related to the address 1LzhS3k3e9Ub8i2W1V8xQFdB8n2MYCHPCa.

You can get the private key from a public key only if you know already that the private key lies in a very limited range (in this case from 2^54 to 2^55)

Can you please explain the method you were using to accomplish this magic? 2^55 - 2^54 = 1.8 x 10^16, that's a lot of private keys to check by brute-forcing them. What you are claiming doesn't make sense at all.

[arulbero]

Can you please explain the method you were using to accomplish this magic? 2^55 - 2^54 = 1.8 x 10^16, that's a lot of private keys to check by brute-forcing them. What you are claiming doesn't make sense at all.

Getting the private key from a public key is known as "the elliptic curve discrete logarithm problem".

There are several algorithms to solve this problem:

1) brute force attack  (roughly p steps, you mean this method)

2) Pollard Rho (roughly sqrt(p) steps, based on birthday paradox)

3) Baby Step - Giant Step ( roughly sqrt(p) steps if you have enough memory space to store sqrt(p) points)

(p = number of points = number of private keys )



Take a look at:

http://andrea.corbellini.name/2015/06/08/elliptic-curve-cryptography-breaking-security-and-a-comparison-with-rsa/

http://www.cs.umd.edu/~gasarch/COURSES/198/Su14/baby.pdf


I used the Baby Step - Giant Step applied to a search space of 2^54 points --> 2^27 steps (more or less). It took about 18 seconds to retrieve the private key. Obviously if I had to search the private key in the entire search space of 2^256 points, I couldn't perform the 2^128 required steps (this is computationally infeasible).


If you don't believe me, pick a random 55 bit private key (below 0x0000000000000000000000000000000000000000000000000080000000000000), then generate a public key (you can use http://gobittest.appspot.com/Address), post the public key here --> I will retrieve your private key

[itod]

If you don't believe me, pick a random 55 bit private key (below 0x0000000000000000000000000000000000000000000000000080000000000000), then generate a public key (you can use http://gobittest.appspot.com/Address), post the public key here --> I will retrieve your private key

OK, here you go:

Public key:
04994AA66A13D08439CA0FFF47EBBAD07405A6D9A18EB898DA4B9D13057E99ED13FAC49FE416797 36825B3818C9424AAA5BE48E3DF17368FDBCA866047BAF48575
Address:
18fz1TWRMFJVEpmFAZcqUFrJfawkLReAuy

Please tell me the private key.

[arulbero]

If you don't believe me, pick a random 55 bit private key (below 0x0000000000000000000000000000000000000000000000000080000000000000), then generate a public key (you can use http://gobittest.appspot.com/Address), post the public key here --> I will retrieve your private key

OK, here you go:

Public key:
04994AA66A13D08439CA0FFF47EBBAD07405A6D9A18EB898DA4B9D13057E99ED13FAC49FE416797 36825B3818C9424AAA5BE48E3DF17368FDBCA866047BAF48575
Address:
18fz1TWRMFJVEpmFAZcqUFrJfawkLReAuy

Please tell me the private key.

16.8 seconds :

Code:

Private key : 0000000000000000000000000000000000000000000000000057dfa374c1d98f
Public key  : 994aa66a13d08439ca0fff47ebbad07405a6d9a18eb898da4b9d13057e99ed13 fac49fe41679736825b3818c9424aaa5be48e3df17368fdbca866047baf48575
 
PrKey WIF u.: 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nbxtoaCrX2MMwWZG
Address u.  : 5428465a5580146783bfe114e0d4f8aad3c7957e
Address u.  : 18fz1TWRMFJVEpmFAZcqUFrJfawkLReAuy

[itod]

If you don't believe me, pick a random 55 bit private key (below 0x0000000000000000000000000000000000000000000000000080000000000000), then generate a public key (you can use http://gobittest.appspot.com/Address), post the public key here --> I will retrieve your private key

OK, here you go:

Public key:
04994AA66A13D08439CA0FFF47EBBAD07405A6D9A18EB898DA4B9D13057E99ED13FAC49FE416797 36825B3818C9424AAA5BE48E3DF17368FDBCA866047BAF48575
Address:
18fz1TWRMFJVEpmFAZcqUFrJfawkLReAuy

Please tell me the private key.

16.8 seconds :

Code:

Private key : 0000000000000000000000000000000000000000000000000057dfa374c1d98f
Public key  : 994aa66a13d08439ca0fff47ebbad07405a6d9a18eb898da4b9d13057e99ed13 fac49fe41679736825b3818c9424aaa5be48e3df17368fdbca866047baf48575
 
PrKey WIF u.: 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nbxtoaCrX2MMwWZG
Address u.  : 5428465a5580146783bfe114e0d4f8aad3c7957e
Address u.  : 18fz1TWRMFJVEpmFAZcqUFrJfawkLReAuy

Congratulations, I've learned something today.

[lolobit2]

16.8 seconds :



what do you use to calculate cpu gpu ? what's the wattage?

[arulbero]

16.8 seconds :

what do you use to calculate cpu gpu ? what's the wattage?

I used a mobile cpu (only 1 core): Intel Xeon E3-1505M v6

[lolobit2]

[/quote]

I used a mobile cpu (only 1 core): Intel Xeon E3-1505M v6
[/quote]

open private messages for beginners .I can't write to you.have a suggestion

[prema]

If you don't believe me, pick a random 55 bit private key (below 0x0000000000000000000000000000000000000000000000000080000000000000), then generate a public key (you can use http://gobittest.appspot.com/Address), post the public key here --> I will retrieve your private key

OK, here you go:

Public key:
04994AA66A13D08439CA0FFF47EBBAD07405A6D9A18EB898DA4B9D13057E99ED13FAC49FE416797 36825B3818C9424AAA5BE48E3DF17368FDBCA866047BAF48575
Address:
18fz1TWRMFJVEpmFAZcqUFrJfawkLReAuy

Please tell me the private key.

16.8 seconds :

Code:

Private key : 0000000000000000000000000000000000000000000000000057dfa374c1d98f
Public key  : 994aa66a13d08439ca0fff47ebbad07405a6d9a18eb898da4b9d13057e99ed13 fac49fe41679736825b3818c9424aaa5be48e3df17368fdbca866047baf48575
 
PrKey WIF u.: 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nbxtoaCrX2MMwWZG
Address u.  : 5428465a5580146783bfe114e0d4f8aad3c7957e
Address u.  : 18fz1TWRMFJVEpmFAZcqUFrJfawkLReAuy

When do you calculate a private address for a 56bit puzzle?

Prema

[holy_ship]

When do you calculate a private address for a 56bit puzzle?

This "trick" is explained here and in LBC thread.
If someone spends PART of puzzle56, then Arulbero (or anyone who is capable of) can spend the rest.

I guess, this doesn't prove regular BTC wallets to be vulnerable, as their location in 2^159 address space is unknown.

Anyway huge respect to arulbero. He definitely didn't sleep at math classes.

[Andzhig]

I think that a novice programmer can find 56. Here that there will be further through 10-20 steps...

Arulbero looking for 56 between 00000000000000000000000000000000000000000000000000B2BE1F9B67E100 00000000000000000000000000000000000000000000000000D2BE1F9B67E100

[holy_ship]

Arulbero looking for 56 between 00000000000000000000000000000000000000000000000000B2BE1F9B67E100 00000000000000000000000000000000000000000000000000D2BE1F9B67E100

You talk some crap as usual, there are no spends on p56, so public address is unknown.

[Andzhig]

Well and how he from a transaction the public key received? sent a bit bitcoin to the address? What prevents him from doing the same thing with 56? I gave him an approximate search space.

                                              puzzle step difference                       2^difference
44        15404761757071     120349701227 >          62460552416       8796093022208        8733632469792
45        19996463086597     156222367864 >          35872666637     17592186044416       17556313377779
46        51408670348612     401630237098 >        245407869234      35184372088832      34938964219598
47      119666659114170     934895774329 >        533265537231      70368744177664      69835478640433
48      191206974700443    1493804489847 >       558908715518     140737488355328     140178579639810
49      409118905032525    3196241445566 >      1702436955719    281474976710656     279772539754937
50      611140496167764    4774535126310 >      1578293680744    562949953421312     561371659740568
51    2058769515153876   16084136837139 >    11309601710829   1125899906842624   1114590305131795
52    4216495639600700   32941372184380 >    16857235347241   2251799813685248   2234942578338007
53    6763683971478124   52841281027172 >    19899908842792  4503599627370496   4483699718527704  
54    9974455244496708   77925431597630 >    25084150570458   9007199254740992   8982115104170534
55  30045390491869460  234729613217730 >  156804181620100 18014398509481984  17857594327861884  
                                                           >                           36028797018963968  358*************


8140<->8156 in this range multiplied by 128 6 times should be 56 (if we proceed from the previous steps not 357 and not 359).

36028797018963968-8140<->8156+234729613217730x128              scanning intervals (dec)                

35800098600386560 35844079065497600                       59318788069777664 53689288535564544
35804496646897664 35848477112008704                       58755838116356352 53126338582143232
35808894693408768 35852875158519808                       58192888162935040 52563388628721920
35813292739919872 35857273205030912                       57629938209513728 52000438675300608
35817690786430976 35861671251542016                       57066988256092416 51437488721879296
35822088832942080 35866069298053120                       56504038302671104 50874538768457984
35826486879453184 35870467344564224                       55941088349249792 50311588815036672
35830884925964288 35874865391075328                       55378138395828480 49748638861615360
35835282972475392                                                   54815188442407168
35839681018986496                                                   54252238488985856  

[Narutofuc]

here are the other pvk decimal values I was able to find:

Address 15: 26867
Address 16: 51510
Address 17: 95823
Address 18: 198669
Address 19: 357535
Address 20: ?

[Andzhig]

here are the other pvk decimal values I was able to find:

Address 15: 26867
Address 16: 51510
Address 17: 95823
Address 18: 198669
Address 19: 357535
Address 20: ?

everything is already done https://bitcointalk.org/index.php?topic=1306983.msg13424809#msg13424809 https://bitcointalk.org/index.php?topic=1306983.msg13463670#msg13463670