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

Jean_Luc

sr. member

Activity: 462

Merit: 701

Thanks for the test Wink

You didn't reconstruct the final private key with the good key, you have to use the first generated private key (for -rp) which is the one which should be kept secret by the requester of the prefix.

Code:

C:\C++\VanitySearch\x64\Release>VanitySearch.exe -rp KxFuiDGdGLoMKGnVfZ4x4sXLs6GPkp2a7teATCyLV65XKxt65s35 keyinfo.txt

Pub Addr: 1Laure3pgFU6v1EdqT15B9SQ612tTBS4WE
Priv (WIF): p2pkh:L1PqadvjgQJ7XXQZ8c8hf7j8RRu7F7J8Fws1t3Zasd7qiXjwyLwT
Priv (HEX): 0x7C8F3FC0B693F368219BD4F7DCE82C10FEBFA2F9CBB1FD55EF5B68DE24411C6C

Lolo54

member

Activity: 131

Merit: 32

Hello Jean_Luc

always a good speed for the basic command (identical)
I tried to be as complete as possible for the test

Code:

VanitySearchCUDA10.113.exe -gpu 1Testbtc
VanitySearch v1.13
Difficulty: 51529903411245
Search: 1Testbtc [Compressed]
Start Thu Apr 18 13:11:49 2019
Base Key: DFDABB80A765A04F86AF2D673B7CCDD59DED63D8DECBC52CA9907B2EDA16FE4B
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
1321.297 MK/s (GPU 1294.818 MK/s) (2^35.81) [P 0.12%][50.00% in 07:29:15][0]

for new functions

Code:

VanitySearchCUDA10.113.exe -gpu -s "laurent123456" -kp
Priv : KxFuiDGdGLoMKGnVfZ4x4sXLs6GPkp2a7teATCyLV65XKxt65s35
Pub  : 026F6F0A6D845EA109C837976BC06040F4C1DA98881B7E165C9431FE1A7198AAD8

Code:

VanitySearchCUDA10.113.exe -gpu -stop -sp 026F6F0A6D845EA109C837976BC06040F4C1DA98881B7E165C9431FE1A7198AAD8 -o keyinfo.txt 1Laure
VanitySearch v1.13
Difficulty: 264104224
Search: 1Laure [Compressed With Public Key]
Start Thu Apr 18 14:19:08 2019
Base Key: BEBF153068FCE331CCE0CAD96E7A28C257FCFDA27106E406615425D394FD3A5A
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)

go to the keyinfo.txt file the key pair is generated

Code:

Pub Addr: 1LaureDAydQYaq9MCAmdtSMTdVEqwCYGNu
PartialPriv: L3CUQDbWbAAN1nrpC7VtkWUcmGHvfrwqbQXyzX7R4Y85Kt1yM9yw

we can also remove the command -stop so several key pair will be generated just as well and choose the desired one

Code:

VanitySearchCUDA10.113.exe -gpu -sp 026F6F0A6D845EA109C837976BC06040F4C1DA98881B7E165C9431FE1A7198AAD8 -o keyinfo.txt 1Laure
VanitySearch v1.13
Difficulty: 264104224
Search: 1Laure [Compressed With Public Key]
Start Thu Apr 18 14:23:32 2019
Base Key: 69CB978C32F80D552D1974EF9C602DB3AC0429CF69FA6E7449AF467E4A673D2E
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
1389.539 MK/s (GPU 1356.604 MK/s) (2^32.96) [P 100.00%][99.00% in 00:00:00][32]

generated keyinfo.txt file

Code:

Pub Addr: 1Laure8jVGTY9PwSmHirbMLiWwTCnfyUTA
PartialPriv: L2Fgvp4tSRbnef3q1xN3tdUKtXL7xV3FLsUhkUaK6rSbvgZeJfJo

Pub Addr: 1LaurecbFFeL1U4WWZ5975ygCimkU5LtDw
PartialPriv: KwrrMpy91Sgxf5bRSapMMDdM28e6xZk3DJD2eWSnG9t8DRagK5cQ

Pub Addr: 1Laureaz3vp1QjQHPgC6gfqYEJC2do5DeU
PartialPriv: L2Fgvp4tSRbnef3q1xN3tdUKtXL7y2C51CjCQEB2CnkmVGPdN6JS

Pub Addr: 1LaurebqudrAdzGoCcdTehayF6YBPecfTy
PartialPriv: L2P4pvzHr1YyGE5y2yZ5BmH8pe4vVtQaGhGUfNcnVt6eaQqtW3ek

Pub Addr: 1LauresDqY9bMsYXYPAjg8or8ZnBkcbbhy
PartialPriv: L2dvi9DnFyRSsgaMPxGfx3KaaR3EkWgXiwGZYtG3RExGDkrWr65J

Pub Addr: 1LaureGCSLrGBp7z3QmZnxxuWUKxUyd87K
PartialPriv: Kz1LpDaW169L9W53UCajYexviSLgCL7vKj5eRvPNrixxeuwWN7LB

Pub Addr: 1Laurecjn2vCiVQJK9hvRdDQactAaSEUT7
PartialPriv: KxHvnxoAer6GZSN4Jd78jEomCCE6rVVTdS8cTVynNjAXL3GSgRqN

Pub Addr: 1LaureZeYBTtN8BN9Kh56dQUyVHV9uthSs
PartialPriv: KyBrP3Acsp6sBiLfyQd7sCbdkHh2LusLF36xE1c4ZXTbJWNxpoHW

Pub Addr: 1LauresFskwLLuJcao1cutuu8F9WjPe1jY
PartialPriv: Kxq44WvEBmSxdX8EH5x4uJZ55Ym47zPtXSuGMgCoRTFdQsk7Upfe

Pub Addr: 1LaureSMMPCUTUcmdMEwqSq5j9NeoGjGdp
PartialPriv: KzQXt3mjoMybfoJbbcUsPaZyLV4jY3kwcAPdViFNHEDZns21YpcD

Pub Addr: 1Laurezhs8jKTkyLLGMBQhawDwbF9MyE2V
PartialPriv: L1Qcgc7EHidrCNTC6jAJvwaFSBgBFc4kzQJqZhr1SoggkFqjCCQD

Pub Addr: 1Laure1ogSdn7BwN2jcoyRDUEhofWTLSCE
PartialPriv: KzmN1fYJZ5rYnLMb7X5Ti6qW4u2FigYhDqp3AXMBDsskwdWjyjnL

Pub Addr: 1LaurecRE9STrJLeuJ6274HJP5LWBMnXLg
PartialPriv: L2Fgvp4tSRbnef3q1xN3tdUKtXL7xUBrWSrM3zgXjvJ3UMZZqriW

Pub Addr: 1LaureJM3Lq3UPUDygkpRSNMX7JFz2mBYC
PartialPriv: L2Fgvp4tSRbnef3q1xN3tdUKtXL7xPLS7RjtBjbwKdMUU2MXbULe

Pub Addr: 1Laure28fPTiqh1hX5V3o4TTTYtRog7aHA
PartialPriv: KzmN1fYJZ5rYnLMb7X5Ti6qW4u2FiSULfRbGctumFBNxwjemVq4D

Pub Addr: 1LaureTvZgrj8WJTEjjLdiVGpRWeEjoVRc
PartialPriv: KzMgFNNrxeSGiPMuEbBfFQNLXysvXzsAdFKKBbVxWoPTDRobNPZd

Pub Addr: 1Laure6kksCGnCksLeKYiLUGnBrKj3gEVS
PartialPriv: L2Fgvp4tSRbnef3q1xN3tdUKtXL7xmkyDQZigZJNyVrhJNG9mVUT

Pub Addr: 1LaureK5uaDeKPBwU3pnLPhwmCzWah8FLm
PartialPriv: L1FGpjDXuontforrEo9nK9L2KCn5bctbPPZpLBG58WpHYsBxEspD

we can also add the -r 10000 or 5000000 command to generate

Code:

C:\Users\Laurent\Documents\Bitcoin\VanitySearchCUDA10.113.exe -gpu -r 1000000 -sp 026F6F0A6D845EA109C837976BC06040F4C1DA98881B7E165C9431FE1A7198AAD8 -o keyinfo.txt 1Laure
VanitySearch v1.13
Difficulty: 264104224
Search: 1Laure [Compressed With Public Key]
Start Thu Apr 18 13:40:54 2019
Base Key: Randomly changed every 1000000 Mkeys
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
1341.496 MK/s (GPU 1311.409 MK/s) (2^33.65) [P 100.00%][99.00% in 00:00:00][52]

The manipulation works perfectly with the 3 types of addresses in 1Laure in 3AbV1 and with bc1q

Code:

VanitySearchCUDA10.113.exe -gpu -stop -sp 026F6F0A6D845EA109C837976BC06040F4C1DA98881B7E165C9431FE1A7198AAD8 -o keyinfo.txt bc1qlaure
VanitySearch v1.13
Difficulty: 33554432
Search: bc1qlaure [Compressed With Public Key]
Start Thu Apr 18 14:30:55 2019
Base Key: 2D94FBC6143DC091781AE96773F1089260EE575ABE467906BA01AA01EE1931A9
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)

fiLE keyinfo.txt

Code:

Pub Addr: bc1qlaure4pu9nl3rnnec8qmxqc42kcndwhc6gne3q
PartialPriv: L4GjeJDYKNEZzRZw4qEgK1LUG5sHigygFLbcFU3ViwxNJd9Q9dq9

I have this error message at the end to rebuild the final private key using the partial private key

Code:

VanitySearchCUDA10.113.exe -rp KzpaHTHmod39eYQZ7jMwQUNSSZrQeZfEMpPoVXNRETnWg5tejVnR keyinfo.txt
Unable to reconstruct final key from partialkey line 0
 Addr: 1Laure3pgFU6v1EdqT15B9SQ612tTBS4WE
 PartKey: KzpaHTHmod39eYQZ7jMwQUNSSZrQeZfEMpPoVXNRETnWg5tejVnR

otherwise the program is still easy to use, all commands run perfectly except for this moment this little bug in the end or so I did a wrong handling Huh

Code:

VanitySearchCUDA10.113.exe -gpu -s "laurent123456" -kp
Priv : KxFuiDGdGLoMKGnVfZ4x4sXLs6GPkp2a7teATCyLV65XKxt65s35
Pub  : 026F6F0A6D845EA109C837976BC06040F4C1DA98881B7E165C9431FE1A7198AAD8

VanitySearchCUDA10.113.exe -gpu -stop -sp 026F6F0A6D845EA109C837976BC06040F4C1DA98881B7E165C9431FE1A7198AAD8 -o keyinfo.txt 1Laure
VanitySearch v1.13
Difficulty: 264104224
Search: 1Laure [Compressed With Public Key]
Start Thu Apr 18 14:50:31 2019
Base Key: 41C8D10E5CBCB278109D8CFDFD4508AF2D6787F34AF7EE5FD9F5AA243586F5DF
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)

Pub Addr: 1Laure3pgFU6v1EdqT15B9SQ612tTBS4WE
PartialPriv: KzpaHTHmod39eYQZ7jMwQUNSSZrQeZfEMpPoVXNRETnWg5tejVnR

VanitySearchCUDA10.113.exe -rp KzpaHTHmod39eYQZ7jMwQUNSSZrQeZfEMpPoVXNRETnWg5tejVnR keyinfo.txt
Unable to reconstruct final key from partialkey line 0
 Addr: 1Laure3pgFU6v1EdqT15B9SQ612tTBS4WE
 PartKey: KzpaHTHmod39eYQZ7jMwQUNSSZrQeZfEMpPoVXNRETnWg5tejVnR

Why this message " Unable to reconstruct final key from partialkey line 0 "

Jean_Luc

sr. member

Activity: 462

Merit: 701

Hello,

The new release 1.13 is available for download. It supports split-key.

More info in the readme:
https://github.com/JeanLucPons/VanitySearch/blob/master/README.md#generate-a-vanity-address-for-a-third-party-using-split-key-vanity-address

Thanks to test it Wink

Jean_Luc

sr. member

Activity: 462

Merit: 701

In fact i already added the feature. It is committed on GutHub but not yet released (there is still a bug, from time to time the address cannot be reconstructed)
Few word for those who want to test from the source:

Case: Alice want a nice prefix but does not have CPU power available, Bob has the power but cannot know the private key of Alice.

Alice generate a key pair then she sends the public key and the wanted prefix to Bob:

Code:

C:\C++\VanitySearch\x64\Release>VanitySearch.exe -s "AliceSeed" -kp
Priv : L4U2Ca2wyo721n7j9nXM9oUWLzCj19nKtLeJuTXZP3AohW9wVgrH
Pub  : 03FC71AE1E88F143E8B05326FC9A83F4DAB93EA88FFEACD37465ED843FCC75AA81

Bob runs VanitySeacrh using the Alice's public key and send back the keyinfo.txt file to Alice:

Code:

C:\C++\VanitySearch\x64\Release>VanitySearchCUDA8.exe -sp 03FC71AE1E88F143E8B05326FC9A83F4DAB93EA88FFEACD37465ED843FCC75AA81 -gpu -o keyinfo.txt -stop 1ALice
VanitySearch v1.12
Difficulty: 264104224
Search: 1ALice [Compressed With Public Key]
Start Wed Apr 17 20:03:19 2019
Base Key: 8B456380CE20C7CA2ACA52A6B17EB53B98C789AD8215F09D1D478260492E7DD3
Number of CPU thread: 3
GPU: GPU #0 GeForce GTX 645 (3x192 cores) Grid(24x128)
49.429 MK/s (GPU 45.930 MK/s) (2^26.60) [P 31.92%][50.00% in 00:00:01][0]

File keyinfo.txt:

Code:

Pub Addr: 1ALiceQeUJwFKwGYLvZDMfKC1h9XCshLJ7
PartialPriv: L54zKpetuL8rVVvyWRFJG8PdQs4PaPuvP3Rb7G8SXLBVSjLsMx4m

Alice runs VanitySearch using her first generated private key and the Bob's file to get safely the final private key:

Code:

C:\C++\VanitySearch\x64\Release>VanitySearchCUDA8.exe -rp L4U2Ca2wyo721n7j9nXM9oUWLzCj19nKtLeJuTXZP3AohW9wVgrH keyinfo.txt

Pub Addr: 1ALiceQeUJwFKwGYLvZDMfKC1h9XCshLJ7
Priv (WIF): p2pkh:L1kjZP36qVCcp1eXXJE7CfyuWojc1rCTw8Xs8rNrCxM5imLgm4ro
Priv (HEX): 0xD874F31B0B73ED255865FEB210C181589A860ACDB4C374FB4F685DFE2077797F2

Jean_Luc

sr. member

Activity: 462

Merit: 701

Quote from: ?? on ??

Is it possible to generate a split-key address so I can create an address for someone else and they don't have to worry that I know their private-key?
>> https://en.bitcoin.it/wiki/Split-key_vanity_address

Yes this can be done.
I'll add this feature ASAP.
Wink

Jean_Luc

sr. member

Activity: 462

Merit: 701

Quote from: Lolo54 on April 09, 2019, 06:51:45 AM

1BTC is calculated on average according to the mode 10 to 15 times ~~slower~~ faster than 1Tes

Yes this is due to the pivot at 1QLbz7... (The switch from 0x[00]FFFFFFFF.... to 0x[00]0XXXXXXX...).

Thanks for the tests.

Lolo54

member

Activity: 131

Merit: 32

Perfect it works very well no more error message with -b nor with -u with this version 1.12
It's amazing the speed difference according to the prefix to calculate Shocked

1BTC is calculated on average according to the mode 10 to 15 times slower than 1Tes

Code:

VanitySearchCUDA10.112.exe -gpu -b -o vanity.txt 1teS
VanitySearch v1.12
Difficulty: 4553521
Search: 1teS [Compressed or Uncompressed]
Start Tue Apr  9 13:30:55 2019
Base Key:CA0095835D96BB099F1EDF9837E0E41A233C9516D98CDA6989A4D9483DDAE8BE
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
335.488 MK/s (GPU 324.686 MK/s) (2^34.16) [P 100.00%][99.00% in 00:00:00][8525]

Code:

VanitySearchCUDA10.112.exe -gpu -u -o vanity.txt 1BTC
VanitySearch v1.12
Difficulty: 78509
Search: 1BTC [Uncompressed]
Start Tue Apr  9 13:34:17 2019
Base Key:AB1137C6F8BF8074E57D27F2F4882FE84FA334A56CDD2BC8E9F2570F306E9493
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
43.005 MK/s (GPU 28.219 MK/s) (2^31.70) [P 100.00%][99.00% in 00:00:00][41788]

Code:

VanitySearchCUDA10.112.exe -gpu -o vanity.txt 1BTC
VanitySearch v1.12
Difficulty: 78509
Search: 1BTC [Compressed]
Start Tue Apr  9 13:41:11 2019
Base Key:4BED85DFFA3A1B529E95EA2CF90F9BFE80EFDE547B419F8EA5DE9EABBBDF47B0
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
50.841 MK/s (GPU 22.619 MK/s) (2^28.92) [P 100.00%][99.00% in 00:00:00][6105]

Code:

VanitySearchCUDA10.112.exe -gpu -b -o vanity.txt 1BTC
VanitySearch v1.12
Difficulty: 78509
Search: 1BTC [Compressed or Uncompressed]
Start Tue Apr  9 13:53:18 2019
Base Key:FD10E87508883CE873902008A49CA5DC300A83628B3081A3673B25691B70E28C
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
22.865 MK/s (GPU 14.056 MK/s) (2^28.83) [P 100.00%][99.00% in 00:00:00][13889]

Jean_Luc

sr. member

Activity: 462

Merit: 701

Hello,

I fixed the issue. New release 1.12 is ready. I upload the CUDA8 ASAP.
The bug was due to 'negative zero' when a match was found for a symmetric point at index 0 of the group.
In that case the symmetric point noted -0 was interpreted as 0.
It did not affect compressed address because, for that case, the y value of the point does not matter (the parity is handled using an other way).
So I simply applied the same logic for compressed and uncompressed, it should work fine.
It happened with a probability of 1/(GPR_SIZE*2) = 1/2048.

Many thanks to Lolo54 for all the tests.

Jean_Luc

sr. member

Activity: 462

Merit: 701

I manged to reproduce the bug.
It happens only for uncompressed addresses.
It is not link to CUDA 8 or 10.
It happens also if CPU is used alone or if GPU is used alone.
But with a probability of ~1/2000 Sad

I don't know if it is also linked to the prefix length (I don't think) it is difficult to reproduce with longer prefix due to the small probability.

I'll try to debug this...

Lolo54

member

Activity: 131

Merit: 32

Ok jean luc i’m trying tomorrow

Jean_Luc

sr. member

Activity: 462

Merit: 701

No I didn't manage to reproduce the issue. If you use a prefix with 4 char and also starting with a T you can expect that the bug will occurs 58 times less. It could be interesting to test with 'BTC' prefix , for instance, more probable that 'TeS'.

Lolo54

member

Activity: 131

Merit: 32

ok thank you jean luc you answered my question! as for the error for -b or -u with 3 characters (ex 1TesT) did you manage to reproduce the error message and understand where it could come from? This remains very marginal and only involves a small percentage the result even if it was not resolved Wink

Jean_Luc

sr. member

Activity: 462

Merit: 701

Quote from: Lolo54 on April 08, 2019, 09:27:49 AM

Hello
By default it is the dedicated memory of the graphics processor that is used but would it be possible also to force the use of the shared ram? Could this increase the speed of execution or am I wrong?

Hello
VanitySearch uses the GPU global memory to store hash160 that partially match (16bit lookup table) the desired prefixes, the transfer to the RAM of the motherboard is done by the DMA, then the CPU checks all returned hash160 against the complete prefix.
There is no really shared memory that can be accessed directly by the CPU and the GPU (may be it exists on embedded GPU). Transfers are mainly done by the DMA trough the PCIe.
What we usually called "shared memory" in CUDA is a GPU memory shared inside a WARP. A WARP is a block of 32 threads (or more on powerfull GPU) executed on a stream processor.

Lolo54

member

Activity: 131

Merit: 32

Hello
By default it is the dedicated memory of the graphics processor that is used but would it be possible also to force the use of the shared ram? Could this increase the speed of execution or am I wrong?

Lolo54

member

Activity: 131

Merit: 32

the error is also present with -u

Code:

VanitySearch111.exe -gpu -r 1000000 -g 288 -u -o vanity.txt 1TeS
VanitySearch v1.11
Difficulty: 4553521
Search: 1TeS [Uncompressed]
Start Sun Apr  7 12:55:56 2019
Base Key: Randomly changed every 1000000 Mkeys
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)

Warning, wrong private key generated !
  Addr :1TeSe9xEChqvbe92yfARYuL5ZNiuY5iuR
  Check:1NJFrr7R8SKcZvnbRFc6k1NL2ZVEHXat7d
607.423 MK/s (GPU 564.899 MK/s) (2^30.18) [P 100.00%][99.00% in 00:00:00][264]
Warning, wrong private key generated !
  Addr :1TeScAAKnPYiubeMp9zY1oksSwHvQJyo5
  Check:19MTYSffqZLhXy3ShmWRb4rBY8oujWt8tG
594.454 MK/s (GPU 564.622 MK/s) (2^31.15) [P 100.00%][99.00% in 00:00:00][536]

the error seems to be no longer present if the search is greater than 3 characters 1TeSt

Code:

VanitySearch111.exe  -gpu -r 1000000 -g 288 -u -o vanity.txt 1TeSt
VanitySearch v1.11
Difficulty: 264104224
Search: 1TeSt [Uncompressed]
Start Sun Apr  7 13:09:54 2019
Base Key: Randomly changed every 1000000 Mkeys
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
737.703 MK/s (GPU 720.716 MK/s) (2^38.21) [P 100.00%][99.00% in 00:00:00][1183]

Jean_Luc

sr. member

Activity: 462

Merit: 701

Quote from: Lolo54 on April 06, 2019, 06:56:00 PM

the mistake is still there on rtx 2070 with -g 144 and with -g 288

mmm... Strange... I will try to make a long test. It would be great if other uses can also test this case:
VanitySearch.exe -gpu -b -o vanity.txt 1TeS
and run it up to find at least ~10000 matches (~2^34 keys) in order to confirm that it comes from VanitySearch and not from your driver and/or hardware !

Quote from: Lolo54 on April 06, 2019, 06:56:00 PM

on Cuda 8 with -g 4 everything seems ok VanitySearch is running worry-free even with -b and no error message everything seems ok

OK, that's confirm that with -b option and the default setting, your old GPU exceed the timeout.

Thanks for the reports

Lolo54

member

Activity: 131

Merit: 32

the mistake is still there on rtx 2070 with -g 144 and with -g 288
on Cuda 8 with -g 4 everything seems ok VanitySearch is running worry-free even with -b and no error message everything seems ok

Code:

VanitySearch111.exe -gpu -g 144 -r 1000000 -b -o vanity.txt 1TeS
VanitySearch v1.11
Difficulty: 4553521
Search: 1TeS [Compressed or Uncompressed]
Start Sun Apr  7 01:53:48 2019
Base Key: Randomly changed every 1000000 Mkeys
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(144x128)
181.527 MK/s (GPU 175.730 MK/s) (2^31.57) [P 100.00%][99.00% in 00:00:00][1476]
Warning, wrong private key generated !
  Addr :1TeSeqmnn8MyYXaVYeES2SaPnUAuWQbxG
  Check:13GydPaDnhPLLjJk2XyXEABtTtBmTNkUxb
182.163 MK/s (GPU 176.372 MK/s) (2^32.17) [P 100.00%][99.00% in 00:00:00][2202]

Code:

VanitySearch111.exe -gpu -g 288 -b -r 1000000 -o vanity.txt 1TeS
VanitySearch v1.11
Difficulty: 4553521
Search: 1TeS [Compressed or Uncompressed]
Start Sun Apr  7 02:03:35 2019
Base Key: Randomly changed every 1000000 Mkeys
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
167.236 MK/s (GPU 161.537 MK/s) (2^33.64) [P 100.00%][99.00% in 00:00:00][5831]
Warning, wrong private key generated !
  Addr :1TeSgBkRY3wtxfVX342SLGZBXcb8Fi2bC
  Check:13CSJrjs5kvtbVtnyE39GNMq3UgjQcm9vq
150.590 MK/s (GPU 144.750 MK/s) (2^34.36) [P 100.00%][99.00% in 00:00:00][9619]
Warning, wrong private key generated !
  Addr :1TeSL4K1P7SGqhVyKSFoXH4iixygLi3eP
  Check:19V2ZjTcDjtXy1cgrm7iM7xG5pR3ofJrrM
163.799 MK/s (GPU 157.963 MK/s) (2^34.39) [P 100.00%][99.00% in 00:00:00][9825]
Warning, wrong private key generated !
  Addr :1TeSDuJJy2NUYAqBmzF58zAsZ4vn26CwM
  Check:1F2Y9NQwD1qoPR9jWdALLdmLXatXxepP9n
167.448 MK/s (GPU 161.686 MK/s) (2^35.14) [P 100.00%][99.00% in 00:00:00][16459]

Code:

VanitySearchCUDA8.111.exe -gpu -g 4 -r 1000000 -b -o vanity.txt 1TeS
VanitySearch v1.11
Difficulty: 4553521
Search: 1TeS [Compressed or Uncompressed]
Start Sun Apr  7 01:59:05 2019
Base Key: Randomly changed every 1000000 Mkeys
Number of CPU thread: 3
GPU: GPU #0 GeForce GT 520M (1x48 cores) Grid(4x128)
3.553 MK/s (GPU 2.503 MK/s) (2^31.72) [P 100.00%][99.00% in 00:00:00][2545]

Jean_Luc

sr. member

Activity: 462

Merit: 701

The check function checks only one kernel call, here the problem happens after many calls.
I tried with my GTX 1050 and I didn't manage to reproduce the issue. ~2^34 keys, ~10000 matches without problems.
Could you try on the RTX 2070 to launch with -g 144 to see if it changes something ?

Quote from: Lolo54 on April 06, 2019, 12:58:00 PM

The most annoying is for those running only on CUDA 8 (like me with my old hardware) but who can’t launch with -b Vanitysearch instead no errors without -b it works well

Did you try with -g 4 ?

Lolo54

member

Activity: 131

Merit: 32

Pourtant aucune erreur -check tout est ok Huh

Code:

VanitySearch111.exe -check
GetBase10() Results OK
Add() Results OK : 854.701 MegaAdd/sec
Mult() Results OK : 34.014 MegaMult/sec
Div() Results OK : 6.378 MegaDiv/sec
ModInv()/ModExp() Results OK
ModInv() Results OK : 152.621 KiloInv/sec
IntGroup.ModInv() Results OK : 2.801 MegaInv/sec
ModMulK1() Results OK : 4.613 MegaMult/sec
ModSquareK1() Results OK : 5.951 MegaMult/sec
ModMulK1order() Results OK : 4.026 MegaMult/sec
ModSqrt() Results OK !
Check Generator :OK
Check Double :OK
Check Add :OK
Check GenKey :OK
Adress : 15t3Nt1zyMETkHbjJTTshxLnqPzQvAtdCe OK!
Adress : 1BoatSLRHtKNngkdXEeobR76b53LETtpyT OK!
Adress : 1Test6BNjSJC5qwYXsjwKVLvz7DpfLehy OK!
Adress : 16S5PAsGZ8VFM1CRGGLqm37XHrp46f6CTn OK!
Adress : 1Tst2RwMxZn9cYY5mQhCdJic3JJrK7Fq7 OK!
Adress : 3CyQYcByvcWK8BkYJabBS82yDLNWt6rWSx OK!
Adress : 31to1KQe67YjoDfYnwFJThsGeQcFhVDM5Q OK!
Adress : bc1q6tqytpg06uhmtnhn9s4f35gkt8yya5a24dptmn OK!
Check Calc PubKey (full) 1ViViGLEawN27xRzGrEhhYPQrZiTKvKLo :OK
Check Calc PubKey (even) 1Gp7rQ4GdooysEAEJAS2o4Ktjvf1tZCihp:OK
Check Calc PubKey (odd) 18aPiLmTow7Xgu96msrDYvSSWweCvB9oBA:OK
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
Seed: 3768113328
472.198 MegaKey/sec
ComputeKeys() found 6902 items , CPU check...

Lolo54

member

Activity: 131

Merit: 32

Quote from: Jean_Luc on April 06, 2019, 11:11:58 AM

Few more questions:
Does the bug concerning the "wrong generated key" is reproducible and do you always get a wrong key every ~2500 matches ?
Does it happen without the -r option ?

Yes Jean_Luc is reproducible even without the random which does not seem to affect the error

Code:

VanitySearch111.exe -gpu -b -o vanity.txt 1teS
VanitySearch v1.11
Difficulty: 4553521
Search: 1teS [Compressed or Uncompressed]
Start Sat Apr  6 19:46:06 2019
Base Key:BCC54F37771BAEE82D1AEBE1CA891F69718D285F9E90560C334ACA56DA3DCA63
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
163.936 MK/s (GPU 158.026 MK/s) (2^31.53) [P 100.00%][99.00% in 00:00:00][1365]
Warning, wrong private key generated !
  Addr :1teSp8d6dFj8ZCQhcT5SXMHdfdwV2kR5S
  Check:147sQLxg75aoYKc4E9tQxFDvyVEzj3TiHE

Warning, wrong private key generated !
  Addr :1teSB48V2TNi1aBnNEzpR9xENsNHChJci
  Check:1JYfB2NDLAXCB5c2UEYLwhb3xm7N7C5kZP
163.657 MK/s (GPU 157.807 MK/s) (2^31.74) [P 100.00%][99.00% in 00:00:00][1663]

This seems to be due to the EXCLUSIVELY calculation of the unzipped keys since by putting only -u the error also occursThis seems to be due to the EXCLUSIVELY calculation of the unzipped keys since by putting only -u the error also occurs

Code:

VanitySearch111.exe -gpu -r 1000000 -u -o vanity.txt 1TeS
VanitySearch v1.11
Difficulty: 4553521
Search: 1TeS [Uncompressed]
Start Sat Apr  6 19:49:36 2019
Base Key: Randomly changed every 1000000 Mkeys
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
292.479 MK/s (GPU 280.867 MK/s) (2^32.27) [P 100.00%][99.00% in 00:00:00][1177]
Warning, wrong private key generated !
  Addr :1TeSCTxiHYpZzhY8CimJCwbrqTvtzV1gg
  Check:1EhdJ3k1Vhs7BZGQmFgZhDiBGgogQz8j5w
278.226 MK/s (GPU 268.900 MK/s) (2^32.40) [P 100.00%][99.00% in 00:00:00][1271]

no recurrence on the number of match 2500 or not instead on CUDA 10 the "bug" is not awkward since the rate of calculation error is about 0.05% which is a detail of no importance in fact but I point out to you Wink

The most annoying is for those running only on CUDA 8 (like me with my old hardware) but who can’t launch with -b Vanitysearch instead no errors without -b it works well

Topic: VanitySearch (Yet another address prefix finder) - page 50. (Read 32966 times)