[ARCHIVE] Bitcoin challenge discusion - page 9.

bounty0z

member

Activity: 142

Merit: 70

Quote from: ttdclient on November 04, 2019, 02:14:53 AM

I did not realize there was another thread on this topic I guess I was posting in the older one.

Just wanted to let people following this thread know about the pool I have created for collectively finding the solution to bit 64.

If you go to http://www.ttdsales.com/64bit/

You can create an account and then you will have access to the user and stats page. From there you can download the client software.

It works with bitcrack and allows all of us to work together without ever checking keys that have already been checked.

Shows top ten contributors and collected proceeds will be divided accordingly for the work contributed.

its only for windows !! did you have linux version ?

bulleteyedk

jr. member

Activity: 84

Merit: 1

Quote from: ttdclient on November 04, 2019, 02:14:53 AM

I did not realize there was another thread on this topic I guess I was posting in the older one.

Just wanted to let people following this thread know about the pool I have created for collectively finding the solution to bit 64.

If you go to http://www.ttdsales.com/64bit/

You can create an account and then you will have access to the user and stats page. From there you can download the client software.

It works with bitcrack and allows all of us to work together without ever checking keys that have already been checked.

Shows top ten contributors and collected proceeds will be divided accordingly for the work contributed.

Cool, i will def. look into this, thanks for sharing Wink

ttdclient

jr. member

Activity: 34

Merit: 11

I did not realize there was another thread on this topic I guess I was posting in the older one.

Just wanted to let people following this thread know about the pool I have created for collectively finding the solution to bit 64.

If you go to http://www.ttdsales.com/64bit/

You can create an account and then you will have access to the user and stats page. From there you can download the client software.

It works with bitcrack and allows all of us to work together without ever checking keys that have already been checked.

Shows top ten contributors and collected proceeds will be divided accordingly for the work contributed.

bulleteyedk

jr. member

Activity: 84

Merit: 1

Quote from: ?? on ??

Guys, what keys rate of BitCrack will be on rtx 2070(not Ti)? Is there any influence of processor for video card keys rate?

Expect to get approx. 650-700 MKey/s

This is the performance for the GPU's just above and under yours:
RTX 2080 = 885 MKey/s
RTX 2060 = 620 MKey/s

Regards your question i really don't think it matter how fast/slow your CPU is, im running on an old mining rig with a lowcost CPU.

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: ?? on ??

Knowing the public key reduces some of the other things you have to calculate at that step.
If you are generating key pairs, you just have to check the public key at that point, without proceeding to see if it comes back to the desired address, and you can move on to the next key pair generation.

What you've described is a minor optimization of basic brute forcing. It may improve speed by a small factor, but it's still brute forcing.

Both Pollard's Kangaroo and Baby-Step Giant-Step use a different method to crack the key.

To demonstrate: I mentioned in an earlier message that my old Xeon server could crack 57 bits in 13 minutes using BSGS... and that's using a single CPU core only (no GPU acceleration). To try every combination with brute forcing in that same 13 minutes would require a potential generation rate of something like 184 trillion keys per second. You'd need about 140,000 high end GPUs running BitCrack to do that.

bounty0z

member

Activity: 142

Merit: 70

Quote from: iparktur on November 01, 2019, 03:48:13 PM

No I mean like , 63 and 65 were solved but 64 should be lower then 65 , So how come its not solved O_o

to understand well, all wallet with 65 ,70,75,80,85 .... 115 ,120 ,all of them sent a transaction so we know the public key of them.
in mathematics if we know public key ,we can solve a elliptic curve equation to find the private key using the poolar kangaroo algorithm. but it take time for any case have to found.
for now this algorithm tried to find the 110# but it will take like 90days or under to find it, depend on your calcul rate(gpu,cpu)
as you can see in comments ,the one who find the 105# he take two weeks to find the code ,so you can't just say we can find from 1 to 1000 using this algorithme, and as I know the wallet 115# will take years to find it so we have to find another solution.

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: H3XBAE on November 01, 2019, 03:41:42 PM

No I mean like , 63 and 65 were solved but 64 should be lower then 65 , So how come its not solved O_o

#63 was solved by brute force (presumably).
#65 was solved because the public key is known, which can be cracked more efficiently than by pure brute force.

Every 5th address has had its public key revealed. That's how #65, #70, #75, #80, #85, #90, #95, #100, #105 were solved, but people are still stuck with brute forcing #64.

mrxtraf

member

Activity: 255

Merit: 27

Quote from: H3XBAE on November 01, 2019, 03:41:42 PM

No I mean like , 63 and 65 were solved but 64 should be lower then 65 , So how come its not solved O_o

65 resolved because resolved 70 and 75 and 80 etc. Because they know public keys. What is difficult to read the topic?

iparktur

jr. member

Activity: 119

Merit: 1

Quote from: H3XBAE on November 01, 2019, 03:41:42 PM

No I mean like , 63 and 65 were solved but 64 should be lower then 65 , So how come its not solved O_o

Many addresses multiple of 5 (#65; #75; #85, etc.) have already been resolved.
Check out this thread above.

H3XBAE

newbie

Activity: 4

Merit: 0

No I mean like , 63 and 65 were solved but 64 should be lower then 65 , So how come its not solved O_o

iparktur

jr. member

Activity: 119

Merit: 1

Quote from: H3XBAE on November 01, 2019, 09:12:29 AM

Guys Im pretty new to this ,
I just had to ask.

I see that 63 and 65 are solved but 64 is empty.
Does that mean some one have solved it and changed the key OR no one solved it ? Im just curios as to why its not solved while both 63 and 65 are solved

#64 - 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN - 0.64002564 BTC

H3XBAE

newbie

Activity: 4

Merit: 0

Guys Im pretty new to this ,
I just had to ask.

I see that 63 and 65 are solved but 64 is empty.
Does that mean some one have solved it and changed the key OR no one solved it ? Im just curios as to why its not solved while both 63 and 65 are solved

MrFreeDragon

sr. member

Activity: 443

Merit: 350

Quote from: ?? on ??

hi

Public key #110 = 0309976ba5570966bf889196b7fdf5a0f9a1e9ab340556ec29f8bb60599616167d

is this public key?

Yes, correct.
From the last spending #110 transation: PUSHDATA(33)[0309976ba5570966bf889196b7fdf5a0f9a1e9ab340556ec29f8bb60599616167d]

bounty0z

member

Activity: 142

Merit: 70

Quote from: bulleteyedk on October 26, 2019, 09:21:24 AM

try to see how high you can get the -p value for these before you get memory error:

-b 52 -t 256 - p 1200
-b 26 -t 512 - p 1000

im surprised the result is not a bit higher to be honest, but some card are better for this bitcrack than others, this also shows just that unfortunally

After trying : -b 52 -t 512 -p 1200
I use CUDA 10.0

[2019-10-26.13:56:49] [Info] Initializing Tesla K80
[2019-10-26.13:56:49] [Info] Generating 31,948,800 starting points (1218.8MB)
tcmalloc: large alloc 1073741824 bytes == 0x55cef84c8000 @ 0x7fd3ac675887 0x55ceb65d3d45 0x55ceb65d9d3b 0x55ceb65da15f 0x55ceb65cd5c0 0x55ceb65c901e 0x55ceb65c2e00 0x7fd3ab6b7b97 0x55ceb65c491a
[2019-10-26.13:56:49] [Info] Compression: compressed
[2019-10-26.13:56:49] [Info] Starting at: 0000000000000000000000000000000000000000000000008000000000000000
[2019-10-26.13:56:49] [Info] Ending at: 000000000000000000000000000000000000000000000000FFFFFFFFFF000000
[2019-10-26.13:56:49] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-10-26.13:56:49] [Info] Initializing Tesla K80
[2019-10-26.13:56:49] [Info] Generating 31,948,800 starting points (1218.8MB)
tcmalloc: large alloc 1073741824 bytes == 0x55cef84c8000 @ 0x7fd3ac675887 0x55ceb65d3d45 0x55ceb65d9d3b 0x55ceb65da15f 0x55ceb65cd5c0 0x55ceb65c901e 0x55ceb65c2e00 0x7fd3ab6b7b97 0x55ceb65c491a
[2019-10-26.13:57:00] [Info] 10.0%
.....
[2019-10-26.13:57:10] [Info] 100.0%
[2019-10-26.13:57:10] [Info] Done
Tesla K80 2993 / 11441MB | 1 target 115.58 MKey/s (5,814,681,600 total)

As you said its look like K80 not that good in bruteforcing, if I keep bruteforcing like that I think I need more than 100year

Thanks

ItaCraft

member

Activity: 138

Merit: 10

Quote from: bulleteyedk on October 26, 2019, 06:01:35 AM

@ItaCraft

RTX 2080 is running smoothly at 875-885 MKey/s with the parameters: -b 46 -t 512 -p 1000

Thank you for the info, I'm running with -b 192 -t 256 -p 1024
It added + 20Mkey/s when running with 2M keys

Quote from: bounty0z on October 26, 2019, 09:01:18 AM

for my Tesla K80

-b 13 -t 256 - p 1200 (basic settings) ==> 55MKey/s
-b 26 -t 256 - p 1200 (double SM) ==> 99Mkey/s
-b 39 -t 256 - p 1200 (triple SM) ==> 108Mkey/s
-b 52 -t 256 - p 1200 (quad SM) ==> 117Mkey/s

-b 13 -t 512 - p 1000 (basic settings) ==> 99MKey/s
-b 26 -t 512 - p 1000 (double SM) ==> 125Mkey/s
-b 39 -t 512 - p 1000 (triple SM) ===> alloc error and get 110Mkey
-b 52 -t 512 - p 1000 (quad SM) == alloc error and get 110Mkey

Here are my results, thanks for you support

Oh sorry now I see my mistake, Tesla K80 is running at 105 Mkey/s no matter how many keys, I made an confusion because I also tested Tesla T4 that gave me 250Mkey/s but only 100 Mkey/s when using my 2M keys list

bulleteyedk

jr. member

Activity: 84

Merit: 1

try to see how high you can get the -p value for these before you get memory error:

-b 52 -t 256 - p 1200
-b 26 -t 512 - p 1000

im surprised the result is not a bit higher to be honest, but some card are better for this bitcrack than others, this also shows just that unfortunally

bounty0z

member

Activity: 142

Merit: 70

for my Tesla K80

-b 13 -t 256 - p 1200 (basic settings) ==> 55MKey/s
-b 26 -t 256 - p 1200 (double SM) ==> 99Mkey/s
-b 39 -t 256 - p 1200 (triple SM) ==> 108Mkey/s
-b 52 -t 256 - p 1200 (quad SM) ==> 117Mkey/s

-b 13 -t 512 - p 1000 (basic settings) ==> 99MKey/s
-b 26 -t 512 - p 1000 (double SM) ==> 125Mkey/s
-b 39 -t 512 - p 1000 (triple SM) ===> alloc error and get 110Mkey
-b 52 -t 512 - p 1000 (quad SM) == alloc error and get 110Mkey

Here are my results, thanks for you support

bulleteyedk

jr. member

Activity: 84

Merit: 1

Based on performance data from all the other cards posted in here i would asume your Tesla K80 card should be able to do around ~ 200-245 MKey/s with the right parameters.

I would try something like this:

-b 13 -t 256 - p 1200 (basic settings)
-b 26 -t 256 - p 1200 (double SM)
-b 39 -t 256 - p 1200 (triple SM)
-b 52 -t 256 - p 1200 (quad SM)

try these as your basic parameters, the -p parameter you can lower or raise to max performance before you hit a memory error, so it's trial and error to get to the best performance settings
you might as well try the same settings with -t 512, doing that might require you to lower the -p parameter as shown below:

-b 13 -t 512 - p 1000 (basic settings)
-b 26 -t 512 - p 1000 (double SM)
-b 39 -t 512 - p 1000 (triple SM)
-b 52 -t 512 - p 1000 (quad SM)

let us know how this turns out Wink

bounty0z

member

Activity: 142

Merit: 70

Quote from: ItaCraft on October 25, 2019, 11:32:34 PM

Table update with bitcrack key/rate per sec:

Code:

1. RTX 2080ti 1,200-1,300 Mkey/sec (price $1,200-1,500)
2. RTX 2080 810 Mkey/s | 300 Mkey/s (2M addresses)
3. GTX 2070ti 805 Mkey/sec
4. RTX 2060 620 Mkey/sec
5. GTX 1080ti 345 Mkey/sec (price $700-1,000)
6. Tesla K80 250 Mkey/sec | 100 Mkes/s (2M addresses)
7. GTX 1080 130 Mkey/sec (price $500)
8. GTX 1070ti 100 Mkey/sec
9. GTX 1070 80-90 Mkey/sec (price $450-550)
10. GTX 1060 69 Mkey/sec
11. GTX 1050ti 64 Mkey/sec (price $150-200)
12. GTX 980 70-80 Mkey/sec
13. GTX 770(2Gb) 120 MKey/sec
14. GTX 680 109 Mkey/sec (price $150)
15. GT 640 9 Mkey/sec
16. RX 480 107 Mkey/sec (price $130-150)
17. RX 470 105 Mkey/sec (price $150-300)
18. RX 580 89 Mkey/sec (price $200-250)
19. RX 560 50 Mkey/sec (price $100-150)
20. R9 280/290x 20 Mkey/sec (price $50)

Added RTX 2080 and Tesla K80

Please you have parameter of tesla k80 ,because i only get 100mkey/s . if you have any idea how to get more please show me how.

bulleteyedk

jr. member

Activity: 84

Merit: 1

@ItaCraft

RTX 2080 is running smoothly at 875-885 MKey/s with the parameters: -b 46 -t 512 -p 1000

Topic: [ARCHIVE] Bitcoin challenge discusion - page 9. (Read 28991 times)