Bitcoin Forum
October 27, 2020, 05:57:28 PM *
News: Latest Bitcoin Core release: 0.20.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 [2] 3 4 »
21  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: April 08, 2019, 05:32:08 PM
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
22  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: April 08, 2019, 02:27:49 PM
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?
23  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: April 07, 2019, 11:42:54 PM
QUESTION - why the software clBitCrack after a closing -up has not written to the information of any concurrence to addresses?
What I have made incorrectly?
Try to do that and your problem should be fixed and you should increase your speed
create a text file in C: \ CARD that you name "resu" or otherwise and a second text file that corresponds to the file in which you mention all the addresses you want (one address per line) the syntax is important otherwise you will have a error message call this file "check"
so it will load all your addresses and as soon as it will find one you will be able to find all the details in your file resu
tapes the following commands to launch
-b 36 -t 128 -p 800 -c -u -i check.txt -o resu.txt --keyspace e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b845: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991c8962b865 
or only
-p 900 -c -u -i check.txt -o resu.txt --keyspace e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b845: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991c8962b865
24  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: April 07, 2019, 10:57:17 AM
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]
25  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: April 06, 2019, 11:56:00 PM
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]
26  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: April 06, 2019, 06:00:25 PM
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...
27  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: April 06, 2019, 05:58:00 PM
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
28  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: April 06, 2019, 02:15:38 PM
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
 


29  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: April 04, 2019, 12:38:22 PM
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
30  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: April 04, 2019, 11:55:58 AM
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]
31  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: April 03, 2019, 04:56:42 PM
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
32  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: April 03, 2019, 04:31:18 PM
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]
33  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: March 30, 2019, 11:42:24 AM
Hello, it seems to me faster

works perfectly

Code:
VanitySearchCUDA8..exe -gpu 1Testrrr
VanitySearch v1.10
Difficulty: 51529903411245
Search: 1Testrrr [Compressed]
Start Sat Mar 30 12:38:01 2019
Base Key:57AA37BF4DB32E5668B51B6599428CF30FB675996C0A10FDA84761AE0B3C3BE9
Number of CPU thread: 3
GPU: GPU #0 GeForce GT 520M (1x48 cores) Grid(8x128)
10.233 MK/s (GPU 7.026 MK/s) (2^27.89) [P 0.00%][50.00% in 40.4d][0]
34  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: March 30, 2019, 01:12:09 AM
And if a weak graphics card on a laptop?
What can be the optimal settings for the AMD Radeon HD 6520G ?

AMD Radeon HD 6520G
try this
-p 400 -c -u 1Dg98F1x115vkgL9cHh4fqhpQpY2dXz83u
35  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: March 30, 2019, 01:00:41 AM
good evening Jean_Luc thank you for the great work here is the result of my tests on my configuration NVIDIA GeForce GT520M Intel core I5-2430M

Code:
VanitySearchCUDA8.exe -check
VanitySearch v1.10
GetBase10() Results OK
Add() Results OK : 61.690 MegaAdd/sec
Mult() Results OK : 6.542 MegaMult/sec
Div() Results OK : 834.376 KiloDiv/sec
ModInv()/ModExp() Results OK
ModInv() Results OK : 103.923 KiloInv/sec
IntGroup.ModInv() Results OK : 1.565 MegaInv/sec
ModMulK1() Results OK : 1.939 MegaMult/sec
ModSquareK1() Results OK : 1.922 MegaMult/sec
ModMulK1order() Results OK : 1.031 MegaMult/sec
ModSqrt() Results OK !
Check Generator :OK
Check Double :OK
Check Add :OK
Check GenKey :OK
Adress : 15t3Nt1zyMETkHbjJTTshxLnqPzQvAtdCe OK!
Adress : 1BoatSLRHtKNngkdXEeobR76b53LETtpyT OK!
Adress : 1JeanLucgidKHxfY5gkqGmoVjo1yaU4EDt OK(comp)!
Adress : 1Test6BNjSJC5qwYXsjwKVLvz7DpfLehy OK!
Adress : 1BitcoinP7vnLpsUHWbzDALyJKnNo16Qms OK(comp)!
Adress : 16S5PAsGZ8VFM1CRGGLqm37XHrp46f6CTn OK(comp)!
Adress : 1Tst2RwMxZn9cYY5mQhCdJic3JJrK7Fq7 OK(comp)!
Check Calc PubKey (full) 1ViViGLEawN27xRzGrEhhYPQrZiTKvKLo :OK
Check Calc PubKey (even) 1Gp7rQ4GdooysEAEJAS2o4Ktjvf1tZCihp:OK
Check Calc PubKey (odd) 18aPiLmTow7Xgu96msrDYvSSWweCvB9oBA:OK
GPU: GPU #0 GeForce GT 520M (1x48 cores) Grid(8x128)
Seed: 1024278713
7.191 MegaKey/sec
ComputeKeys() found 176 items , CPU check...
GPU/CPU check OK

Code:
VanitySearchCUDA8.exe -l
VanitySearch v1.10
GPU #0 GeForce GT 520M (1x48 cores) (Cap 2.1) (1024.0 MB) (Multiple host threads)

Code:
VanitySearchCUDA8.exe -t 4 -gpu 1Testrrr
VanitySearch v1.10
Difficulty: 51529903411245
Search: 1Testrrr [Compressed]
Start Sat Mar 30 01:58:45 2019
Base Key:EB4A2ED806A60F7C834D62E4CA6C12DFA10C57FDD8075060EADC02E849168E02
Number of CPU thread: 4
GPU: GPU #0 GeForce GT 520M (1x48 cores) Grid(8x128)
7.731 MK/s (GPU 6.929 MK/s) (2^27.07) [P 0.00%][50.00% in 53.4d][0]

Code:
VanitySearchCUDA8.exe -gpu 1Testrrr
VanitySearch v1.10
Difficulty: 51529903411245
Search: 1Testrrr [Compressed]
Start Sat Mar 30 01:45:44 2019
Base Key:497A23E01DE91DCC1958FF3111AC7158E295766E266BEBD85879A53689C3CEF3
Number of CPU thread: 3
GPU: GPU #0 GeForce GT 520M (1x48 cores) Grid(8x128)
7.770 MK/s (GPU 7.058 MK/s) (2^28.94) [P 0.00%][50.00% in 53.1d][0]

only CPU - much slow

Code:
1Testrrr
VanitySearch v1.10
Difficulty: 51529903411245
Search: 1Testrrr [Compressed]
Start Sat Mar 30 02:06:38 2019
Base Key:1CDE92D7AB47587457BFE29138D7F766885CACEF828B2EBF2C27008857B3F019
Number of CPU thread: 4
0.840 MK/s (GPU 0.000 MK/s) (2^24.02) [P 0.00%][50.00% in 1.3y][0]

 Smiley

36  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: March 29, 2019, 03:53:01 AM
Test the following parameters -b 36 -t 512 -p 2900 or only -p 2900 or 3400 Otherwise check using cudaInfo.exe for the best settings for your configuration.
Regarding the performance optimization of cubitcrack compared to vanitysearch it is not so comparable in that their usefulness is different but also because the author here is no present unlike on the vanitysearch file. It is obvious that cubitcrack could be very much optimized in terms of speed of execution by using both the CPU and Gpu but also in its calculation way that could without worry be increased by 50% ... this is not However, it would in no way endanger private keys farther than the one already discovered even if the beach was known for it must be used another way of doing that brute force. Vanitysearch even if much faster is absolutely not done for that either!
37  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: March 23, 2019, 08:57:09 PM
An other report from a user using CUDA 8 and gcc 4.8 on a GeForce GTX 460. It works.


Does CUDA 8 work on Windows or only Linux?

-Dave
for the moment only on linux but it seems to me that jean_luc try or will try to adjust for windows also .... it is more difficult than for linux I think
38  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: March 20, 2019, 03:50:05 PM
I compiled a cuda 8 binaries if you want to try if you have same the behavior.
http://zelda38.free.fr/VanitySearch/1.9/VanitySearch50_cuda8

On my install with SDK 8, it uses 135 registers and 0 spill move.
With SDK 10, only 120 registers and also 0 spill move.

Hello
is it possible jean luc to compile it in .exe for CUDA 8 under windows or it only works for linux with cuda 8?
39  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: March 16, 2019, 02:48:10 PM
I confirm that there is a problem with difficulty calculation when searching prefix like 1111something...

For this prefix vanitygen
vanitygen.exe 11111
Difficulty: 4294967296
[353.08 Kkey/s][total 20853248][Prob 0.5%][50% in 2.8h]

and for

vanitygen.exe 111111
Difficulty: 1099511627776
[326.68 Kkey/s][total 987648][Prob 0.0%][50% in 27.0d]
40  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: March 16, 2019, 10:50:58 AM
 Shocked Beautiful increase stivensons me compared to the first version on only CPU go 10 times faster!
Iím not going to slow down but still amazing

By comparing the respective vanitygen/ cubitcrack speeds (compressed only) / vanitysearch on my CPU only

Vanitygen : Difficulty: 15318045009
[331.74 Kkey/s][total 2865408][Prob 0.0%][50% in 8.9h]

cubitcrack: GeForce GT 520M  531/1024MB | 1 target 3.18 MKey/s (17,301,504 total) [00:00:03]

vanitysearch: Start Sat Mar 16 12:13:44 2019
Difficulty: 15318045009
Search: 1testr
Base Key:30704D4B3275DE9A2D2F8B9AD01DB22F5694E0A58F0C0A0E21D1B1A110305637
Number of CPU thread: 4
15.261 MK/s (GPU 0.000 MK/s) (2^26.12) [P 0.48%][50.00% in 00:14:34][0]
Pages: « 1 [2] 3 4 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!