VanitySearch (Yet another address prefix finder)

[Jean_Luc]

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.

[1714042652]

1714042652

[1714042652]

1714042652

[1714042652]

1714042652

[1714042652]

1714042652

[1714042652]

1714042652

[1714042652]

1714042652

[arulbero]

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://bitcointalk.org/index.php?topic=4453897.msg49793258#msg49793258

in particular:

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

[Jean_Luc]

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.

[stivensons]

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

[stivensons]

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://bitcointalk.org/index.php?topic=4453897.msg49793258#msg49793258

in particular:

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

[Jean_Luc]

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.

[stivensons]

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.

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

[stivensons]

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://bitcointalk.org/index.php?topic=4453897.msg49793258#msg49793258

in particular:

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]

[Jean_Luc]

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.

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.

[arulbero]

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

[stivensons]

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

I mean, for example, to set a range for creating an address in a specific range, I want to create an address in 2 ^ 135 - 2 ^ 136 with a specific mask

[Jean_Luc]

I mean, for example, to set a range for creating an address in a specific range, I want to create an address in 2 ^ 135 - 2 ^ 136 with a specific mask

For VanitySearch, I don't really see the interest of this options and it is a good way to see its funds stolen.
May be it can be useful for bitcrak, if you have detected a failure in a wallet pseudo random generator and you know more or less subspaces of generated key.

[OgNasty]

Can VanitySearch look for more than 1 vanity prefix at a time?

[Jean_Luc]

Can VanitySearch look for more than 1 vanity prefix at a time?

Not yet, I will add this in the next release.
As I said, in a previous post, this feature need a refurbishment of the code.
This refurbishment should also allow an optimization of data transfer between GPU and CPU.

Some news:
After very interesting exchanges with arulbero (by PM), we should see significant performance increase in the next release.

[Jean_Luc]

Hello,

I published a new release (1.6).
No new feature, just performance increase (16% GPU, 50% CPU on my hardware).
The performance increase are mainly due to a best ECC calculations ( many thanks to arulbero )
It affects less the GPU because the GPU has no SIMD instructions to speed up the SHA, so the resource goes mainly to it and much less to ECC calculations.

Next Step:
- Add support for multi prefix search and (-i input.txt)
- Optimize CPU/GPU exchange
- Add missing ECC optimizations (some symmetries and endomorphism)
- Add support for GPU funnel shift that should speed up SHA (but I need to find a board with compute capability >3.5, mine is 3.0).

Thanks for testing it

I almost reached the same performance with my CPU alone (Intel Core i7-4770 3.4GHz) than oclvanitygen with my GPU (GTX 645)
but still 10 days of calculation to reach to prefix I want.

[Lolo54]

Tested Jean_Luc nice, on my old gear the improvement is 65% CPU .... for the GPU I can not enjoy it for the moment CUDA 8.0
Start Wed Mar  6 15:55:46 2019
Search: 1testr
Difficulty: 15318045009
Base Key:5D48B5A686EF3CCD828F2B23DBD365564D4193F3DC5EA98EB696641F8C8CFC17
Number of CPU thread: 4
3.016 MK/s (GPU 0.000 MK/s) (2^28.15) [P 1.92%][50.00% in 00:57:02][0]

[arulbero]

I published a new release (1.6).
No new feature, just performance increase (16% GPU, 50% CPU on my hardware).
The performance increase are mainly due to a best ECC calculations ( many thanks to arulbero )
It affects less the GPU because the GPU has no SIMD instructions to speed up the SHA, so the resource goes mainly to it and much less to ECC calculations.

On my pc:

VanitySearch -stop -u -t 1 1tryme --> 1,2 MKeys/s

my ecc library  --> 2,0 MKeys/s  (17 M Public keys/s)

Now (Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz):
 

VanitySearch -stop -u -t 1 1tryme --> 2,078 MKeys/s

VanitySearch -stop  -t 1 1tryme --> 2,771 MKeys/s

VanitySearch -stop  -t 8 1tryme --> 10,758 MKeys/s

EDIT:


Search: 1Happpppy
Difficulty: 51529903411245
Base Key:89D6DCD4B58447BB26F7FAFC99C12612B4ADB97E8A0CC5133253E3CB74B6734E
Number of CPU thread: 6
GPU: GPU #0 Quadro M2200 (8x128 cores) Grid(64x128)
98.840 MK/s (GPU 88.068 MK/s) (2^31.39) [P 0.01%][50.00% in 4.3d]


For a comparison with Bitcrack:

./cuBitCrack  -b 128 -t 256 -p 256 1FshYsUh3mqgsG29XpZ23eLjWV8Ur3VwH
Quadro M2200     568/4038MB | 1 target 61.75 MKey/s (807,927,808 total) [00:00:21]


 

[stivensons]

Hello,

I published a new release (1.6).
No new feature, just performance increase (16% GPU, 50% CPU on my hardware).
The performance increase are mainly due to a best ECC calculations ( many thanks to arulbero )
It affects less the GPU because the GPU has no SIMD instructions to speed up the SHA, so the resource goes mainly to it and much less to ECC calculations.

Next Step:
- Add support for multi prefix search and (-i input.txt)
- Optimize CPU/GPU exchange
- Add missing ECC optimizations (some symmetries and endomorphism)
- Add support for GPU funnel shift that should speed up SHA (but I need to find a board with compute capability >3.5, mine is 3.0).

Thanks for testing it

I almost reached the same performance with my CPU alone (Intel Core i7-4770 3.4GHz) than oclvanitygen with my GPU (GTX 645)
but still 10 days of calculation to reach to prefix I want.

good speed increase 

Code:

G:\vanitysearch>vanitysearch -stop -t 0 -gpu -gpuId 0,1,2,3,4,5,6 1Testtttt
Start Thu Mar  7 22:17:16 2019
Search: 1Testtttt
Difficulty: 2988734397852221
Base Key:AC4A942372FF30E640421B959E6BE9EA97DC872B03041A59F73D9C19A5902F7B
Number of CPU thread: 0
GPU: GPU #2 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #1 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)y]
GPU: GPU #6 GeForce GTX 1060 3GB (9x128 cores) Grid(72x128)
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)
1043.526 MK/s (GPU 1043.526 MK/s) (2^34.80) [P 0.00%][50.00% in 23.1d]

[SlarkBoy]

Nice speed 

Code:

C:\VanitySearch>VanitySearch.exe -stop -gpu -gpuId 0,1,2,3 1SLarkBoyKEK
Start Sun Mar 10 22:26:19 2019
Difficulty: 583137945833742401536Search: 1SLarkBoyKEK
Base Key:7098934A348028B578A730116289AC3A6BB56AFF8664117F5CE69920A360A4E9
Number of CPU thread: 31
GPU: GPU #0 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128)
GPU: GPU #3 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128)
GPU: GPU #2 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128)
GPU: GPU #1 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128)
7260.449 MK/s (GPU 7212.931 MK/s) (2^36.56) [P 0.00%][50.00% in 1765.33y][0]


C:\VanitySearch>VanitySearch.exe -stop -gpu -gpuId 0,1 1SLarkBoyKEK
Start Mon Mar 11 02:56:57 2019
Difficulty: 583137945833742401536Search: 1SLarkBoyKEK
Base Key:B97C76053D7951498A9122DEBC2951EB803A51C309326D1C321DF35DF5FB79EE
Number of CPU thread: 19
GPU: GPU #0 GeForce GTX 1080 Ti (28x128 cores) Grid(224x128)
GPU: GPU #1 GeForce GTX 1080 Ti (28x128 cores) Grid(224x128)
1293.435 MK/s (GPU 1255.415 MK/s) (2^32.96) [P 0.00%][50.00% in 9909.36y][0]

[Lolo54]

Nice speed  

Code:

C:\VanitySearch>VanitySearch.exe -stop -gpu -gpuId 0,1,2,3 1SLarkBoyKEK
Start Sun Mar 10 22:26:19 2019
Difficulty: 583137945833742401536Search: 1SLarkBoyKEK
Base Key:7098934A348028B578A730116289AC3A6BB56AFF8664117F5CE69920A360A4E9
Number of CPU thread: 31
GPU: GPU #0 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128)
GPU: GPU #3 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128)
GPU: GPU #2 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128)
GPU: GPU #1 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128)
7260.449 MK/s (GPU 7212.931 MK/s) (2^36.56) [P 0.00%][50.00% in 1765.33y][0]


C:\VanitySearch>VanitySearch.exe -stop -gpu -gpuId 0,1 1SLarkBoyKEK
Start Mon Mar 11 02:56:57 2019
Difficulty: 583137945833742401536Search: 1SLarkBoyKEK
Base Key:B97C76053D7951498A9122DEBC2951EB803A51C309326D1C321DF35DF5FB79EE
Number of CPU thread: 19
GPU: GPU #0 GeForce GTX 1080 Ti (28x128 cores) Grid(224x128)
GPU: GPU #1 GeForce GTX 1080 Ti (28x128 cores) Grid(224x128)
1293.435 MK/s (GPU 1255.415 MK/s) (2^32.96) [P 0.00%][50.00% in 9909.36y][0]

ah yes impressive speed but the tesla config is crazy   ! it also allows to see that despite a software optimizes and the top of the technology it is still not possible to obtain a vanity address of 12 patterns or more in a reasonable delay alas  
it can already have good fun to create beautiful addresses of vanity if you do not climb so high in the number of pattern remaining within a reasonable time ...