Latest posts of: Lolo54

Show Posts
Pages: « 1 2 3 [4] 5 6 »

Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder)

on: April 18, 2019, 03:36:21 PM

Effectively Grin

everything works perfectly Wink

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 17:31:42 2019
Base Key: 4C4F9EA9EC872852E88364D461C68A8B17B4A49A3556C0B1FD97B341CA64E495
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)

VanitySearchCUDA10.113.exe -rp KxFuiDGdGLoMKGnVfZ4x4sXLs6GPkp2a7teATCyLV65XKxt65s35 keyinfo.txt

Pub Addr: 1LaureFDXZ7qs9cWU8PgiZ5fhWHgQJ5eNY
Priv (WIF): p2pkh:KzpFMQA6UcDJCDWDYFpz9LdV4VAFSm8EiQbonHx48s9MEAcB3B7p
Priv (HEX): 0x6B478EFA094CFDD0A1030610C25F223DB4D95C0639634C042A1711B8A6B2C2F2

Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder)

on: April 18, 2019, 01:10:50 PM

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 "

Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys

on: April 18, 2019, 12:10:37 AM

Quote from: SuffaBit on April 16, 2019, 11:00:55 PM How much addresses i can add in one time? no limit on the number of addresses but it is the speed of calculation which will decrease according to the number

Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys

on: April 09, 2019, 07:53:33 PM

it should work if the file is placed in c: \ card

Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys

on: April 09, 2019, 03:04:45 PM

no coding to enter the addresses you simply create a text file and you insert the addresses so it does not need any space at the end of the addresses and one per line that addresses in 1 Code: 18GD1XxYxoiDs4zrAP9xnZhuzjCDsoNVCZ 1JgC1U7RC1fivD6BwRe7sg2UrGoF6CiQvh 1PvizbqgxRiRdtfBpbSexRwTnY7T5V286i 15yq4fvcvfDVY4ZQfjHTYekh2iPjK41Stg 1KDiHQHnEw9dtH2mXakJ8T1cyDTcYKZHh8 1A2DL4Cubj8tBKV1piCMSLvkWZZATkYV2d 1KhPpNtT2KpnYF5UAn4kN5Ly2j8Ak9h2y8 1GQiJfCpC7axrrfxNM7FCMDXvMa8oNPkgN 1EPqn5hHuYniGKreV81ipH86LgdqRzqxpS check that your text files are only named check and resu and not check.txt and resu.txt otherwise your command line should be C: \ CARD \ clBitCrack.exe -b 36 -t 128 -p 800 -c -u -i check.txt.txt -o resu.txt.txt --keyspace e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b845: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991c8962b865

Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder)

on: April 09, 2019, 11:51:45 AM

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]

Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder)

on: April 08, 2019, 06:12:50 PM

Ok jean luc i’m trying tomorrow

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

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?

Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys

on: April 07, 2019, 11:42:54 PM

Quote from: iparktur on April 07, 2019, 06:30:37 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

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]

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]

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...

Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder)

on: April 06, 2019, 05:58:00 PM

Quote from: Jean_Luc on April 06, 2019, 04:11:58 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

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

Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder)

on: April 04, 2019, 12:38:22 PM

Quote from: Jean_Luc on April 04, 2019, 12:23:57 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

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]

Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder)

on: April 03, 2019, 04:56:42 PM

Quote from: Jean_Luc on April 03, 2019, 04:37:53 PM 1.11 available for CUDA8 Super thanks Jean-Luc, look I just edited my top post to complete my tests I tried to be as complete as possible by showing various commands good -i and -o everyone will put what they want in -i

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]

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]

Pages: « 1 2 3 [4] 5 6 »