Latest posts of: blm98

Show Posts
Pages: [1]

Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys

on: May 20, 2021, 07:56:47 PM

Quote from: Desyationer on May 20, 2021, 06:31:43 PM What is this program? It generates random addresses at a speed of 240m / s on gtx1066 and checks against the base of addresses, while for bitcrack only 25-30 in the -u -c mode and only with the specified range. I found a video on YouTube and took screenshots, perhaps the seller renamed the original version, which can be downloaded for free. Video link - https://youtu.be/5ITn7_kGb8c screen link https://ibb.co/qpz15HG https://ibb.co/9wzzVDZ https://ibb.co/Dpc0HxR https://ibb.co/YWQcqtM https://ibb.co/rZ1XPT8 It's VanitySearch... But you need to understand the BIG differences between this 2 programs : VanitySearch : Search patern of bitcoin address with random search. It's use the symetrie of the elliptic curve. Ex : privKey "1" -> Calc puKey = X, Y -> Sha256 -> Ripemd160 -> found ? no : puKey for "-1" = X, -Y -> Sha256 -> Ripemd160 -> found ? privKey "2" -> Calc puKey = X, Y -> Sha256 -> Ripemd160 -> found ? no : puKey for "-2" = X, -Y -> Sha256 -> Ripemd160 -> found ? ... So the speed is highter than Bitcrack because for 1 pubKey calc you have 2 result. But if you search in a specific range like "BitcoinChallenge", 50% of the search no use... BitCrack : Specific bitcoin address in specific range with ordered search. It don't use the symetrie of the elliptic curve. Ex : privKey "1" -> Calc puKey = X, Y -> Sha256 -> Ripemd160 -> it's equal ? privKey "2" -> Calc puKey = X, Y -> Sha256 -> Ripemd160 -> it's equal ? ... So the speed is hight for specifique range. But you need to know your graphic card to configure the program. For exemple, with a gtx 1066, the SM count is 10 so the param should be : -b 10 -t 256 -p 1024 or -b 20 -t 256 -p 768 or -b 100 -t 256 -p 512

Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys

on: May 06, 2021, 11:01:36 PM

hello, Finally, it works ! But I had to split the kernel in 2... You can see a fonctional code for the new drivers here : https://github.com/ByLamacq/BitCrack Benchmark with drivers 160.32 and Cuda 11.2 on ubuntu : - RTX 2080 => 800 MKeys /s - RTX 3090 => 1800 MKeys/s Can you build and try this ? Thx

Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys

on: April 30, 2021, 12:29:58 PM

Quote from: NotATether on April 30, 2021, 10:50:43 AM Quote from: blm98 on April 30, 2021, 05:22:42 AM Hello, So, can you tell us more about the code problem ? Thank you. At some point, Nvidia made a change in the way their newer GPUs ran CUDA code which causes a fatal Misaligned Access error when starting Bitcrack, and he apparently made a patch for it that he wants us to test. (Don't have RTX 3000 GPUs to test with, sorry richie.) Thx, but yes I know for the new drivers problem with RTX2000 and RTX3000. (I don't have this problem with an gtx 1050ti with new drivers...) I have a RTX2080 and a RTX3090 so I tried to solved the problem and so I want to understand where is the problem... ^^' I find and solved problem with constants pointers but I block on an error in sha function... I have a problem with the variables a,b,c,d,e,f,g,h... I want to understand because I don't have this problem with the same kernels with my platform test with pyCuda.

Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys

on: April 30, 2021, 05:22:42 AM

Quote from: richieburns on April 26, 2021, 09:36:10 AM https://github.com/richieburns/BitCrack_AMP/releases/download/v1.0.0_AMP/BitCrack_AMP.zip Bitcrack CUDA 11.2 Compute 8.6 Win10 Would appreciate some benchmarks for RTX 30 series cards..... Cheers Hello, So, can you tell us more about the code problem ? Thank you.

Other / Off-topic / Re: [ARCHIVE] Bitcoin challenge discusion

on: December 13, 2019, 08:47:35 PM

On a my GTX 1050ti on Ubuntu 16.04, after 3 month of development work, i get 105 Mkey/s with -p 512 and 112 MKey/sec with -p 768. I get 125 MKey/sec when the program run with nvprof but I don't know why for the moment... it's +50% from 83 MKey/sec and +100% from 64 MKey/sec !

Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys

on: December 13, 2019, 08:32:36 PM

First, thanks for the author. It's a good program. Especially for mathematical logic!

My platform : Ubuntu 16.04, GTX 1050Ti and Cuda 10.1 (15 targets compressed)

With this card, on this topic, you can normaly get 64 MKey/sec with the parameters -b 500 -t 125 -p 128
I get 69 MKey/sec and with the parameters -b 300 -t 125 -p 512 i get 83 MKey/sec

And after 3 months of development work :

Code:

./cuBitCrack -b 300 -t 128 -p 512 -o result.txt  -i targets31-45.txt
[2019-12-13.19:40:18] [Info] Compression: compressed
[2019-12-13.19:40:18] [Info] Starting at: 0000000000000000000000000000000000000000000000000000000000000001
[2019-12-13.19:40:18] [Info] Ending at:   FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
[2019-12-13.19:40:18] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-12-13.19:40:18] [Info] Initializing GeForce GTX 1050 Ti
[2019-12-13.19:40:18] [Info] Generating 19,660,800 starting points (750.0MB)
[2019-12-13.19:40:24] [Info] 10.0%
[2019-12-13.19:40:25] [Info] 20.0%
[2019-12-13.19:40:26] [Info] 30.0%
[2019-12-13.19:40:27] [Info] 40.0%
[2019-12-13.19:40:28] [Info] 50.0%
[2019-12-13.19:40:29] [Info] 60.0%
[2019-12-13.19:40:30] [Info] 70.0%
[2019-12-13.19:40:31] [Info] 80.0%
[2019-12-13.19:40:32] [Info] 90.0%
[2019-12-13.19:40:33] [Info] 100.0%
[2019-12-13.19:40:33] [Info] Done
[2019-12-13.19:40:33] [Info] Loading addresses from 'targets31-45.txt'
[2019-12-13.19:40:33] [Info] 15 addresses loaded (0.0MB)
GeForce GTX 1050 2043 / 4040MB | 15 targets 105.99 MKey/s (1,946,419,200 total) [00:00:17][2019-12-13.19:40:54] [Info] Found key for address '1LhE6sCTuGae42Axu1L1ZB7L96yi9irEBE'. Written to 'result.txt'
GeForce GTX 1050 2043 / 4040MB | 14 targets 105.52 MKey/s (2,143,027,200 total) [00:00:19]

and with -p 768 -> 112 MKey/sec

and (but i don't know why for the moment) :

Code:

sudo /usr/local/cuda/bin/nvprof -o cuBitCracktm.nvvp -f ./cuBitCrack -b 300 -t 128 -p 512 -o result.txt  -i targets31-45.txt
[sudo] Mot de passe de blm : 
==2036== NVPROF is profiling process 2036, command: ./cuBitCrack -b 300 -t 128 -p 512 -o result.txt -i targets31-45.txt
[2019-12-13.00:17:03] [Info] Compression: compressed
[2019-12-13.00:17:03] [Info] Starting at: 0000000000000000000000000000000000000000000000000000000000000001
[2019-12-13.00:17:03] [Info] Ending at:   FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
[2019-12-13.00:17:03] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-12-13.00:17:03] [Info] Initializing GeForce GTX 1050 Ti
[2019-12-13.00:17:03] [Info] Generating 19,660,800 starting points (750.0MB)
[2019-12-13.00:17:10] [Info] 10.0%
[2019-12-13.00:17:11] [Info] 20.0%
[2019-12-13.00:17:12] [Info] 30.0%
[2019-12-13.00:17:13] [Info] 40.0%
[2019-12-13.00:17:14] [Info] 50.0%
[2019-12-13.00:17:15] [Info] 60.0%
[2019-12-13.00:17:16] [Info] 70.0%
[2019-12-13.00:17:17] [Info] 80.0%
[2019-12-13.00:17:18] [Info] 90.0%
[2019-12-13.00:17:19] [Info] 100.0%
[2019-12-13.00:17:19] [Info] Done
[2019-12-13.00:17:19] [Info] Loading addresses from 'targets31-45.txt'
[2019-12-13.00:17:19] [Info] 15 addresses loaded (0.0MB)
GeForce GTX 1050 2067 / 4040MB | 15 targets 125.10 MKey/s (1,867,776,000 total) [00:00:13][2019-12-13.00:17:36] [Info] Found key for address '1LhE6sCTuGae42Axu1L1ZB7L96yi9irEBE'. Written to 'result.txt'
GeForce GTX 1050 2067 / 4040MB | 14 targets 125.49 MKey/s (3,047,424,000 total) [00:00:22][2019-12-13.00:17:44] [Info] Found key for address '1FRoHA9xewq7DjrZ1psWJVeTer8gHRqEvR'. Written to 'result.txt'
GeForce GTX 1050 2067 / 4040MB | 13 targets 124.76 MKey/s (3,755,212,800 total) [00:00:28]

This post is to show that there is still a significant room for improvement in this program.

Other / Off-topic / Re: [ARCHIVE] Bitcoin challenge discusion

on: December 13, 2019, 07:43:49 PM

Quote from: ItaCraft on October 26, 2019, 03:32:34 AM

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)

For Nvidia GTX 1050Ti (4gb) on Ubuntu 16.04 and Cuda 10.1, with the parameters that you can find on this topic (-b 500 -t 128 -p 128) you can get 69 MKey/sec with 15 targets.
Why 15 ? Because it's the limit in bitcrack between classic comparison and bloom filter to find adresses.

With the parameters : -b 300 -t 128 -p 512 -> 83 mKey/sec.
Blocks must be a multiple of Streaming Multiprocessors (SM) count.
Threads must be a multiple of 32. The true count in each SM is better...
GTX 1050Ti have 6 SM with 4 units of 32 ROPs -> 6*4*32 = 768 cuda core !

Pages: [1]