VanitySearch (Yet another address prefix finder) - page 60.

arulbero

legendary

Activity: 1932

Merit: 2077

Quote from: stivensons on March 04, 2019, 10:00:59 AM

Compressed

Code:

G:\bit\cuBitCrack.exe -c -d 0 1CF1o6DRBpyGXqQXVJHTGiHNVVu54npgHo
[2019-03-04.21:54:29] [Info] Compression: compressed
GeForce GTX 1060 1083/6144MB | 1 target 58.56 MKey/s (1,473,773,568 total) [00:00:23]

Uncompressed

Code:

G:\bit\cuBitCrack.exe -u -d 0 1CF1o6DRBpyGXqQXVJHTGiHNVVu54npgHo
[2019-03-04.21:53:35] [Info] Compression: uncompressed
GeForce GTX 1060 1083/6144MB | 1 target 51.94 MKey/s (1,238,368,256 total) [00:00:21]

Both

Code:

G:\bit\cuBitCrack.exe -c -u -d 0 1CF1o6DRBpyGXqQXVJHTGiHNVVu54npgHo
[2019-03-04.21:52:18] [Info] Compression: both
GeForce GTX 1060 1083/6144MB | 1 target 46.99 MKey/s (1,696,071,680 total) [00:00:34]

Then with GeForce GTX 1060:

bitcrack: 58.5 MKeys/s

VanitySearch: 580/7 = 82 MKeys/s

Jean_Luc

sr. member

Activity: 462

Merit: 701

Code:

[quote author=stivensons link=topic=5112311.msg50017516#msg50017516 date=1551710888]
Will there be settings like Bitcrack in the future?
 -i, --in FILE
Read addresses from FILE, one address per line. If FILE is "-" then stdin is read

Yes, I'm thinking to add this. It will need an important refurbishment of the code however it goes in the same way as optimizing data transfer. So probably yes.

Quote from: stivensons on March 04, 2019, 09:48:08 AM

Code:

--keyspace KEYSPACE
    Specify the range of keys to search, where KEYSPACE is in the format,

	START:END start at key START, end at key END
	START:+COUNT start at key START and end at key START + COUNT
    :END start at key 1 and end at key END
	:+COUNT start at key 1 and end at key 1 + COUNT

No (if I understand well the purpose of this option).
VanitySearch is a prefix finder in order to generate usable addresses, you can specifie a seed to generate a base key ,it is even recommended. That's all. The seed is then passed into a pbkdf2_hmac_sha512 in order to protect against seed search attack. If you don't specifie the seed, the basekey is generated using timestamps (in us) plus the date and also passed into the pbkdf2_hmac_sha512.
The result of the pbkdf2_hmac_sha512 is then passed into a SHA256 wich is use as the base key.

stivensons

jr. member

Activity: 82

Merit: 1

Quote from: arulbero on March 04, 2019, 08:07:55 AM

To do a comparison with another software, bitcrack (that has a different goal, instead of having a set of same prefix addresses it has as target a set of addresses with funds, but more or less both programs do the same calculations):

https://bitcointalksearch.org/topic/bitcrack-a-tool-for-brute-forcing-private-keys-4453897

in particular:

Quote

GeForce GTX 1060 3GB = compressed = 60.61 MKeys/s
GeForce GTX 1060 3GB = both = 46.93 MKeys/s

Compressed

Code:

G:\bit\cuBitCrack.exe -c -d 0 1CF1o6DRBpyGXqQXVJHTGiHNVVu54npgHo
[2019-03-04.21:54:29] [Info] Compression: compressed
[2019-03-04.21:54:29] [Info] Starting at: 0000000000000000000000000000000000000000000000000000000000000001
[2019-03-04.21:54:29] [Info] Ending at:   FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
[2019-03-04.21:54:29] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-03-04.21:54:29] [Info] Initializing GeForce GTX 1060 6GB
[2019-03-04.21:54:29] [Info] Generating 262,144 starting points (10.0MB)
[2019-03-04.21:54:29] [Info] 10.0%
[2019-03-04.21:54:29] [Info] 20.0%
[2019-03-04.21:54:29] [Info] 30.0%
[2019-03-04.21:54:29] [Info] 40.0%
[2019-03-04.21:54:29] [Info] 50.0%
[2019-03-04.21:54:29] [Info] 60.0%
[2019-03-04.21:54:29] [Info] 70.0%
[2019-03-04.21:54:29] [Info] 80.0%
[2019-03-04.21:54:30] [Info] 90.0%
[2019-03-04.21:54:30] [Info] 100.0%
[2019-03-04.21:54:30] [Info] Done
GeForce GTX 1060 1083/6144MB | 1 target 58.56 MKey/s (1,473,773,568 total) [00:00:23]

Uncompressed

Code:

G:\bit\cuBitCrack.exe -u -d 0 1CF1o6DRBpyGXqQXVJHTGiHNVVu54npgHo
[2019-03-04.21:53:35] [Info] Compression: uncompressed
[2019-03-04.21:53:35] [Info] Starting at: 0000000000000000000000000000000000000000000000000000000000000001
[2019-03-04.21:53:35] [Info] Ending at:   FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
[2019-03-04.21:53:35] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-03-04.21:53:35] [Info] Initializing GeForce GTX 1060 6GB
[2019-03-04.21:53:36] [Info] Generating 262,144 starting points (10.0MB)
[2019-03-04.21:53:36] [Info] 10.0%
[2019-03-04.21:53:36] [Info] 20.0%
[2019-03-04.21:53:36] [Info] 30.0%
[2019-03-04.21:53:36] [Info] 40.0%
[2019-03-04.21:53:36] [Info] 50.0%
[2019-03-04.21:53:36] [Info] 60.0%
[2019-03-04.21:53:36] [Info] 70.0%
[2019-03-04.21:53:36] [Info] 80.0%
[2019-03-04.21:53:36] [Info] 90.0%
[2019-03-04.21:53:36] [Info] 100.0%
[2019-03-04.21:53:36] [Info] Done
GeForce GTX 1060 1083/6144MB | 1 target 51.94 MKey/s (1,238,368,256 total) [00:00:21]

Both

Code:

G:\bit\cuBitCrack.exe -c -u -d 0 1CF1o6DRBpyGXqQXVJHTGiHNVVu54npgHo
[2019-03-04.21:52:18] [Info] Compression: both
[2019-03-04.21:52:18] [Info] Starting at: 0000000000000000000000000000000000000000000000000000000000000001
[2019-03-04.21:52:18] [Info] Ending at:   FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
[2019-03-04.21:52:18] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-03-04.21:52:18] [Info] Initializing GeForce GTX 1060 6GB
[2019-03-04.21:52:19] [Info] Generating 262,144 starting points (10.0MB)
[2019-03-04.21:52:19] [Info] 10.0%
[2019-03-04.21:52:19] [Info] 20.0%
[2019-03-04.21:52:19] [Info] 30.0%
[2019-03-04.21:52:19] [Info] 40.0%
[2019-03-04.21:52:19] [Info] 50.0%
[2019-03-04.21:52:19] [Info] 60.0%
[2019-03-04.21:52:19] [Info] 70.0%
[2019-03-04.21:52:19] [Info] 80.0%
[2019-03-04.21:52:19] [Info] 90.0%
[2019-03-04.21:52:19] [Info] 100.0%
[2019-03-04.21:52:20] [Info] Done
GeForce GTX 1060 1083/6144MB | 1 target 46.99 MKey/s (1,696,071,680 total) [00:00:34]

stivensons

jr. member

Activity: 82

Merit: 1

Quote from: Jean_Luc on March 04, 2019, 09:28:11 AM

Quote from: stivensons on March 04, 2019, 09:19:09 AM

I get the same ~ 580mk\s

OK Thank you for the test.
With the optimizations suggested by arulbero , with few memory transfer improvements, by adding specific GPU intrinsic (notably the funnel shift that should improve SHA and RIPE performance), I hope to reach 1GK/s on your config. Wink

Waiting for a new version

Will there be settings like Bitcrack in the future?

Code:

 -i, --in FILE
Read addresses from FILE, one address per line. If FILE is "-" then stdin is read

Code:

--keyspace KEYSPACE
    Specify the range of keys to search, where KEYSPACE is in the format,

	START:END start at key START, end at key END
	START:+COUNT start at key START and end at key START + COUNT
    :END start at key 1 and end at key END
	:+COUNT start at key 1 and end at key 1 + COUNT

Jean_Luc

sr. member

Activity: 462

Merit: 701

Quote from: stivensons on March 04, 2019, 09:19:09 AM

I get the same ~ 580mk\s

OK Thank you for the test.
With the optimizations suggested by arulbero , with few memory transfer improvements, by adding specific GPU intrinsic (notably the funnel shift that should improve SHA and RIPE performance), I hope to reach 1GK/s on your config. Wink

stivensons

jr. member

Activity: 82

Merit: 1

Quote from: arulbero on March 04, 2019, 08:07:55 AM

To do a comparison with another software, bitcrack (that has a different goal, instead of having a set of same prefix addresses it has as target a set of addresses with funds, but more or less both programs do the same calculations):

https://bitcointalksearch.org/topic/bitcrack-a-tool-for-brute-forcing-private-keys-4453897

in particular:

Quote

GeForce GTX 1060 3GB = compressed = 60.61 MKeys/s
GeForce GTX 1060 3GB = both = 46.93 MKeys/s

I will test and write the results

stivensons

jr. member

Activity: 82

Merit: 1

Quote from: Jean_Luc on March 04, 2019, 07:55:06 AM

OK Thanks
So it is similar.
Could try now
vanitysearch -stop -t 0 -gpu -gpuId 0,1,2,3,4,5,6 -g 160,160,160,160,160,160,144 1Testtttt.
It we still have same perf, that means that the default setting are rather good.

I get the same ~ 580mk\s

Jean_Luc

sr. member

Activity: 462

Merit: 701

On my hardware, bitcrak (cuda version) is rather slow. With a single target, compressed, I reach only 15 MK/s against 26MK/s with vanitysearch.

arulbero

legendary

Activity: 1932

Merit: 2077

To do a comparison with another software, bitcrack (that has a different goal, instead of having a set of same prefix addresses it has as target a set of addresses with funds, but more or less both programs do the same calculations):

https://bitcointalksearch.org/topic/bitcrack-a-tool-for-brute-forcing-private-keys-4453897

in particular:

Quote

GeForce GTX 1060 3GB = compressed = 60.61 MKeys/s
GeForce GTX 1060 3GB = both = 46.93 MKeys/s

Jean_Luc

sr. member

Activity: 462

Merit: 701

OK Thanks
So it is similar.
Could try now
vanitysearch -stop -t 0 -gpu -gpuId 0,1,2,3,4,5,6 -g 160,160,160,160,160,160,144 1Testtttt.
It we still have same perf, that means that the default setting are rather good.

stivensons

jr. member

Activity: 82

Merit: 1

Quote from: Jean_Luc on March 04, 2019, 01:57:54 AM

Done

~580 mk\s

Code:

G:\vanitysearch>vanitysearch -stop -t 0 -gpu -gpuId 0,1,2,3,4,5,6 1Testtttt
Start Mon Mar 4 19:44:19 2019
Search: 1Testtttt
Difficulty: 2988734397852221
Base Key:7AE06275083610799006F50B0FE5BBD967F3DD8F9961CB07C69A006610F1F58D
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #3 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #5 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #4 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #1 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)y]
GPU: GPU #2 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #6 GeForce GTX 1060 3GB (9x128 cores) Grid(72x128)fy]
578.045 MK/s (GPU 578.045 MK/s) (2^36.43) [P 0.00%][50.00% in 41.7d]]

Lolo54

member

Activity: 117

Merit: 32

For me Jean_Luc increase 25%
Start Mon Mar 4 13:37:46 2019
Search: 1test
Difficulty: 264104224
Base Key:28FB7A9193F49D3D8F63B1E05F0556D3EF57AF1F0ADCD83F8D6A399C8C110D5B
Number of CPU thread: 4
1.970 MK/s (GPU 0.000 MK/s) (2^26.47) [P 29.69%][50.00% in 00:00:50][0]
Pub Addr: 1testwtBewKHpZTwLYggYLzv4rNohko9X

1.970 vs 1.616

Jean_Luc

sr. member

Activity: 462

Merit: 701

Done

stivensons

jr. member

Activity: 82

Merit: 1

Quote from: Jean_Luc on March 04, 2019, 01:53:05 AM

Quote from: stivensons on March 04, 2019, 12:22:58 AM

CPU 20-25% Cool

OK, thanks. Could you try this release:
http[Suspicious link removed]
I changed the number of thread per block to 128 and divided by 2 the default number of block per grid.
I would like to know if, on your config, it improves performance, it is the same or it is worst ?
Thank you

link removed Sad

, upload to github as test release

Jean_Luc

sr. member

Activity: 462

Merit: 701

Quote from: stivensons on March 04, 2019, 12:22:58 AM

CPU 20-25% Cool

OK, thanks. Could you try the release 1.5.1 (Available on gitbub)
I changed the number of thread per block to 128 and divided by 2 the default number of block per grid.
I would like to know if, on your config, it improves performance, it is the same or it is worst ?
Thank you

Edit :
Changed the link

stivensons

jr. member

Activity: 82

Merit: 1

Quote from: Jean_Luc on March 03, 2019, 11:44:45 AM

Ok Thanks.

So it seems that the CPU is not able to handle the key rate. If i believe the output you give, it seems that your CPU is a dual core ?
If you launch the task manager, your CPU is at 100% ?
I think I have to optimize the exchange between CPU and GPU. This is also in my task list.
A good challenge would be to reach 1GK/s on your config Cheesy

CPU 20-25% Cool

Lolo54

member

Activity: 117

Merit: 32

ok thank you for the answer jean_luc I thought well that he had a problem with the old age of my equipment. good I’ll try to see it gets there but given my great talent I don’t think:-)

Jean_Luc

sr. member

Activity: 462

Merit: 701

Quote from: Lolo54 on March 03, 2019, 11:48:00 AM

Hello on my side being on a GPU GeForce GT 520 M/ Cuda 8/ driver 391.35/ windows 10 64 / version of appi direct3D 11.2/CUDA 48 ...I have the following error message with the command -gpu 1TEST

Aie !
The problem is that the current CUDA SDK does not support anymore old compute capabilities.
The GeForce GT 520 M has compute capability 2.1 (as my old Quadro 600).
To make my old Quadro work I had to compile VanitySearch with CUDA SDK 8.0 (under Linux)
The current release of VanitySearch (for windows) is compiled with CUDA SDK 10.0.
So you can try to compile VanitySearch by yourself.
Visual Studio Community Edition 2017 is free.
CUDA SDK 8.0 is still available from nVidia site.
Follow the instruction on the VanitySearch HomePage.

Lolo54

member

Activity: 117

Merit: 32

Hello on my side being on a GPU GeForce GT 520 M/ Cuda 8/ driver 391.35/ windows 10 64 / version of appi direct3D 11.2/CUDA 48 ...I have the following error message with the command -gpu 1TEST

-gpu 1test
Start Sun Mar 3 17:38:59 2019
Search: 1test
Difficulty: 264104224
Base Key:FB566C95AB1A65C55F3B3B2608708D53FF1913130D1FB445369683CA2EF7DB8D
Number of CPU thread: 3
GPUEngine: CudaGetDeviceCount CUDA driver version is insufficient for CUDA runtime version
GPU:
GPUEngine: Kernel: CUDA driver version is insufficient for CUDA runtime version

how to fix it? Is this a problem due my old hardware or driver not up to date?
if I move to a higher version of Cuda on my pc impossible to install ca tells me not compatible Undecided

otherwise it works fine but I’m on that speed there Cry

Start Sun Mar 3 17:42:11 2019
Search: 1test
Difficulty: 264104224
Base Key:906001ED1C80550A53E5BCEA4C797442E8A698379040155C046F3CC9ADD665C2
Number of CPU thread: 4
1.616 MK/s (GPU 0.000 MK/s) (2^21.67) [P 1.26%][50.00% in 00:01:51][0]

Jean_Luc

sr. member

Activity: 462

Merit: 701

Ok Thanks.

So it seems that the CPU is not able to handle the key rate. If i believe the output you give, it seems that your CPU is a dual core ?
If you launch the task manager, your CPU is at 100% ?
I think I have to optimize the exchange between CPU and GPU. This is also in my task list.
A good challenge would be to reach 1GK/s on your config Cheesy

Topic: VanitySearch (Yet another address prefix finder) - page 60. (Read 32072 times)