Latest posts of: stivensons

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

Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] $DVT DeVault - The Decentralized Community Economy [PoW + Cold Rewards]

on: June 04, 2019, 04:22:45 PM

BSOD.PW supports DeVault Welcome to the world of happy mining! https://bsod.pw Code: -a sha256d -o stratum+tcp://pool.bsod.pw:2604 -u WALLET.rig You can mine this coin SOLO and PARTY (what is it?) on https://bsod.pw Code: -a sha256d -o stratum+tcp://pool.bsod.pw:2604 -u WALLET.rig -p m=solo Code: -a sha256d -o stratum+tcp://pool.bsod.pw:2604 -u WALLET.rig -p m=party.yourpassword NOTICE: You can use eu for Europe, us for North America and asia for Asia instead of pool in your .bat file or config Feel free to use our new monitor apps for Android and iOS: https://play.google.com/store/apps/details?id=kg.stark.bsod https://itunes.apple.com/ru/app/bsod-pw-mining-pool/id1459532591 Helping you make profit in crypto altcoins mining since 2017, Your bsod.pw team.

Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][PoW][X16R] Zyrk - Pushing the boundaries of blockchain technology

on: May 05, 2019, 12:35:45 PM

BSOD.PW supports ZyrkCoin Welcome to the world of happy mining! https://bsod.pw Code: -a x16r -o stratum+tcp://pool.bsod.pw:2594 -u WALLET.rig You can mine this coin SOLO and PARTY (what is it?) on https://bsod.pw Code: -a x16r -o stratum+tcp://pool.bsod.pw:2594 -u WALLET.rig -p m=solo Code: -a x16r -o stratum+tcp://pool.bsod.pw:2594 -u WALLET.rig -p m=party.yourpassword NOTICE: You can use us for North America and asia for Asia instead of eu in your .bat file or config Feel free to use our new monitor app for Android https://play.google.com/store/apps/details?id=kg.stark.bsod Feel free to use our new monitor app for IOS https://itunes.apple.com/ru/app/bsod-pw-mining-pool/id1459532591 Be wise. Make profit. Your bsod.pw team.

Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN]✅[IEO] GEXAN - BLOCKCHAIN LOTTERY! [POW+POS+MN]✅[Smart Contracts]

on: April 26, 2019, 06:26:48 PM

BSOD.PW supports Gexan Welcome to the world of happy mining! https://bsod.pw Code: -a phi2 -o stratum+tcp://pool.bsod.pw:2590 -u WALLET.rig You can mine this coin SOLO and PARTY (what is it?) on https://bsod.pw Code: -a phi2 -o stratum+tcp://pool.bsod.pw:2590 -u WALLET.rig -p m=solo Code: -a phi2 -o stratum+tcp://pool.bsod.pw:2590 -u WALLET.rig -p m=party.yourpassword NOTICE: You can use us for North America and asia for Asia instead of eu in your .bat file or config Feel free to use our new monitor app for Android https://play.google.com/store/apps/details?id=kg.stark.bsod Be wise. Make profit. Your bsod.pw team.

Alternate cryptocurrencies / Announcements (Altcoins) / Re: NA

on: March 19, 2019, 01:09:52 PM

BSOD.PW supports Gulden Welcome to the world of happy mining! https://bsod.pw Code: -a scrypt -o stratum+tcp://eu.bsod.pw:2578 -u WALLET.rig You can mine this coin SOLO and PARTY (what is it?) on https://bsod.pw Code: -a scrypt -o stratum+tcp://eu.bsod.pw:2578 -u WALLET.rig -p m=solo Code: -a scrypt -o stratum+tcp://eu.bsod.pw:2578 -u WALLET.rig -p m=party.yourpassword NOTICE: You can use us for North America and asia for Asia instead of eu in your .bat file or config Feel free to use our new monitor app for Android https://play.google.com/store/apps/details?id=kg.stark.bsod Be wise. Make profit. Your bsod.pw team.

Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][POW/POS] VHS: Distributed Computing [0 premine, no presale]

on: March 19, 2019, 10:02:44 AM

BSOD.PW supports VHS Welcome to the world of happy mining! https://bsod.pw Code: -a hex -o stratum+tcp://eu.bsod.pw:2576 -u WALLET.rig You can mine this coin SOLO and PARTY (what is it?) on https://bsod.pw Code: -a hex -o stratum+tcp://eu.bsod.pw:2576 -u WALLET.rig -p m=solo Code: -a hex -o stratum+tcp://eu.bsod.pw:2576 -u WALLET.rig -p m=party.yourpassword NOTICE: You can use us for North America and asia for Asia instead of eu in your .bat file or config Feel free to use our new monitor app for Android https://play.google.com/store/apps/details?id=kg.stark.bsod Be wise. Make profit. Your bsod.pw team.

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

on: March 18, 2019, 05:12:04 AM

Quote from: Jean_Luc on March 17, 2019, 06:28:46 PM

Quote from: stivensons on March 17, 2019, 06:04:15 PM

if you post a release windows , I can test it too

You can test with the release you have.
You can try:

Code:

VanitySearch -gpuId 0 -check 
VanitySearch -gpuId 6 -check (On the 3GB)

Thanks

Tomorow, I will try to set up cuda sdk 10 on a recent hardware (Linux) and see If I can reproduce the issue.

cuda 10

Code:

G:\vanitysearch>vanitysearch   -gpuId 0 -check
GetBase10() Results OK
Add() Results OK : 567.189 MegaAdd/sec
Mult() Results OK : 38.169 MegaMult/sec
Div() Results OK : 4.410 MegaDiv/sec
ModInv()/ModExp() Results OK
ModInv() : 281.352 KiloInv/sec
IntGroup.ModInv() : 8.365 MegaInv/sec
ModMulK1() : 10.770 MegaMult/sec
ModSqrt() 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)!
Check Calc PubKey (full) 1ViViGLEawN27xRzGrEhhYPQrZiTKvKLo :OK
Check Calc PubKey (even) 1Gp7rQ4GdooysEAEJAS2o4Ktjvf1tZCihp:OK
Check Calc PubKey (odd) 18aPiLmTow7Xgu96msrDYvSSWweCvB9oBA:OK
GPU: GPU #0 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
Seed: 1853432973
296.742 MegaKey/sec
ComputeKeys() found 1947 items , CPU check...
GPU/CPU check OK

Code:

G:\vanitysearch>vanitysearch   -gpuId 6 -check
GetBase10() Results OK
Add() Results OK : 556.067 MegaAdd/sec
Mult() Results OK : 35.273 MegaMult/sec
Div() Results OK : 4.104 MegaDiv/sec
ModInv()/ModExp() Results OK
ModInv() : 260.561 KiloInv/sec
IntGroup.ModInv() : 7.773 MegaInv/sec
ModMulK1() : 9.881 MegaMult/sec
ModSqrt() 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)!
Check Calc PubKey (full) 1ViViGLEawN27xRzGrEhhYPQrZiTKvKLo :OK
Check Calc PubKey (even) 1Gp7rQ4GdooysEAEJAS2o4Ktjvf1tZCihp:OK
Check Calc PubKey (odd) 18aPiLmTow7Xgu96msrDYvSSWweCvB9oBA:OK
GPU: GPU #6 GeForce GTX 1060 3GB (9x128 cores) Grid(72x128)
Seed: 2205931314
260.131 MegaKey/sec
ComputeKeys() found 1752 items , CPU check...
GPU/CPU check OK

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

on: March 17, 2019, 06:04:15 PM

Quote from: Jean_Luc on March 17, 2019, 04:55:04 PM Ok Thanks, could you try to run cuda-memcheck on the release version. if you post a release windows , I can test it too

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

on: March 16, 2019, 10:45:49 AM

Code:

G:\vanitysearch>vanitysearch -o done6.txt -t 0 -gpu -gpuId 0,1,2,3,4,5,6 1C3J4uW
Start Sat Mar 16 17:37:13 2019
Difficulty: 15318045009
Search: 1C3J4uW
Base Key:91DCE68637F7B992C3F0C6927E5DD81121A319C8018CE3CF8703CA9AD27ECD6B
Number of CPU thread: 0
GPU: GPU #6 GeForce GTX 1060 3GB (9x128 cores) Grid(72x128)
GPU: GPU #5 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #4 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #0 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #2 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #3 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #1 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
2155.100 MK/s (GPU 2155.100 MK/s) (2^38.99) [P 100.00%][99.00% in 00:00:00][32]

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

on: March 12, 2019, 01:08:05 PM

Code:

G:\vanitysearch>vanitysearch -stop -t 0 -gpu -gpuId 0,1,2,3,4,5,6 1Testtttt
Start Tue Mar 12 20:03:18 2019
Difficulty: 2988734397852221Search: 1Testtttt
Base Key:E04D2ABC020297FCE97546517F7F2B190EFE4A6055B293615B326B03F1857ACB
Number of CPU thread: 0
GPU: GPU #6 GeForce GTX 1060 3GB (9x128 cores) Grid(72x128)
GPU: GPU #0 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)y][0]
GPU: GPU #5 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #3 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #2 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #1 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #4 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
1571.848 MK/s (GPU 1571.848 MK/s) (2^34.87) [P 0.00%][50.00% in 15.3d][0]

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

on: March 07, 2019, 03:20:53 PM

Quote from: Jean_Luc on March 06, 2019, 02:57:02 PM Hello, I published a new release (1.6). No new feature, just performance increase (16% GPU, 50% CPU on my hardware). The performance increase are mainly due to a best ECC calculations ( many thanks to arulbero ) It affects less the GPU because the GPU has no SIMD instructions to speed up the SHA, so the resource goes mainly to it and much less to ECC calculations. Next Step: - Add support for multi prefix search and (-i input.txt) - Optimize CPU/GPU exchange - Add missing ECC optimizations (some symmetries and endomorphism) - Add support for GPU funnel shift that should speed up SHA (but I need to find a board with compute capability >3.5, mine is 3.0). Thanks for testing it I almost reached the same performance with my CPU alone (Intel Core i7-4770 3.4GHz) than oclvanitygen with my GPU (GTX 645) but still 10 days of calculation to reach to prefix I want. good speed increase Code: G:\vanitysearch>vanitysearch -stop -t 0 -gpu -gpuId 0,1,2,3,4,5,6 1Testtttt Start Thu Mar 7 22:17:16 2019 Search: 1Testtttt Difficulty: 2988734397852221 Base Key:AC4A942372FF30E640421B959E6BE9EA97DC872B03041A59F73D9C19A5902F7B Number of CPU thread: 0 GPU: GPU #2 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128) GPU: GPU #1 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)y] GPU: GPU #6 GeForce GTX 1060 3GB (9x128 cores) Grid(72x128) GPU: GPU #0 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128) GPU: GPU #3 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128) GPU: GPU #5 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128) GPU: GPU #4 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128) 1043.526 MK/s (GPU 1043.526 MK/s) (2^34.80) [P 0.00%][50.00% in 23.1d]

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

on: March 04, 2019, 03:27:32 PM

Quote from: stivensons on March 04, 2019, 02:48:08 PM

Code:

--keyspace KEYSPACE
    Specify the range of keys to search, where KEYSPACE is in the format,

	START:END start at key START, end at key END
	START:+COUNT start at key START and end at key START + COUNT
    :END start at key 1 and end at key END
	:+COUNT start at key 1 and end at key 1 + COUNT

I mean, for example, to set a range for creating an address in a specific range, I want to create an address in 2 ^ 135 - 2 ^ 136 with a specific mask

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

on: March 04, 2019, 03:00:59 PM

Quote from: arulbero on March 04, 2019, 01:07:55 PM

To do a comparison with another software, bitcrack (that has a different goal, instead of having a set of same prefix addresses it has as target a set of addresses with funds, but more or less both programs do the same calculations):

https://bitcointalk.org/index.php?topic=4453897.msg49793258#msg49793258

in particular:

Quote

GeForce GTX 1060 3GB = compressed = 60.61 MKeys/s
GeForce GTX 1060 3GB = both = 46.93 MKeys/s

Compressed

Code:

G:\bit\cuBitCrack.exe -c -d 0 1CF1o6DRBpyGXqQXVJHTGiHNVVu54npgHo
[2019-03-04.21:54:29] [Info] Compression: compressed
[2019-03-04.21:54:29] [Info] Starting at: 0000000000000000000000000000000000000000000000000000000000000001
[2019-03-04.21:54:29] [Info] Ending at:   FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
[2019-03-04.21:54:29] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-03-04.21:54:29] [Info] Initializing GeForce GTX 1060 6GB
[2019-03-04.21:54:29] [Info] Generating 262,144 starting points (10.0MB)
[2019-03-04.21:54:29] [Info] 10.0%
[2019-03-04.21:54:29] [Info] 20.0%
[2019-03-04.21:54:29] [Info] 30.0%
[2019-03-04.21:54:29] [Info] 40.0%
[2019-03-04.21:54:29] [Info] 50.0%
[2019-03-04.21:54:29] [Info] 60.0%
[2019-03-04.21:54:29] [Info] 70.0%
[2019-03-04.21:54:29] [Info] 80.0%
[2019-03-04.21:54:30] [Info] 90.0%
[2019-03-04.21:54:30] [Info] 100.0%
[2019-03-04.21:54:30] [Info] Done
GeForce GTX 1060 1083/6144MB | 1 target 58.56 MKey/s (1,473,773,568 total) [00:00:23]

Uncompressed

Code:

G:\bit\cuBitCrack.exe -u -d 0 1CF1o6DRBpyGXqQXVJHTGiHNVVu54npgHo
[2019-03-04.21:53:35] [Info] Compression: uncompressed
[2019-03-04.21:53:35] [Info] Starting at: 0000000000000000000000000000000000000000000000000000000000000001
[2019-03-04.21:53:35] [Info] Ending at:   FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
[2019-03-04.21:53:35] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-03-04.21:53:35] [Info] Initializing GeForce GTX 1060 6GB
[2019-03-04.21:53:36] [Info] Generating 262,144 starting points (10.0MB)
[2019-03-04.21:53:36] [Info] 10.0%
[2019-03-04.21:53:36] [Info] 20.0%
[2019-03-04.21:53:36] [Info] 30.0%
[2019-03-04.21:53:36] [Info] 40.0%
[2019-03-04.21:53:36] [Info] 50.0%
[2019-03-04.21:53:36] [Info] 60.0%
[2019-03-04.21:53:36] [Info] 70.0%
[2019-03-04.21:53:36] [Info] 80.0%
[2019-03-04.21:53:36] [Info] 90.0%
[2019-03-04.21:53:36] [Info] 100.0%
[2019-03-04.21:53:36] [Info] Done
GeForce GTX 1060 1083/6144MB | 1 target 51.94 MKey/s (1,238,368,256 total) [00:00:21]

Both

Code:

G:\bit\cuBitCrack.exe -c -u -d 0 1CF1o6DRBpyGXqQXVJHTGiHNVVu54npgHo
[2019-03-04.21:52:18] [Info] Compression: both
[2019-03-04.21:52:18] [Info] Starting at: 0000000000000000000000000000000000000000000000000000000000000001
[2019-03-04.21:52:18] [Info] Ending at:   FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
[2019-03-04.21:52:18] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-03-04.21:52:18] [Info] Initializing GeForce GTX 1060 6GB
[2019-03-04.21:52:19] [Info] Generating 262,144 starting points (10.0MB)
[2019-03-04.21:52:19] [Info] 10.0%
[2019-03-04.21:52:19] [Info] 20.0%
[2019-03-04.21:52:19] [Info] 30.0%
[2019-03-04.21:52:19] [Info] 40.0%
[2019-03-04.21:52:19] [Info] 50.0%
[2019-03-04.21:52:19] [Info] 60.0%
[2019-03-04.21:52:19] [Info] 70.0%
[2019-03-04.21:52:19] [Info] 80.0%
[2019-03-04.21:52:19] [Info] 90.0%
[2019-03-04.21:52:19] [Info] 100.0%
[2019-03-04.21:52:20] [Info] Done
GeForce GTX 1060 1083/6144MB | 1 target 46.99 MKey/s (1,696,071,680 total) [00:00:34]

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

on: March 04, 2019, 02:48:08 PM

Quote from: Jean_Luc on March 04, 2019, 02:28:11 PM Quote from: stivensons on March 04, 2019, 02:19:09 PM I get the same ~ 580mk\s OK Thank you for the test. With the optimizations suggested by arulbero , with few memory transfer improvements, by adding specific GPU intrinsic (notably the funnel shift that should improve SHA and RIPE performance), I hope to reach 1GK/s on your config. Waiting for a new version Will there be settings like Bitcrack in the future? Code: -i, --in FILE Read addresses from FILE, one address per line. If FILE is "-" then stdin is read Code: --keyspace KEYSPACE Specify the range of keys to search, where KEYSPACE is in the format, START:END start at key START, end at key END START:+COUNT start at key START and end at key START + COUNT :END start at key 1 and end at key END :+COUNT start at key 1 and end at key 1 + COUNT

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

on: March 04, 2019, 02:21:25 PM

Quote from: arulbero on March 04, 2019, 01:07:55 PM To do a comparison with another software, bitcrack (that has a different goal, instead of having a set of same prefix addresses it has as target a set of addresses with funds, but more or less both programs do the same calculations): https://bitcointalk.org/index.php?topic=4453897.msg49793258#msg49793258 in particular: Quote GeForce GTX 1060 3GB = compressed = 60.61 MKeys/s GeForce GTX 1060 3GB = both = 46.93 MKeys/s I will test and write the results

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

on: March 04, 2019, 02:19:09 PM

Quote from: Jean_Luc on March 04, 2019, 12:55:06 PM OK Thanks So it is similar. Could try now vanitysearch -stop -t 0 -gpu -gpuId 0,1,2,3,4,5,6 -g 160,160,160,160,160,160,144 1Testtttt. It we still have same perf, that means that the default setting are rather good. I get the same ~ 580mk\s

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

on: March 04, 2019, 12:49:53 PM

Quote from: Jean_Luc on March 04, 2019, 06:57:54 AM

Done

~580 mk\s

Code:

G:\vanitysearch>vanitysearch -stop -t 0 -gpu -gpuId 0,1,2,3,4,5,6 1Testtttt
Start Mon Mar  4 19:44:19 2019
Search: 1Testtttt
Difficulty: 2988734397852221
Base Key:7AE06275083610799006F50B0FE5BBD967F3DD8F9961CB07C69A006610F1F58D
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #3 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #5 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #4 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #1 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)y]
GPU: GPU #2 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
GPU: GPU #6 GeForce GTX 1060 3GB (9x128 cores) Grid(72x128)fy]
578.045 MK/s (GPU 578.045 MK/s) (2^36.43) [P 0.00%][50.00% in 41.7d]]

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

on: March 04, 2019, 06:55:57 AM

Quote from: Jean_Luc on March 04, 2019, 06:53:05 AM Quote from: stivensons on March 04, 2019, 05:22:58 AM CPU 20-25% OK, thanks. Could you try this release: http[Suspicious link removed] I changed the number of thread per block to 128 and divided by 2 the default number of block per grid. I would like to know if, on your config, it improves performance, it is the same or it is worst ? Thank you link removed , upload to github as test release

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

on: March 04, 2019, 05:22:58 AM

Quote from: Jean_Luc on March 03, 2019, 04:44:45 PM Ok Thanks. So it seems that the CPU is not able to handle the key rate. If i believe the output you give, it seems that your CPU is a dual core ? If you launch the task manager, your CPU is at 100% ? I think I have to optimize the exchange between CPU and GPU. This is also in my task list. A good challenge would be to reach 1GK/s on your config CPU 20-25%

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

on: March 03, 2019, 03:26:03 PM

Code:

G:\vanitysearch>vanitysearch -stop -t 0 -gpu -gpuId 0,1,2,3,4,5,6 1Testtttt
Start Sun Mar  3 22:19:31 2019
Search: 1Testtttt
Difficulty: 2988734397852221
Base Key:F0407AC53C32B6FD85A9EE9AB912B9650426BC87C5FB4470B89FEF71A853CF
Number of CPU thread: 0
GPU: GPU #5 GeForce GTX 1060 6GB (10x128 cores) Grid(160x64)
GPU: GPU #2 GeForce GTX 1060 6GB (10x128 cores) Grid(160x64)
GPU: GPU #0 GeForce GTX 1060 6GB (10x128 cores) Grid(160x64)
GPU: GPU #1 GeForce GTX 1060 6GB (10x128 cores) Grid(160x64)y]
GPU: GPU #3 GeForce GTX 1060 6GB (10x128 cores) Grid(160x64)
GPU: GPU #6 GeForce GTX 1060 3GB (9x128 cores) Grid(144x64)
GPU: GPU #4 GeForce GTX 1060 6GB (10x128 cores) Grid(160x64)
581.006 MK/s (GPU 581.006 MK/s) (2^35.94) [P 0.00%][50.00% in 41.5d]]

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

on: March 03, 2019, 12:37:46 PM

Quote from: Jean_Luc on March 03, 2019, 11:22:29 AM

Multi-GPU support is ready (Release 1.5), I tested it on Linux only, so If a Windows user can test it It would be great.

Example of usage (on a old PC here running Ubuntu 18-04, with 2 Quadro 600 inside):

Code:

$ ./VanitySearch -l
GPU #0 Quadro 600 (2x48 cores) (Cap 2.1) (963.3 MB) (Multiple host threads)
GPU #1 Quadro 600 (2x48 cores) (Cap 2.1) (964.5 MB) (Multiple host threads)

Code:

$ ./VanitySearch -stop -gpu -gpuId 0,1 1Test
Start Sun Mar  3 12:16:26 2019
Search: 1Test
Difficulty: 264104224
Base Key:593CB755EB63B403F247F9890BE2F0FEAB3E9023A779E18A6EA62FD6C3D1FDF5
Number of CPU thread: 1
GPU: GPU #1 Quadro 600 (2x48 cores) Grid(32x64)
GPU: GPU #0 Quadro 600 (2x48 cores) Grid(32x64)
11.009 MK/s (GPU 10.221 MK/s) (2^27.61) [P 53.96%][60.00% in 00:00:03]
Pub Addr: 1Test2JF73wznXjD3LYEfCw4kPqArkvAp
Prv Addr: 5JVb2RQC5APQXti4yaGyNwEyo4phmvm773YaxD6rG9jGyZZtP32
Prv Key : 0x593CB755EB63B403F247F9890BE2F0FEABBF9023A7FBE18A6EA62FD6C3D2BAEE
Check   : 1LZeyhprPQq64ctexwc4Bgo5h15ZSGRWkE
Check   : 1Test2JF73wznXjD3LYEfCw4kPqArkvAp (comp)

Thanks for testing Wink

everything works perfectly

windows-10x64

Code:

G:\vanitysearch>vanitysearch -stop -gpu -gpuId 0,1,2,3,4,5,6 1Testtttt
Start Sun Mar  3 19:31:49 2019
Search: 1Testtttt
Difficulty: 2988734397852221
Base Key:3A7BB2F81F78F539A33498862C05256FA4BFE84B9550082788661B3A48F7DDD6
Number of CPU thread: 1
GPU: GPU #0 GeForce GTX 1060 6GB (10x128 cores) Grid(160x64)
GPU: GPU #2 GeForce GTX 1060 6GB (10x128 cores) Grid(160x64).6661y]
GPU: GPU #6 GeForce GTX 1060 3GB (9x128 cores) Grid(144x64)
GPU: GPU #5 GeForce GTX 1060 6GB (10x128 cores) Grid(160x64)
GPU: GPU #3 GeForce GTX 1060 6GB (10x128 cores) Grid(160x64)
GPU: GPU #1 GeForce GTX 1060 6GB (10x128 cores) Grid(160x64)
GPU: GPU #4 GeForce GTX 1060 6GB (10x128 cores) Grid(160x64)
546.837 MK/s (GPU 545.374 MK/s) (2^35.49) [P 0.00%][50.00% in 44.0d]

Pages: [1] 2 3 4 5 »