bounty0z
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 142
Merit: 70
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 22, 2019, 08:57:11 PM |
|
You should use the same bit version (32 or 64) and the same Python version (cp37 in the file name means Python version 3.7). The error looks like you use the incorrect wheel version.
thanks but its look like no hope ,because I use python 3.7 and x64 also, I changed to try python27 but still same error. thanks for your support. and about puzzle, What if we minimize the range of search ?!! it's possible to find it fast than full range. Thanks
|
|
|
|
brainless
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 318
Merit: 34
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 22, 2019, 09:52:29 PM |
|
You should use the same bit version (32 or 64) and the same Python version (cp37 in the file name means Python version 3.7). The error looks like you use the incorrect wheel version.
thanks but its look like no hope ,because I use python 3.7 and x64 also, I changed to try python27 but still same error. thanks for your support. and about puzzle, What if we minimize the range of search ?!! it's possible to find it fast than full range. Thanks on ubuntu first run these command with sudo apt-get install libgmp-dev apt-get install libmpfr-dev apt-get install libmpc-dev then run direct install pip install gmpy2 or downloaded gmpy2 wheel files you will success ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
13sXkWqtivcMtNGQpskD78iqsgVy9hcHLF
|
|
|
bounty0z
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 142
Merit: 70
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 22, 2019, 10:30:05 PM |
|
apt-get install libgmp-dev apt-get install libmpfr-dev apt-get install libmpc-dev
Thanks ,that was usefull in my ubuntu machine. so now we have just to specify a range and search into it to optimize our search. Hope can do it as soon as we can, even gpu membre are more powerfull XD Thanks
|
|
|
|
paniker
Newbie
Offline
Activity: 49
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 23, 2019, 01:14:15 PM |
|
I have been trying to solve the puzzle but every time I tried I got an headache. I dont know where to start and I keep on researching until I end up with nothing. I even ask some of my friends who are good with this things but I cannot understand fully their explanation. I guess I will stop doing the challenge and will focus on the signature campaign. Well good luck to you guys in solving the puzzle its hopeless for me.
Just a every day. https://www.youtube.com/watch?v=im2VlRprLVchow can i play the same? )
|
|
|
|
mrxtraf
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 23, 2019, 01:50:56 PM |
|
I have been trying to solve the puzzle but every time I tried I got an headache. I dont know where to start and I keep on researching until I end up with nothing. I even ask some of my friends who are good with this things but I cannot understand fully their explanation. I guess I will stop doing the challenge and will focus on the signature campaign. Well good luck to you guys in solving the puzzle its hopeless for me.
Just a every day. https://www.youtube.com/watch?v=im2VlRprLVchow can i play the same? ) https://mrxtraf.github.io/brainwalletXX/#game
|
|
|
|
ItaCraft
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 138
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 26, 2019, 03:32:34 AM |
|
Table update with bitcrack key/rate per sec: 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
|
|
|
|
bulleteyedk
Jr. Member
Offline
Activity: 85
Merit: 1
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 26, 2019, 10:01:35 AM |
|
@ItaCraft
RTX 2080 is running smoothly at 875-885 MKey/s with the parameters: -b 46 -t 512 -p 1000
|
|
|
|
bounty0z
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 142
Merit: 70
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 26, 2019, 11:14:21 AM |
|
Table update with bitcrack key/rate per sec: 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
Offline
Activity: 85
Merit: 1
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 26, 2019, 12:00:05 PM |
|
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](https://bitcointalk.org/Smileys/default/wink.gif)
|
|
|
|
bounty0z
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 142
Merit: 70
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 26, 2019, 01:01:18 PM |
|
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
Offline
Activity: 85
Merit: 1
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 26, 2019, 01:21:24 PM |
|
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
|
|
|
|
ItaCraft
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 138
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 26, 2019, 02:00:38 PM |
|
@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 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
|
|
|
|
bounty0z
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 142
Merit: 70
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 26, 2019, 02:00:59 PM |
|
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
|
|
|
|
MrFreeDragon
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 30, 2019, 02:04:01 AM |
|
hi
Public key #110 = 0309976ba5570966bf889196b7fdf5a0f9a1e9ab340556ec29f8bb60599616167d
is this public key?
Yes, correct. From the last spending #110 transation: PUSHDATA(33)[ 0309976ba5570966bf889196b7fdf5a0f9a1e9ab340556ec29f8bb60599616167d]
|
|
|
|
H3XBAE
Newbie
Offline
Activity: 4
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 01, 2019, 01:12:29 PM |
|
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
|
|
|
|
iparktur
Jr. Member
Offline
Activity: 119
Merit: 1
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 01, 2019, 02:32:19 PM |
|
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
Offline
Activity: 4
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 01, 2019, 07: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
|
|
|
|
iparktur
Jr. Member
Offline
Activity: 119
Merit: 1
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 01, 2019, 07: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
Many addresses multiple of 5 (#65; #75; #85, etc.) have already been resolved. Check out this thread above.
|
|
|
|
mrxtraf
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 01, 2019, 07:49:02 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?
|
|
|
|
almightyruler
Legendary
Offline
Activity: 2268
Merit: 1092
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 02, 2019, 03:04:36 AM |
|
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.
|
|
|
|
|