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

Jean_Luc

sr. member

Activity: 462

Merit: 701

Quote from: ?? on ??

I don't, you do, and if you want people to use it, you are going to have to do something.

The way pbkdf2_hmac_sha512 is implemented is safe, long passwords (>128 characters for SHA512) are truncated to 128.
No change needed here unless someone finds a trap of really wants password longer than 128 char.

Quote from: ?? on ??

Hi,

I just remembered a few features of "profanity" used for ETH-addresses:

Code:

--letters Score on letters anywhere in hash.
--numbers Score on numbers anywhere in hash.
--mirror Score on mirroring from center.

Source: https://github.com/johguse/profanity

Would it be possible to implement those "modes" into VanitySearch?

Hi,
Yes it could be done but I still have work with fast base58 encoding and I will be off the next week.

Jean_Luc

sr. member

Activity: 462

Merit: 701

Why do you want to implement in a different way ?

Jean_Luc

sr. member

Activity: 462

Merit: 701

and ?
did you manage to exploit something ?

Jean_Luc

sr. member

Activity: 462

Merit: 701

Quote from: stortz on May 01, 2019, 03:15:35 PM

also, Is it possible to add this address to a specific electrum wallet? I don't think it's possible without creating a new wallet, correct?

You can use Wallet->Private keys>Import to import address(es) (giving the corresponding private key(s)) in the current opened wallet.
I'm using Electrum 3.3.4.

Jean_Luc

sr. member

Activity: 462

Merit: 701

Thanks to all for these performance reports. I appreciate it

Note that the Tesla V100 result was with an old release.
If i compare to the result of the 1080 ti posted in the same SlarkBoy's post, 1255M/Ks for 2 1080Ti, (627MK/s per board), and the result from here (1001 MK/s) we may expect a 60% speed increase on the Tesla with last VanitySearch release (~2800MK/s).

Lolo54

member

Activity: 117

Merit: 32

Quote

I underclock my cards so I'm not sure I should post the speeds, but I can say that the 2070 outperforms the 1080ti and even the liquid cooled model by a little bit, and uses significantly less power while doing so. The 2070 is a great buy for this purpose in my opinion.

Exact OgNasty the RTX 2070 is the best performance / price compromise .... just look at the TESLA V100 $ 10000 scores for 50% extra speed or a 2080 TI twice as expensive as a 2070 but for a result that is not doubled in terms of speed ... if in addition we take into account the power consumption the RTX 2070 is very correct

stortz

jr. member

Activity: 40

Merit: 15

Quote from: Jean_Luc on March 18, 2019, 01:53:09 AM

Hello,

Quote from: stortz on March 17, 2019, 05:43:52 PM

it ran, but just closed after finding it
did it generate the private keys into a file?
I am confused

To output the key in a file, use the -o option.

Code:

VanitySearch -stop -gpu -o key.txt 1stortz

Many thanks stivensons for the report

this setup worked
perhaps you should make it as a default setting

Code:

-stop -gpu -o key.txt 1

this is the code I added to the shortcut to the program, as you pointed. It worked perfectly.

edit:
also, Is it possible to add this address to a specific electrum wallet? I don't think it's possible without creating a new wallet, correct?

OgNasty

donator

Activity: 4760

Merit: 4323

Leading Crypto Sports Betting & Casino Platform

Quote from: DaveF on May 01, 2019, 01:55:58 PM

Quote from: escope on May 01, 2019, 01:42:02 PM

Quote from: Jean_Luc on May 01, 2019, 01:10:18 AM

Wildcard search is between 4 and 5 times slower than classic search for known prefixes. I reach ~40MK/s with my 1050 Ti and ~4MK/s with my i7-4770.
It is due to the fact that I have to compute full address each time and it requires 2 SHA for the checksum and a base58 encoding. For the CPU release, I implemented SSE checksum and I will try to implement SSE Base58 encoding using Barret's reduction (for computing div and mod 58).

Thank you very very much! I am really looking forward to a new commit.

Quote from: DaveF on April 29, 2019, 09:27:50 AM

Has anyone put together (or started to put together) a list of CPUs / Video Cards & the speed you can get out of them.
Anything else?

GPU: GPU #0 GeForce GTX 750 (4x128 cores) Grid(32x128)
104.960 MK/s (GPU 94.405 MK/s) (2^32.12)

Quote from: DaveF on April 29, 2019, 09:27:50 AM

GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
1535.880 MK/s (GPU 1470.257 MK/s)

Oh my take my money I want buy that now

1) added
2) Amazon. The source of all things: https://amzn.to/2Li0UsI

-Dave

I underclock my cards so I'm not sure I should post the speeds, but I can say that the 2070 outperforms the 1080ti and even the liquid cooled model by a little bit, and uses significantly less power while doing so. The 2070 is a great buy for this purpose in my opinion.

DaveF

legendary

Activity: 3500

Merit: 6320

Crypto Swap Exchange

Quote from: escope on May 01, 2019, 01:42:02 PM

Quote from: Jean_Luc on May 01, 2019, 01:10:18 AM

Wildcard search is between 4 and 5 times slower than classic search for known prefixes. I reach ~40MK/s with my 1050 Ti and ~4MK/s with my i7-4770.
It is due to the fact that I have to compute full address each time and it requires 2 SHA for the checksum and a base58 encoding. For the CPU release, I implemented SSE checksum and I will try to implement SSE Base58 encoding using Barret's reduction (for computing div and mod 58).

Thank you very very much! I am really looking forward to a new commit.

Quote from: DaveF on April 29, 2019, 09:27:50 AM

Has anyone put together (or started to put together) a list of CPUs / Video Cards & the speed you can get out of them.
Anything else?

GPU: GPU #0 GeForce GTX 750 (4x128 cores) Grid(32x128)
104.960 MK/s (GPU 94.405 MK/s) (2^32.12)

Quote from: DaveF on April 29, 2019, 09:27:50 AM

GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
1535.880 MK/s (GPU 1470.257 MK/s)

Oh my take my money I want buy that now

1) added
2) Amazon. The source of all things: https://amzn.to/2Li0UsI

-Dave

escope

newbie

Activity: 13

Merit: 24

Quote from: Jean_Luc on May 01, 2019, 01:10:18 AM

Wildcard search is between 4 and 5 times slower than classic search for known prefixes. I reach ~40MK/s with my 1050 Ti and ~4MK/s with my i7-4770.
It is due to the fact that I have to compute full address each time and it requires 2 SHA for the checksum and a base58 encoding. For the CPU release, I implemented SSE checksum and I will try to implement SSE Base58 encoding using Barret's reduction (for computing div and mod 58).

Thank you very very much! I am really looking forward to a new commit.

Quote from: DaveF on April 29, 2019, 09:27:50 AM

Has anyone put together (or started to put together) a list of CPUs / Video Cards & the speed you can get out of them.
Anything else?

GPU: GPU #0 GeForce GTX 750 (4x128 cores) Grid(32x128)
104.960 MK/s (GPU 94.405 MK/s) (2^32.12)

Quote from: DaveF on April 29, 2019, 09:27:50 AM

GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
1535.880 MK/s (GPU 1470.257 MK/s)

Oh my take my money I want buy that now

Lolo54

member

Activity: 117

Merit: 32

Bonjour
You can add it https://bitcointalksearch.org/topic/m.50108268

Code:

C: \ VanitySearch> VanitySearch.exe -stop -gpu -gpuId 0,1,2,3 1SLarkBoyKEK
Début Dim 10 mars 2019 22:26:19
Difficulté: 583137945833742401536Search: 1SLarkBoyKEK
base clé: 7098934A348028B578A730116289AC3A6BB56AFF8664117F5CE69920A360A4E9
Nombre de thread CPU: 31
GPU: GPU # 0 Tesla V100-SXM2-16GB (80x64 noyaux) Grille (640x128)
GPU: GPU n ° 3 Tesla V100-SXM2-16GB (80x64 noyaux) Grille (640x128)
GPU: GPU n ° 2 Tesla V100-SXM2-16GB (80x64 cœurs) Grille (640x128)
GPU: GPU n ° 1 Tesla V100-SXM2-16GB (80x64 cœurs) Grille (640x128)
7260.449 MK / s (GPU 7212.931 MK / s) (2 ^ 36.56) [P 0.00%] [50.00% en 1765.33y ] [0]

Jean_Luc

sr. member

Activity: 462

Merit: 701

Many thanks for your report Dave Wink

Some news:
Wildcard search is between 4 and 5 times slower than classic search for known prefixes. I reach ~40MK/s with my 1050 Ti and ~4MK/s with my i7-4770.
It is due to the fact that I have to compute full address each time and it requires 2 SHA for the checksum and a base58 encoding. For the CPU release, I implemented SSE checksum and I will try to implement SSE Base58 encoding using Barret's reduction (for computing div and mod 58).

DaveF

legendary

Activity: 3500

Merit: 6320

Crypto Swap Exchange

Quote from: DarkStar_ on April 30, 2019, 05:06:29 PM

Quote from: DaveF on April 29, 2019, 09:27:50 AM

GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
1535.880 MK/s (GPU 1470.257 MK/s)

Anything else?

GPU: GPU #0 GeForce GTX 1060 3GB (9x128 cores) Grid(72x128)
321.929 MK/s (GPU 321.929 MK/s)

I updated my original post.
https://bitcointalksearch.org/topic/m.50823897

I am going to do my best to keep it updated as more info comes in.
As I add cards I will post the date added so there will be some form of tracking.

-Dave

DarkStar_

legendary

Activity: 2772

Merit: 3284

Quote from: DaveF on April 29, 2019, 09:27:50 AM

GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
1535.880 MK/s (GPU 1470.257 MK/s)

Anything else?

GPU: GPU #0 GeForce GTX 1060 3GB (9x128 cores) Grid(72x128)
321.929 MK/s (GPU 321.929 MK/s)

Coinettin

newbie

Activity: 2

Merit: 0

Hi Jean_Luc,

Thank you for your work. It's a huge step for generating vanity addresses. I appreciate it.

DaveF

legendary

Activity: 3500

Merit: 6320

Crypto Swap Exchange

Has anyone put together (or started to put together) a list of CPUs / Video Cards & the speed you can get out of them.
I know it's a newer project and Jean_Luc is working VERY VERY hard on it so getting accurate numbers is going to be a moving target. But for now all we can do is look through the thread and see who is running what to get a general idea.
So far I have pulled from this thread:

GPU: GPU #0 GeForce GTX 1080 Ti (28x128 cores) Grid(224x128)
914.418 MK/s (GPU 896.216 MK/s)

GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
220.180 MK/s (GPU 220.180 MK/s)

GPU: GPU #0 GeForce GT 520M (1x48 cores) Grid(8x128)
10.233 MK/s (GPU 7.026 MK/s)

GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
1535.880 MK/s (GPU 1470.257 MK/s)

Added 30-April-2019

GPU: GPU #0 GeForce GTX 1060 3GB (9x128 cores) Grid(72x128)
321.929 MK/s (GPU 321.929 MK/s)

GPU: GPU #0 GeForce GTX 1080 (20x128 cores) Grid(160x128)
672.062 MK/s (GPU 672.062 MK/s)

Added 1-May-2019

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)
So 7260 / 4 = 1815 MK/s

GPU: GPU #0 GeForce GTX 750 (4x128 cores) Grid(32x128)
104.960 MK/s (GPU 94.405 MK/s) (2^32.12)

Added 3-May-2019
i7-7700K CPU Number of CPU thread: 8
22.092 MK/s (GPU 0.000 MK/s)

With -t 7
Number of CPU thread: 7
21.609 MK/s

Added 8-May-2019

EVGA RTX 2080 XC ULTRA
1427.967 MK/s (GPU 1424.946 MK/s)

Added 23-May-2019

GPU: GPU #0 GeForce GTX 1660 Ti
961.319 MK/s (GPU 961.319 MK/s)

GPU: GPU #0 GeForce RTX 2080 Ti (68x64 cores) Grid(544x128)
GPU: GPU #1 GeForce RTX 2080 Ti (68x64 cores) Grid(544x128)
5128.213 MK/s (GPU 5128.213 MK/s)
So 5128 / 2 = 2564 MK/s

Added 8-June-2019

GPU: GPU #0 GeForce GTX 960M (5x128 cores) Grid(40x128)
117.802 MK/s (GPU 117.802 MK/s)

Added 23-July-2019

GPU: GPU #0 GeForce GTX 1660 (22x64 cores) Grid(176x128)
839.061 MK/s (GPU 839.061 MK/s)

Added 25-July-2019

GPU: GPU #0 GeForce GTX 1650 (14x64 cores) Grid(112x128)
511.906 MK/s (GPU 511.906 MK/s) (2^36.97)

Added 21-Nov-2019

GPU: GPU #0 GeForce GTX 970 (13x128 cores) Grid(104x128)
360.322 MK/s (GPU 331.442 MK/s) (2^32.77)

Added 25-Nov-2019

GPU: GPU #0 GeForce GTX 980 (16x128 cores) Grid(128x128)
375.384 MK/s (GPU 375.384 MK/s)

GPU: GPU #0 GeForce RTX 2060 SUPER (34x64 cores) Grid(272x256)
[1361.71 Mkey/s][GPU 1361.71 Mkey/s]

GPU: GPU #0 GeForce RTX 2080 SUPER (48x64 cores) Grid(384x256)
[2001.52 Mkey/s][GPU 2001.52 Mkey/s]

Anything else?

-Dave

Last updated 25-Nov-2019.

Jean_Luc

sr. member

Activity: 462

Merit: 701

Quote from: RobertPaulig on April 27, 2019, 01:04:00 PM

Hope to see all upper-case or all lower-case search. Also hope to see regexp search for finding whatever want.

I am not an expert but I guess there are some algos for base64 encoding/decoding on GPU:
https://www.codeproject.com/Articles/276993/Base64-Encoding-on-a-GPU
https://lemire.me/blog/2018/01/17/ridiculously-fast-base64-encoding-and-decoding/

Also there are several fast GPU regexp:
https://madhumithasridhara.github.io/QuickMatch/

Thanks for the link, I will have a look at this.
Adding a way to generate only upper or lower case is easy except for the difficulty calculation.

Quote from: RobertPaulig on April 27, 2019, 01:04:00 PM

Jean_Luc
Here's your piece of code for generating pseudorandom numbers.
...

Thanks for the info but as written in the readme it is better to use a seed for generating a safe base key and obviously to run it on a machine where you are alone. The PNRG is not used at all by default, it is enabled only if you want to use the -r option which I do not recommend (I will add a UNSAFE message in the command line usage infos for the - r option).

escope

newbie

Activity: 13

Merit: 24

Quote from: OgNasty on April 27, 2019, 08:46:54 AM

I don’t believe anything is stopping you from doing this now.

I can. But I guess it is possible by slow CPU regexp in slow Vanitygen only.
Please if you know something lmk about that

RobertPaulig

newbie

Activity: 7

Merit: 1

Jean_Luc
Here's your piece of code for generating pseudorandom numbers.
/* Knuth's PRNG as used in the Mersenne Twister reference implementation */

Code:

for (pos=0; pos  {
   state->key[pos] = seed;
   seed = (1812433253UL * (seed ^ (seed >> 30)) + pos + 1) & 0xffffffffUL;
  }

  state->pos = RK_STATE_LEN;
}

This is a quote from the Wiki

Quote

Is not cryptographically secure, unless the CryptMT variant (discussed below) is used. The reason is that observing a sufficient number of iterations (624 in the case of MT19937, since this is the size of the state vector from which future iterations are produced) allows one to predict all future iterations.

https://en.wikipedia.org/wiki/Mersenne_Twister

OgNasty

donator

Activity: 4760

Merit: 4323

Leading Crypto Sports Betting & Casino Platform

Quote from: escope on April 27, 2019, 06:10:05 AM

Hope to see all upper-case or all lower-case search.

I don’t believe anything is stopping you from doing this now.

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