[ARCHIVE] Bitcoin challenge discusion

[itod]

Actually this was my question. I'm with you that there are only 2^160 addresses, but almost 2^256 private keys. So there should a collision, because every private key could be converted to the address only in one posible way (if we are talking about the same format, like Legacy, Segwit, bech32)
When we have a private key and the address which was generated from the private key, so the x,y coordinates of the address are in the same group as the basis point. There also should be other private keys which lead to teh same address.

And I also very curious about the ability to sign with different private keys. Imagine that somebody found 2 (or may be more) different private keys to the same address. Is it possible to make outgoing transactions with the both keys or only with that one which was primarirly used? I guess that for Legace addresses it is possible. But for beech32 addresses only one unique private key should be used. Am i right?

Yes you are right, there are about 28 million private keys for every single Bitcoin address. Whichever of these 28 million keys you find, you can take the coins from that address. Problem is you can not find the single one of those private keys by chance, let alone the other ones that lead to the same address, so this is totally unimportant. We humans are very bad with large numbers, so 2^160 looks to us very different to 2^256, while in fact they are both so big that for all practical purposes there is no difference between them, that's why the Bitcoin address scheme is designed this way.

[MrFreeDragon]

Actually this was my question. I'm with you that there are only 2^160 addresses, but almost 2^256 private keys. So there should a collision, because every private key could be converted to the address only in one posible way (if we are talking about the same format, like Legacy, Segwit, bech32)
When we have a private key and the address which was generated from the private key, so the x,y coordinates of the address are in the same group as the basis point. There also should be other private keys which lead to teh same address.

And I also very curious about the ability to sign with different private keys. Imagine that somebody found 2 (or may be more) different private keys to the same address. Is it possible to make outgoing transactions with the both keys or only with that one which was primarirly used? I guess that for Legace addresses it is possible. But for beech32 addresses only one unique private key should be used. Am i right?

Yes you are right, there are about 28 million private keys for every single Bitcoin address. Whichever of these 28 million keys you find, you can take the coins from that address. Problem is you can not find the single one of those private keys by chance, let alone the other ones that lead to the same address, so this is totally unimportant. We humans are very bad with large numbers, so 2^160 looks to us very different to 2^256, while in fact they are both so big that for all practical purposes there is no difference between them, that's why the Bitcoin address scheme is designed this way.

28 million? Oh no, much much more! In average there are 2^96 private key for every bitcoin address. 2^96 is 79.22 * 10^27, so 79 and 27 zeros after it   It is much much more than you said 28 million!

Problem here for me is not to find the private key, but to find such collission (2 different private keys to the same address). Such finding will help better understand the group of private keys. Examing such collision in details will help to understand the things which are no known now, i beleive. May be we can see something new for this bitcoin transaction chalenge as well.

The collision finding is offtopic here, so some weeks ago I created a separate discussion for it: https://bitcointalk.org/index.php?topic=5185726

[usama12]

why do check this ranges?

No logic applied. Just guesses.

[st0ffl]

Yes I am very interested about what BurtW and Telariust are doing too, that would be really interesting to see your method since without GPU, the best key/s on Pollard Rho Kangaroo are not more than 450k/s on CPU.. It's pretty good in fact but ridiculous if we compare it to GPU

I posted a solution to test in BurtW's thread.
If there are no concerns regarding the Pollard Kangaroo method and they confirm it, i will post the new table with publickeys to search for in this thread.

[johan11]

I need public key for non find number .. 64, 66 etc  nobody help my?

[st0ffl]

I need public key for non find number .. 64, 66 etc  nobody help my?

The publickeys for #64 and #66 are not revealed. There has to be an outgoing transaction to be able to get the publickey.
We only have the public keys of numbers ending with 5 and 0.

[iparktur]

I need public key for non find number .. 64, 66 etc  nobody help my?

And if for some other address?

[itod]

I need public key for non find number .. 64, 66 etc  nobody help my?

And if for some other address?

Next one where private key is still not found:

Public key for #110 = 0309976ba5570966bf889196b7fdf5a0f9a1e9ab340556ec29f8bb60599616167d

[racminer]

Hi there,
i always thought the puzzle transaction was made by LBC, actually came here cause i saw some publickeys where revealed.
Congrats to #105! Seems like 57fe is winning the race.
Can we expect from 57fe and j2002ba2 that they share their scripts involving GPU ECPoint math when #110 or #115 is found?

I'm impressed how fast the kangaroo method is, tested the python script from 57fe, the modified multicore from Telariust and read BurtW c#.
As a c# developer i was playing a lot with eliptic curve points, when i wanted to learn about bitcoin and about it's security.
Back then i never thought about the the security when you would know that a public key is in a specific space...

I developed a method the last day which is easy to implement within your scripts and halfs the searchtime per space.
Looking forward to post it in BurtW's thread later if somebody is interested.
if the table from j2002ba2 is correct using 4x V100:
#110 > 90 days > 45 days
#115 > 1 year  147 days > 256 days

What i don't understand is why the creator of the puzzle revealed the publickeys to +5 from 2^160...
Correctly there should be 161 to 255 also rewarded when dealing with such.

Yes I am very interested about what BurtW and Telariust are doing too, that would be really interesting to see your method since without GPU, the best key/s on Pollard Rho Kangaroo are not more than 450k/s on CPU.. It's pretty good in fact but ridiculous if we compare it to GPU

As a C# developer have you tried to wrote your own GPU script ?  

By the way anybody know what theses values means exactly if we want to find the #110 on this Pollard Rho GPU script https://github.com/twjvdhorst/Parallel-Pollard-Rho/? What do we have to put instead of the "1" to make it work ?

Here's the cmd :

Code:

Please give the modulus (p).
1
Please give the generator (g).
1
Please give the order of the generator (q).
1
Please give the element (y).
1
What value k for the special point condition would you like to use?
1

This is to solve g^x = y  where g is a prime order q ...

[bigvito19]

Public key for #110 = 0309976ba5570966bf889196b7fdf5a0f9a1e9ab340556ec29f8bb60599616167d
Public key for #115 = 0248d313b0398d4923cdca73b8cfa6532b91b96703902fc8b32fd438a3b7cd7f55
Public key for #120 = 02ceb6cbbcdbdf5ef7150682150f4ce2c6f4807b349827dcdbdd1f2efa885a2630
Public key for #125 = 0233709eb11e0d4439a729f21c2c443dedb727528229713f0065721ba8fa46f00e
Public key for #130 = 03633cbe3ec02b9401c5effa144c5b4d22f87940259634858fc7e59b1c09937852
Public key for #135 = 02145d2611c823a396ef6712ce0f712f09b9b4f3135e3e0aa3230fb9b6d08d1e16
Public key for #140 = 031f6a332d3c5c4f2de2378c012f429cd109ba07d69690c6c701b6bb87860d6640
Public key for #145 = 03afdda497369e219a2c1c369954a930e4d3740968e5e4352475bcffce3140dae5
Public key for #150 = 03137807790ea7dc6e97901c2bc87411f45ed74a5629315c4e4b03a0a102250c49
Public key for #155 = 035cd1854cae45391ca4ec428cc7e6c7d9984424b954209a8eea197b9e364c05f6
Public key for #160 = 02e0a8b039282faf6fe0fd769cfbc4b6b4cf8758ba68220eac420e32b91ddfa673

[almightyruler]

Public key for #160 = 02e0a8b039282faf6fe0fd769cfbc4b6b4cf8758ba68220eac420e32b91ddfa673

One of the inputs of this tx is that key:

https://www.blockchain.com/btc/tx/17e4e323cfbc68d7f0071cad09364e8193eedf8fefbcbd8a21b4b65717a4b3d3

That transaction was created to deliberately reveal the public keys for several of the challenge addresses - that's the only reason we know them.

Incidentally, the destination address for that transaction is the private key 0x1

[balskiy]

Table update with bitcrack key/rate per sec:

Code:

1. RTX 2080ti     1,200-1,300 Mkey/sec  (price $1,200-1,500)
2. GTX 2070ti     805 MMkey/sec
2. GTX 1080ti     345 Mkey/sec          (price $700-1,000)
3. GTX 1080       130 Mkey/sec          (price $500)
3. GTX 1070ti     100 Mkey/sec
3. GTX 1070       80-90 Mkey/sec        (price $450-550)
3. GTX 1060       69 Mkey/sec
4. GTX 1050ti     64 Mkey/sec           (price $150-200)
4. GTX 980        70-80 Mkey/sec
4. GTX 770(2Gb)   120 MKey/sec
4. GTX 680        109 Mkey/sec          (price $150)
4. GT 640         9 Mkey/sec      
5. RX 480         107 Mkey/sec          (price $130-150)
6. RX 470         105 Mkey/sec          (price $150-300)
7. RX 580         89 Mkey/sec           (price $200-250)
8. RX 560         50 Mkey/sec           (price $100-150)
9. R9 280/290x    20 Mkey/sec           (price $50)

RTX 2060    620 Mkey/sec 

[bulleteyedk]

RTX 2060    620 Mkey/sec

Thanks for letting us know how the performance is for RTX 2060, is this the "normal" version or the "super" version ? - if possible please let us the parameters used for -b -t -p


I talked to guy selling a GTX Titan X 12GB card this week, and asked him to run BitCrack, which he did - and he ended up tweaking it to it's max potential, which isnt too good compared to other cheaper and newer cards, but it's great for comparison.

GTX Titan X = 189 Mkey/sec (-b 96 -t 512 -p 1700) @ approx 145W

[balskiy]

RTX 2060    620 Mkey/sec

Thanks for letting us know how the performance is for RTX 2060, is this the "normal" version or the "super" version ? - if possible please let us the parameters used for -b -t -p


I talked to guy selling a GTX Titan X 12GB card this week, and asked him to run BitCrack, which he did - and he ended up tweaking it to it's max potential, which isnt too good compared to other cheaper and newer cards, but it's great for comparison.

GTX Titan X = 189 Mkey/sec (-b 96 -t 512 -p 1700) @ approx 145W

 standard version of the GeForce RTX 2060. -b 30 -t 512 -p 2400  620Mkey
 SUPER version of the GeForce RTX 2060.    -b 34 -t 512 -p 3000  765Mkey

[bulleteyedk]

great, thanks for the information for both MKey results and parameters, it's appreciated

[bulleteyedk]

 standard version of the GeForce RTX 2060. -b 30 -t 512 -p 2400  620Mkey
 SUPER version of the GeForce RTX 2060.    -b 34 -t 512 -p 3000  765Mkey

Impressive performance for those RTX 2060 cards, i've just got my hands on a RTX 2080 card, but i can only squeeze approx 775 MKey/s out of it.
using -b 32 - t 512 - p 1630 (1018.0 MB) - this is just around the max of what i can do without getting out of memory errors.

As i have only 4GB of DDR4 ram in the rig used for bitcrack, i tried installing another 8GB block, which did not make any difference.
This machine is running windows 7 x64, maybe it will run better with windows 10?

Anyone else using RTX 2080 cards? please let me know how your performance is, if those 2060 cards does nearly the same im seriously thinking of swapping the 2080 card for maybe two of those instead.

[usama12]

 standard version of the GeForce RTX 2060. -b 30 -t 512 -p 2400  620Mkey
 SUPER version of the GeForce RTX 2060.    -b 34 -t 512 -p 3000  765Mkey

Impressive performance for those RTX 2060 cards, i've just got my hands on a RTX 2080 card, but i can only squeeze approx 775 MKey/s out of it.
using -b 32 - t 512 - p 1630 (1018.0 MB) - this is just around the max of what i can do without getting out of memory errors.

As i have only 4GB of DDR4 ram in the rig used for bitcrack, i tried installing another 8GB block, which did not make any difference.
This machine is running windows 7 x64, maybe it will run better with windows 10?

Anyone else using RTX 2080 cards? please let me know how your performance is, if those 2060 cards does nearly the same im seriously thinking of swapping the 2080 card for maybe two of those instead.

I was using RTX 2080 and and the max it hit is 1300Mkeys/s.

[MrFreeDragon]

I was using RTX 2080 and and the max it hit is 1300Mkeys/s.

 Probably you are talking about 2080ti, not normal 2080

[bulleteyedk]

I was using RTX 2080 and and the max it hit is 1300Mkeys/s.

 Probably you are talking about 2080ti, not normal 2080

I agree, i really can't see a "normal" RTX 2080 getting 1300 MKey/s - if you really achieved this with a RTX 2080, then please share more about your setup

[usama12]

I was using RTX 2080 and and the max it hit is 1300Mkeys/s.

 Probably you are talking about 2080ti, not normal 2080

Sorry my mistake. yeah it was rtx 2080ti. Actually I ran bitcrack on different cards (rtx 2080ti, rtx 2080, gtx 1080ti ). but Now I forgot the actual results. I will check again on normal 2080 and will post the results here.