Topic: [ARCHIVE] Bitcoin challenge discusion - page 12. (Read 28991 times)
GTX 1660 - 4015/6144MB | 14 targets 475.38 MKey/s
Thanks for sharing, I guess I'll try to write some code to bruteforce some of the smallest unclaimed keys, though I don't hope to find anything, cause my CPU isn't very strong. I have a GTX 1060 gpu though, but I only know Javascript so it will be a bit hard to write a program that utilizes my gpu, but it should be possible. Should be a fun pet project that will at least provide me some experience.
there is no more "unclaimed" keys left with a private keys in small ranges. they were all found a long time ago. now only the big ones are remaining and claiming each is getting harder exponentially as the power of 2 is incremented by one.
if you want to have fun, you can program something. i did that a while ago in c# for small ones as a "challenge" to my skills knowing there is no other reward.
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.
you should use -b 46. since the card contains 46 SM Count
try -b 46 -t 512 -p 3000
Thanks for updating me on the matter of those SM counts, this is new to me, I have all the time concluded that the -b parameter should be used in parallel with ROP counts, but since -b 64 wasn't giving me the best performance i lowered it with /2 going with -b 32 then... great information, thanks
Now i managed to get approx 882 MKey/s with -b 46 -t 512 - p 950 this allocates 22.374.400 starting points (853 MB) which is close to the max for me, please let me know how it's possible to allocate more RAM on the card without memory error.
Once Bitcrack runs it shows 2349/8192MB used
EDIT: in parallel im also running another Bitcrack instance on this rig with an older GTX 770 card, allocating approx 390 MB in starting points, maybe I should try to benchmark the RTX 2080 without running the other card too
EDIT2: running with only one instance of Bitcrack, i can achieve 890 MKey/s with RTX 2080 using parameters: -b 46 - t 512 -t 1000
GRID V100D-32Q 25607 / 32638MB | 4 targets 1302.53 MKey/s
What is your b value? I got more than 1,500 mkeys on Tesla v100 with a value of -b 80 - t 512 -p 2800 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.
you should use -b 46. since the card contains 46 SM Count
try -b 46 -t 512 -p 3000
GRID V100D-32Q 25607 / 32638MB | 4 targets 1302.53 MKey/s
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.
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
I was using RTX 2080 and and the max it hit is 1300Mkeys/s.
Probably you are talking about 2080ti, not normal 2080
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.
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.
great, thanks for the information for both MKey results and parameters, it's appreciated
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
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
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)
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
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
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
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
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.
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
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
I need public key for non find number .. 64, 66 etc nobody help my?
nobody help my?And if for some other address?
Next one where private key is still not found:
Public key for #110 = 0309976ba5570966bf889196b7fdf5a0f9a1e9ab340556ec29f8bb60599616167d
I need public key for non find number .. 64, 66 etc nobody help my?
nobody help my?And if for some other address?
Jump to: