Bitcoin Forum
January 27, 2020, 03:39:35 AM *
News: Latest Bitcoin Core release: 0.19.0.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 [13] 14 15 16 17 18 19 20 21 22 23 24 25 26 27 »
  Print  
Author Topic: VanitySearch (Yet another address prefix finder)  (Read 9186 times)
asche
Hero Member
*****
Offline Offline

Activity: 756
Merit: 922


I forgot more than you will ever know.


View Profile
April 02, 2019, 07:47:14 AM
 #241

It is a first attempt, this is just to allow to run VanitySearch like this (for those who want a private address starting with 3).

You mean a public address starting with 3 I guess?

Thank you for implementing tho Smiley

1580096375
Hero Member
*
Offline Offline

Posts: 1580096375

View Profile Personal Message (Offline)

Ignore
1580096375
Reply with quote  #2

1580096375
Report to moderator
1580096375
Hero Member
*
Offline Offline

Posts: 1580096375

View Profile Personal Message (Offline)

Ignore
1580096375
Reply with quote  #2

1580096375
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1580096375
Hero Member
*
Offline Offline

Posts: 1580096375

View Profile Personal Message (Offline)

Ignore
1580096375
Reply with quote  #2

1580096375
Report to moderator
1580096375
Hero Member
*
Offline Offline

Posts: 1580096375

View Profile Personal Message (Offline)

Ignore
1580096375
Reply with quote  #2

1580096375
Report to moderator
1580096375
Hero Member
*
Offline Offline

Posts: 1580096375

View Profile Personal Message (Offline)

Ignore
1580096375
Reply with quote  #2

1580096375
Report to moderator
Jean_Luc
Full Member
***
Offline Offline

Activity: 222
Merit: 223


View Profile
April 02, 2019, 07:55:50 AM
 #242

You mean a public address starting with 3 I guess?

Right Wink
DarkStar_
Legendary
*
Online Online

Activity: 1582
Merit: 2221


https://bitcoin.watfordfc.com


View Profile WWW
April 02, 2019, 10:07:35 PM
 #243

Just curious, why P2SH? AFAIK there's no benefits of P2SH over legacy addresses if it's only 1 on 1, and you pay more fees. P2SH with Segwit would be great though  Cheesy

It is a first attempt, this is just to allow to run VanitySearch like this (for those who want a private address starting with 3).

Code:
-snip-
Pub Addr: 3PrivG5uq7hwXLyAHbYkFTnFkzx1FEWQdf
Priv (WIF): p2wpkh-p2sh:L2wAVD273GwAxGuEDHvrCqPfuWg5wWLZWy6H3hjsmhCvNVuCERAQ
Priv (HEX): 0xAA83217B3A11FCCFF8142EF0681AD774D7AB6822F574C4BB99CBF9B9DD01E7F2

For 2to2 segwit, I need to implement split private keys then generate a 2to2 address from 2 given public key, this is more complex but I will try to do it. That has no sense that VanitySearch output 2 full private keys in the same file, no ?

One question, 2to2 segwit is possible only with BECH32 format (bc1...) or it is also possible with Base58 (3...) ?



Ah, you meant a P2SH SegWit address. That makes more sense, I thought you were talking about a P2SH address without SegWit. I agree, there's really no point for supporting 2 of 2 multisig or any other multisig option because of how vanitygen works. If you want a challenge, trying to get split key verification working would be nice and probably more useful  Cheesy

2 of 2 SegWit should be possible with Base58 I believe. You can do 2 of 3 SegWit as shown in this transaction, so it makes sense that 2 of 2 is doable.

Jean_Luc
Full Member
***
Offline Offline

Activity: 222
Merit: 223


View Profile
April 03, 2019, 06:59:25 AM
Merited by DarkStar_ (4), OgNasty (1), ETFbitcoin (1)
 #244

Hello,

I just published the release 1.11 of VanitySearch:
https://github.com/JeanLucPons/VanitySearch/releases/tag/1.11
- Added support for segwit address P2SH and BECH32
I upload the windows release for CUDA8 asap.

Code:
C:\C++\VanitySearch\x64\Release>VanitySearch.exe -stop -gpu 3Happy
VanitySearch v1.11
Difficulty: 264104224
Search: 3Happy [Compressed]
Start Wed Apr  3 08:50:51 2019
Base Key:D1D33873F77889F1BF84683A9119A2B369758438EB1D6256E56504497F9475E7
Number of CPU thread: 7
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
129.830 MK/s (GPU 113.242 MK/s) (2^27.95) [P 62.59%][70.00% in 00:00:00][0]
Pub Addr: 3HappypJDDfhbj5HasnFmctzd8Up7B5tLR
Priv (WIF): p2wpkh-p2sh:L3q4EBHk5eiuxhsNagsmY5aK8sCNd6zdh6gmqpVG6S666GbvNgcP
Priv (HEX): 0xC5351D98B0B2DE1BD6B7CACADA9A2BE4E09B849FB8816D1CEEC5A08C63A3E837

Code:
C:\C++\VanitySearch\x64\Release>VanitySearch.exe -stop bc1queen
VanitySearch v1.11
Difficulty: 1048576
Search: bc1queen [Compressed]
Start Wed Apr  3 08:56:32 2019
Base Key:6F907FDE30067DCDE802739E47C6463FE49C32791242458C2D141212DB107A55
Number of CPU thread: 8

Pub Addr: bc1queenu8kq0vjrl509w88mwefdu4pztkdvlst4at
Priv (WIF): p2wpkh:L24UVC7ZYgYjy4cStQvBHD3quJkeYN3xHYBqFjTYjJjwmht84jsg
Priv (HEX): 0x906F8021CFF9823217FD8C61B839B9BED612AA6D9D065AAF92BE4C79F5251BBA

Thanks for testing Wink
asche
Hero Member
*****
Offline Offline

Activity: 756
Merit: 922


I forgot more than you will ever know.


View Profile
April 03, 2019, 08:14:46 AM
 #245


Thank you so much. This tool is perfect now Cheesy

Lolo54
Member
**
Offline Offline

Activity: 70
Merit: 25


View Profile
April 03, 2019, 04:31:18 PM
Last edit: April 03, 2019, 04:53:33 PM by Lolo54
 #246

Hello, here are the results of my tests first on my old hardware Core I5-2430M - NVIDIA GEFORCE GT520M that only supports CUDA 8

Code:
VanitySearchCUDA10.111.exe 1Testrrr
VanitySearch v1.11
Difficulty: 51529903411245
Search: 1Testrrr [Compressed]
Start Wed Apr  3 18:26:55 2019
Base Key:D4098AD1EC1DEB76F2A73F99D5FB7C0BAE6DDD0E5D956D3EE5501891D2377A1D
Number of CPU thread: 4
4.175 MK/s (GPU 0.000 MK/s) (2^25.61) [P 0.00%][50.00% in 98.9d][0]

Then another more efficient configuration
intel core i5-9600k 3.70 GHz  RAM32 GO  GPU NVIDIA 2070

Code:
VanitySearch111.exe -gpu 1Testrrr
VanitySearch v1.11
Difficulty: 51529903411245
Search: 1Testrrr [Compressed]
Start Wed Apr  3 18:36:00 2019
Base Key:926C0B465C72AFA454BEBE9F16EECCD1BFCBF2520FACAD90CD1DE23141769E4B
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
1535.880 MK/s (GPU 1470.257 MK/s) (2^31.52) [P 0.01%][50.00% in 06:27:06][0]

[code]
VanitySearch111.exe -gpu 3BTestrrr
VanitySearch v1.11
Difficulty: 51529903411245
Search: 3BTestrrr [Compressed]
Start Wed Apr  3 18:43:07 2019
Base Key:307D1359B8316234060503DDD4664191869953DE79243998184856E717B631B1
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
665.464 MK/s (GPU 647.760 MK/s) (2^33.25) [P 0.02%][50.00% in 14:53:15][0]


Code:
VanitySearch111.exe -gpu -r 500000 3BTestrrr
VanitySearch v1.11
Difficulty: 51529903411245
Search: 3BTestrrr [Compressed]
Start Wed Apr  3 18:46:37 2019
Base Key: Randomly changed every 500000 Mkeys
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
672.639 MK/s (GPU 654.885 MK/s) (2^33.70) [P 0.03%][50.00% in 14:43:38][0]

Code:
VanitySearch111.exe -gpu -r 2000 -t 6 3Btestrrr
VanitySearch v1.11
Difficulty: 51529903411245
Search: 3Btestrrr [Compressed]
Start Wed Apr  3 18:48:13 2019
Base Key: Randomly changed every 2000 Mkeys
Number of CPU thread: 6
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
421.783 MK/s (GPU 405.673 MK/s) (2^33.37) [P 0.02%][50.00% in 23:29:17][0]

Code:
VanitySearch111.exe -gpu -r 1000 bc1qrmnttuss
VanitySearch v1.11
Difficulty: 1099511627776
Search: bc1qrmnttuss [Compressed]
Start Wed Apr  3 18:51:02 2019
Base Key: Randomly changed every 1000 Mkeys
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
947.492 MK/s (GPU 908.299 MK/s) (2^32.94) [P 0.75%][50.00% in 00:13:15][0]

everything works well including
using -i and -o. Prefixes starting with 3 seem longer to calculate, those starting with 1 and bc1 faster
Thanks again to Jean_Luc for this beautiful update and for all the new features, VanitySearch is now well done[/code]
Jean_Luc
Full Member
***
Offline Offline

Activity: 222
Merit: 223


View Profile
April 03, 2019, 04:37:53 PM
 #247

1.11 available for CUDA8 Wink
Lolo54
Member
**
Offline Offline

Activity: 70
Merit: 25


View Profile
April 03, 2019, 04:56:42 PM
 #248

1.11 available for CUDA8 Wink
Super thanks Jean-Luc, look I just edited my top post to complete my tests Wink
I tried to be as complete as possible by showing various commands good -i and -o everyone will put what they want in -i  Smiley
Jean_Luc
Full Member
***
Offline Offline

Activity: 222
Merit: 223


View Profile
April 03, 2019, 05:38:37 PM
 #249

Yes, P2WPKH-P2SH (starting with '3') addresses are slower, there are 2 hash160 to compute per address, only 1 for P2PKH (starting with '1') and P2WPKH-BECH32 (starting with 'bc1q').

Edit:
Interesting test, you notice also that the -r option is costly for nothing...
Lolo54
Member
**
Offline Offline

Activity: 70
Merit: 25


View Profile
April 04, 2019, 11:55:58 AM
 #250

Good morning,
I don’t know why but with CUDA 8 equivalent parameter seems to calculate +12% faster than CUDA 10

cuda 10
Code:
-gpu 1Testtttt
VanitySearch v1.11
Difficulty: 2988734397852221
Search: 1Testtttt [Compressed]
Start Thu Apr  4 13:46:27 2019
Base Key:9FF416E41E27BCE6DCC117E3EC28D088EA16EB7CF988BEABDFE45490162F0C16
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
1222.410 MK/s (GPU 1195.740 MK/s) (2^36.49) [P 0.00%][50.00% in 19.7d][0]

cuda 8
Code:
VanitySearchCUDA8.111 -gpu 1Testtttt
VanitySearch v1.11
Difficulty: 2988734397852221
Search: 1Testtttt [Compressed]
Start Thu Apr  4 13:49:35 2019
Base Key:A9CEB9932E377B3FC4517C8AF508432AF71CEA2276FDF3E1E97FB0F0D02917F9
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
1369.064 MK/s (GPU 1342.856 MK/s) (2^34.54) [P 0.00%][50.00% in 17.6d][0]
Jean_Luc
Full Member
***
Offline Offline

Activity: 222
Merit: 223


View Profile
April 04, 2019, 12:23:57 PM
 #251

That's strange, on my GTX 1050 Ti, CUDA8 is slightly slower (~3%) than CUDA10. On my GTX 645 it is similar.
Did you wait that key rate is well stabilized ?

Code:
C:\C++\VanitySearch\x64\Release>VanitySearch.exe -t 0 -stop -gpu 1Testtttt
VanitySearch v1.11
Difficulty: 2988734397852221
Search: 1Testtttt [Compressed]
Start Thu Apr  4 14:18:30 2019
Base Key:28B34C47FDB37FB3175059450AFD3D301F682B2F16217EEE25AD83A42939A1B6
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
226.483 MK/s (GPU 226.483 MK/s) (2^32.65) [P 0.00%][50.00% in 106.4d][0]

Code:
C:\C++\VanitySearch\x64\Release>VanitySearchCUDA8.exe -t 0 -stop -gpu 1Testtttt
VanitySearch v1.11
Difficulty: 2988734397852221
Search: 1Testtttt [Compressed]
Start Thu Apr  4 14:19:17 2019
Base Key:290C9148BE403FE1904ACA72641003E9B04507E30A054DA64DB732963C3080D0
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
219.406 MK/s (GPU 219.406 MK/s) (2^32.04) [P 0.00%][50.00% in 109.8d][0]
Lolo54
Member
**
Offline Offline

Activity: 70
Merit: 25


View Profile
April 04, 2019, 12:38:22 PM
 #252

That's strange, on my GTX 1050 Ti, CUDA8 is slightly slower (~3%) than CUDA10. On my GTX 645 it is similar.
Did you wait that key rate is well stabilized ?


ok that is correct Jean_Luc actually waiting 2min the stabilization between the 2 versions is much less important yes about 3% at me too
Lolo54
Member
**
Offline Offline

Activity: 70
Merit: 25


View Profile
April 06, 2019, 02:15:38 PM
Last edit: April 06, 2019, 02:26:36 PM by Lolo54
 #253

Code:
[code]Hello
I noticed a few bugs without knowing where it might have come from?
Some error messages
first under CUDA 10 when the search is started with 3 pattern with GPU // without using GPU no problems

[code]
VanitySearch111.exe -gpu -r 1000000 -b -o vanity.txt 1TeS
VanitySearch v1.11
Difficulty: 4553521
Search: 1TeS [Compressed or Uncompressed]
Start Sat Apr  6 15:26:11 2019
Base Key: Randomly changed every 1000000 Mkeys
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
337.525 MK/s (GPU 324.861 MK/s) (2^32.33) [P 100.00%][99.00% in 00:00:00][2409]
Warning, wrong private key generated !
  Addr :1TeSstduvsJfM9wAJ8UvjN41mvAy9U98J
  Check:1BW7YEF2dEFYpymuysVHywrvQnFcJHMt3x
349.466 MK/s (GPU 338.776 MK/s) (2^33.45) [P 100.00%][99.00% in 00:00:00][5103]
Warning, wrong private key generated !
  Addr :1TeSoeK3628J1GuTqSfcrUSp6UW45Ffmf
  Check:1NwdtKgE7oH4CMdau7w37vHmWN4nuRaegW

The same search without using the GPU no error message seems to happen

Code:
VanitySearch111.exe -r 1000000 -b -o vanity.txt 1TeS
VanitySearch v1.11
Difficulty: 4553521
Search: 1TeS [Compressed or Uncompressed]
Start Sat Apr  6 15:29:51 2019
Base Key: Randomly changed every 1000000 Mkeys
Number of CPU thread: 6
12.683 MK/s (GPU 0.000 MK/s) (2^30.20) [P 100.00%][99.00% in 00:00:00][530]

4 Pattern with or without the -gpu command no error message

Code:
VanitySearch111.exe -gpu -r 1000000 -b -o vanity.txt 1TeST
VanitySearch v1.11
Difficulty: 264104224
Search: 1TeST [Compressed or Uncompressed]
Start Sat Apr  6 15:32:47 2019
Base Key: Randomly changed every 1000000 Mkeys
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
460.813 MK/s (GPU 450.125 MK/s) (2^34.85) [P 100.00%][99.00% in 00:00:00][232]

Code:
VanitySearch111.exe -r 1000000 -b -o vanity.txt 1TeST
VanitySearch v1.11
Difficulty: 264104224
Search: 1TeST [Compressed or Uncompressed]
Start Sat Apr  6 15:34:47 2019
Base Key: Randomly changed every 1000000 Mkeys
Number of CPU thread: 6
12.468 MK/s (GPU 0.000 MK/s) (2^31.08) [P 99.98%][99.00% in 00:00:00][13]

without using the -b command more error even with -gpu and 3 pattern
It seems that the calculation in uncompressed poses worries using the GPU with less than 4 pattern (CUDA 10) and prevents the launch of Vanitysearch under CUDA 8

Under CUDA error message using the -gpu and -b command while without any problem

Code:
VanitySearchCUDA8.111.exe -b -r 100000 -o vanity.txt 1TeS
VanitySearch v1.11
Difficulty: 4553521
Search: 1TeS [Compressed or Uncompressed]
Start Sat Apr  6 15:45:09 2019
Base Key: Randomly changed every 100000 Mkeys
Number of CPU thread: 4
1.724 MK/s (GPU 0.000 MK/s) (2^26.94) [P 100.00%][99.00% in 00:00:00][39]

with the command - gpu CUDA 8 with 3 or 4 pattern message error unless the -b command is not used

Code:
VanitySearchCUDA8.111.exe -gpu -b -r 100000 -o vanity.txt 1TeS
VanitySearch v1.11
Difficulty: 4553521
Search: 1TeS [Compressed or Uncompressed]
Start Sat Apr  6 15:48:40 2019
Base Key: Randomly changed every 100000 Mkeys
Number of CPU thread: 3
GPU: GPU #0 GeForce GT 520M (1x48 cores) Grid(8x128)
GPUEngine: Launch: the launch timed out and was terminated 00:00:00][0]

[/code]
VanitySearchCUDA8.111.exe -gpu -o vanity.txt 1TeST
VanitySearch v1.11
Difficulty: 264104224
Search: 1TeST [Compressed]
Start Sat Apr  6 15:54:54 2019
Base Key:486E8062406D92DBF21C6B8DB09A4733D7F2685A2E30FCC3714B400E5E6DECAD
Number of CPU thread: 3
GPU: GPU #0 GeForce GT 520M (1x48 cores) Grid(8x128)
9.482 MK/s (GPU 6.621 MK/s) (2^30.78) [P 99.91%][99.00% in 00:00:00][11]
[/CODE]

Code:
VanitySearchCUDA8.111.exe -gpu -b -o vanity.txt 1TeS
VanitySearch v1.11
Difficulty: 4553521
Search: 1TeS [Compressed or Uncompressed]
Start Sat Apr  6 16:01:48 2019
Base Key:719ACDC6941DEB67E424B31DB0A0592777C5297E7ABB21E6091DA47CA6A80C2F
Number of CPU thread: 3
GPU: GPU #0 GeForce GT 520M (1x48 cores) Grid(8x128)
GPUEngine: Launch: the launch timed out and was terminated 00:00:00][0]

Code:
VanitySearchCUDA8.111.exe -gpu -r 50000 -o vanity.txt 1TeS
VanitySearch v1.11
Difficulty: 4553521
Search: 1TeS [Compressed]
Start Sat Apr  6 15:59:00 2019
Base Key: Randomly changed every 50000 Mkeys
Number of CPU thread: 3
GPU: GPU #0 GeForce GT 520M (1x48 cores) Grid(8x128)
10.593 MK/s (GPU 7.053 MK/s) (2^28.05) [P 100.00%][99.00% in 00:00:00][56]


the use of the -b command by associating with the -gpu under CUDA 8 seems to prevent the launch of VanitySearch under CUDA 10 but with 3 pattern ex 1TeS error messages appear while from 4pattern ex 1TeST more error messages Huh
 


Jean_Luc
Full Member
***
Offline Offline

Activity: 222
Merit: 223


View Profile
April 06, 2019, 03:58:16 PM
 #254

Hello
Thanks for the report.
I try with both CUDA8 and CUDA10 using -b option and I generated ~2^33 keys with the same pattern as you did.
It has also found ~5000 matches without error in my case using a GTX 645.
Concerning the timeout of your GT 520M try with -g 4, a CUDA kernel has a limit of execution time, searching with -b is longer.
I will make more test on other hardware ASAP.

Code:
C:\C++\VanitySearch\x64\Release>VanitySearchCUDA8.exe -r 100000 -b -o output.txt -gpu 1TeS
VanitySearch v1.11
Difficulty: 4553521
Search: 1TeS [Compressed or Uncompressed]
Start Sat Apr  6 17:07:14 2019
Base Key: Randomly changed every 100000 Mkeys
Number of CPU thread: 3
GPU: GPU #0 GeForce GTX 645 (3x192 cores) Grid(24x128)
13.944 MK/s (GPU 12.859 MK/s) (2^33.43) [P 100.00%][99.00% in 00:00:00][5049]

Code:
C:\C++\VanitySearch\x64\Release>VanitySearch.exe -r 100000 -b -o output.txt -gpu 1TeS
VanitySearch v1.11
Difficulty: 4553521
Search: 1TeS [Compressed or Uncompressed]
Start Sat Apr  6 17:33:01 2019
Base Key: Randomly changed every 100000 Mkeys
Number of CPU thread: 3
GPU: GPU #0 GeForce GTX 645 (3x192 cores) Grid(24x128)
14.804 MK/s (GPU 13.716 MK/s) (2^33.51) [P 100.00%][99.00% in 00:00:00][5315]
Jean_Luc
Full Member
***
Offline Offline

Activity: 222
Merit: 223


View Profile
April 06, 2019, 04:11:58 PM
 #255

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 ?
Lolo54
Member
**
Offline Offline

Activity: 70
Merit: 25


View Profile
April 06, 2019, 05:58:00 PM
Merited by DarkStar_ (4), Jean_Luc (4)
 #256

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
Lolo54
Member
**
Offline Offline

Activity: 70
Merit: 25


View Profile
April 06, 2019, 06:00:25 PM
 #257

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...
Jean_Luc
Full Member
***
Offline Offline

Activity: 222
Merit: 223


View Profile
April 06, 2019, 06:48:12 PM
 #258

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 ?

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
**
Offline Offline

Activity: 70
Merit: 25


View Profile
April 06, 2019, 11:56:00 PM
Last edit: April 07, 2019, 12:15:22 AM by Lolo54
 #259

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
Full Member
***
Offline Offline

Activity: 222
Merit: 223


View Profile
April 07, 2019, 07:44:33 AM
 #260

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 !

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 Smiley
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 [13] 14 15 16 17 18 19 20 21 22 23 24 25 26 27 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!