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

Andre_25

newbie

Activity: 18

Merit: 7

Quote from: Andre_25 on September 24, 2021, 09:15:34 AM

Friends, one question, does the Vanity run faster on linux or on Windows?

I currently use it on Windows and I am wondering if it is worth using it on Linux.

Thanks in what can help me

i repeat this question, please help me.
Thanks,

WanderingPhilospher

full member

Activity: 1162

Merit: 237

Shooters Shoot...

Quote from: eozdem on September 24, 2021, 09:50:11 AM

Quote from: WanderingPhilospher on September 24, 2021, 09:46:22 AM

Quote from: eozdem on September 24, 2021, 09:37:02 AM

I have doubt, if it is starting from 1 each time I start, or it is starting from a random private key ...

Code:

./VanitySearch -o /content/drive/MyDrive/sonuc.txt -gpu -i /content/drive/MyDrive/rch.txt -stop -r 100000

Code:

VanitySearch v1.15.4, add BitCrack mode
[keyspace] start= 1
[keyspace] end=FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
Search: 46 addresses (Lookup size 46,[1,1]) [Compressed]
Start at Fri Sep 24 13:14:17 2021
Number of CPU thread: 1
GPU: GPU #0 Tesla P100-PCIE-16GB (56x64 cores) Grid(448x512)

1, every time. The -r flag you are using (-r 100000) is for rekey, not random. So once your GPU checks 100,000,000,000 keys, the threads will shift up by 100,000,000,000/# of threads.

So how can I force it to start from a random key?

The easiest way without recoding yourself, or using my version, is to create a new start range each time you want to start from a different key.

eozdem

full member

Activity: 227

Merit: 100

Quote from: WanderingPhilospher on September 24, 2021, 09:46:22 AM

Quote from: eozdem on September 24, 2021, 09:37:02 AM

I have doubt, if it is starting from 1 each time I start, or it is starting from a random private key ...

Code:

./VanitySearch -o /content/drive/MyDrive/sonuc.txt -gpu -i /content/drive/MyDrive/rch.txt -stop -r 100000

Code:

VanitySearch v1.15.4, add BitCrack mode
[keyspace] start= 1
[keyspace] end=FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
Search: 46 addresses (Lookup size 46,[1,1]) [Compressed]
Start at Fri Sep 24 13:14:17 2021
Number of CPU thread: 1
GPU: GPU #0 Tesla P100-PCIE-16GB (56x64 cores) Grid(448x512)

1, every time. The -r flag you are using (-r 100000) is for rekey, not random. So once your GPU checks 100,000,000,000 keys, the threads will shift up by 100,000,000,000/# of threads.

So how can I force it to start from a random key?

WanderingPhilospher

full member

Activity: 1162

Merit: 237

Shooters Shoot...

Quote from: eozdem on September 24, 2021, 09:37:02 AM

I have doubt, if it is starting from 1 each time I start, or it is starting from a random private key ...

Code:

./VanitySearch -o /content/drive/MyDrive/sonuc.txt -gpu -i /content/drive/MyDrive/rch.txt -stop -r 100000

Code:

VanitySearch v1.15.4, add BitCrack mode
[keyspace] start= 1
[keyspace] end=FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
Search: 46 addresses (Lookup size 46,[1,1]) [Compressed]
Start at Fri Sep 24 13:14:17 2021
Number of CPU thread: 1
GPU: GPU #0 Tesla P100-PCIE-16GB (56x64 cores) Grid(448x512)

1, every time. The -r flag you are using (-r 100000) is for rekey, not random. So once your GPU checks 100,000,000,000 keys, the threads will shift up by 100,000,000,000/# of threads.

eozdem

full member

Activity: 227

Merit: 100

I have doubt, if it is starting from 1 each time I start, or it is starting from a random private key ...

Code:

./VanitySearch -o /content/drive/MyDrive/sonuc.txt -gpu -i /content/drive/MyDrive/rch.txt -stop -r 100000

Code:

VanitySearch v1.15.4, add BitCrack mode
[keyspace] start= 1
[keyspace] end=FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
Search: 46 addresses (Lookup size 46,[1,1]) [Compressed]
Start at Fri Sep 24 13:14:17 2021
Number of CPU thread: 1
GPU: GPU #0 Tesla P100-PCIE-16GB (56x64 cores) Grid(448x512)

Andre_25

newbie

Activity: 18

Merit: 7

Friends, one question, does the Vanity run faster on linux or on Windows?

I currently use it on Windows and I am wondering if it is worth using it on Linux.

Thanks in what can help me

WhyFhy

hero member

Activity: 1438

Merit: 513

In regards to 3000 series cards and LHR
If it isn't memory intensive it's probably not throttled.
Where technically along the lines of sha256 witch is not memory intensive at all.
I have non lhr cards as well that simply don't perform as expected on VS it could be user error but as long as I've been using this program I dont think so.
For now to me tesla's still dominate VS.
I tried a a100 and couldn't get it to work at all.

WanderingPhilospher

full member

Activity: 1162

Merit: 237

Shooters Shoot...

Quote from: NotATether on September 19, 2021, 01:50:04 AM

Quote from: WanderingPhilospher on September 17, 2021, 11:15:29 PM

No, none of my 3070s are LHR. They were part of first batches before companies decided to nerf them. Also, I do believe that all Founder's Editions cards will not implement LHR.

Honestly, that is the only thing I can think of now...unless it's something odd that I haven't read or experienced before.

Do you have any LHR cards lying around so you can make a vanitysearch benchmark between LHR and non-LHR cards?

Surely, somebody had to have run some tests with them by now. Though it doesn't sound like NVIDIA would nerf Vanitysearch (it sounds like they are only nerving stuff like arith ops).

I do not have any LHR cards.

Right, I am wondering if there is something in Vanitysearch that is similar to an eth miner/ethash algo.

NotATether

legendary

Activity: 1568

Merit: 6660

bitcoincleanup.com / bitmixlist.org

Quote from: WanderingPhilospher on September 17, 2021, 11:15:29 PM

No, none of my 3070s are LHR. They were part of first batches before companies decided to nerf them. Also, I do believe that all Founder's Editions cards will not implement LHR.

Honestly, that is the only thing I can think of now...unless it's something odd that I haven't read or experienced before.

Do you have any LHR cards lying around so you can make a vanitysearch benchmark between LHR and non-LHR cards?

Surely, somebody had to have run some tests with them by now. Though it doesn't sound like NVIDIA would nerf Vanitysearch (it sounds like they are only nerving stuff like arith ops).

WanderingPhilospher

full member

Activity: 1162

Merit: 237

Shooters Shoot...

Quote from: Andre_25 on September 17, 2021, 10:42:15 PM

Quote from: WanderingPhilospher on September 17, 2021, 10:15:54 PM

is your card an LHR model/version?

Yes, I just saw that. Undecided

But I understand that all of the 30 series are.

No, none of my 3070s are LHR. They were part of first batches before companies decided to nerf them. Also, I do believe that all Founder's Editions cards will not implement LHR.

Honestly, that is the only thing I can think of now...unless it's something odd that I haven't read or experienced before.

Andre_25

newbie

Activity: 18

Merit: 7

Quote from: WanderingPhilospher on September 17, 2021, 10:15:54 PM

is your card an LHR model/version?

Yes, I just saw that. Undecided

But I understand that all of the 30 series are.

WanderingPhilospher

full member

Activity: 1162

Merit: 237

Shooters Shoot...

Quote from: Andre_25 on September 17, 2021, 08:36:49 PM

Quote from: WanderingPhilospher on September 17, 2021, 08:20:25 PM

Quote from: Andre_25 on September 17, 2021, 08:13:59 PM

Ok, I have done a couple of tests (repeated so as not to be left with a single result and but with it I can average)

I reduced the list of prefixes to 59 (before they were more than a million) and also shortened the prefixes, to 7 letters (before they were 9 letters) and with this if I can get results only with the GPU and i test it only, for 10 minutes

the query was this: (Without CPU)

Code:

vanitysearch.exe -b -gpu -t 0 -o results2.txt -g 2424,128 -i testShort.txt and the results were: 65

with CPU, the query was:

Code:

vanitysearch.exe -b -gpu -t 8 -o results2.txt -g 2424,128 -i testShort.txt and the results were: 126

I do not know what to think,
Perhaps as you said, it is not yet well Optimized for generation 30 cards and therefore, it "depends" a lot on the cpu for a long list and / or Long prefixes.

Either that or your grid size is crazy. Normally it's like 128,256 or 256,512 where the y is normally larger or double the x. you have 2424,128; I've never seen those kind of settings before.

It is the one that, doing many tests, gave me the best results, it is very near to half the cores that the card has.
although, I don't trust that much anymore.

is your card an LHR model/version?

Andre_25

newbie

Activity: 18

Merit: 7

Quote from: WanderingPhilospher on September 17, 2021, 08:20:25 PM

Quote from: Andre_25 on September 17, 2021, 08:13:59 PM

Ok, I have done a couple of tests (repeated so as not to be left with a single result and but with it I can average)

I reduced the list of prefixes to 59 (before they were more than a million) and also shortened the prefixes, to 7 letters (before they were 9 letters) and with this if I can get results only with the GPU and i test it only, for 10 minutes

the query was this: (Without CPU)

Code:

vanitysearch.exe -b -gpu -t 0 -o results2.txt -g 2424,128 -i testShort.txt and the results were: 65

with CPU, the query was:

Code:

vanitysearch.exe -b -gpu -t 8 -o results2.txt -g 2424,128 -i testShort.txt and the results were: 126

I do not know what to think,
Perhaps as you said, it is not yet well Optimized for generation 30 cards and therefore, it "depends" a lot on the cpu for a long list and / or Long prefixes.

Either that or your grid size is crazy. Normally it's like 128,256 or 256,512 where the y is normally larger or double the x. you have 2424,128; I've never seen those kind of settings before.

It is the one that, doing many tests, gave me the best results, it is very near to half the cores that the card has.
although, I don't trust that much anymore.

WanderingPhilospher

full member

Activity: 1162

Merit: 237

Shooters Shoot...

Quote from: Andre_25 on September 17, 2021, 08:13:59 PM

Ok, I have done a couple of tests (repeated so as not to be left with a single result and but with it I can average)

I reduced the list of prefixes to 59 (before they were more than a million) and also shortened the prefixes, to 7 letters (before they were 9 letters) and with this if I can get results only with the GPU and i test it only, for 10 minutes

the query was this: (Without CPU)

Code:

vanitysearch.exe -b -gpu -t 0 -o results2.txt -g 2424,128 -i testShort.txt and the results were: 65

with CPU, the query was:

Code:

vanitysearch.exe -b -gpu -t 8 -o results2.txt -g 2424,128 -i testShort.txt and the results were: 126

I do not know what to think,
Perhaps as you said, it is not yet well Optimized for generation 30 cards and therefore, it "depends" a lot on the cpu for a long list and / or Long prefixes.

Either that or your grid size is crazy. Normally it's like 128,256 or 256,512 where the y is normally larger or double the x. you have 2424,128; I've never seen those kind of settings before.

Andre_25

newbie

Activity: 18

Merit: 7

Ok, I have done a couple of tests (repeated so as not to be left with a single result and but with it I can average)

I reduced the list of prefixes to 59 (before they were more than a million) and also shortened the prefixes, to 7 letters (before they were 9 letters) and with this if I can get results only with the GPU and i test it only, for 10 minutes

the query was this: (Without CPU)

Code:

vanitysearch.exe -b -gpu -t 0 -o results2.txt -g 2424,128 -i testShort.txt and the results were: 65

with CPU, the query was:

Code:

vanitysearch.exe -b -gpu -t 8 -o results2.txt -g 2424,128 -i testShort.txt and the results were: 126

I do not know what to think,
Perhaps as you said, it is not yet well Optimized for generation 30 cards and therefore, it "depends" a lot on the cpu for a long list and / or Long prefixes.

WanderingPhilospher

full member

Activity: 1162

Merit: 237

Shooters Shoot...

Quote

I think it's weird, and that it should give "almost" the same results.

That is odd, only difference I see right away is -t 8 versus -t 0

What you should do, try searching for say 1 prefix, a short one 1KLmA, or something of the sort. Does your GPU find one or no?
Have you found any addresses with just your GPU, before?

Andre_25

newbie

Activity: 18

Merit: 7

Thanks for helping @WanderingPhilospher

I relate the data:
with CPU and GPU

Code:

vanitysearch.exe -b -gpu -t 8 -o results.txt -g 2424,128 -i input.txt
Ignoring prefix "33ETnbLHH" (P2PKH, P2SH or BECH32 allowed at once)
Ignoring prefix "34X4htRFX" (P2PKH, P2SH or BECH32 allowed at once)
Ignoring prefix "3C8jo9mjw" (P2PKH, P2SH or BECH32 allowed at once)
Ignoring prefix "3GwoqxGsY" (P2PKH, P2SH or BECH32 allowed at once)
Ignoring prefix "38dz18J41" (P2PKH, P2SH or BECH32 allowed at once)
Ignoring prefix "3QWY3TyAs" (P2PKH, P2SH or BECH32 allowed at once)
Ignoring prefix "3KcxxV9z6" (P2PKH, P2SH or BECH32 allowed at once)
Ignoring prefix "3QdXcHSgH" (P2PKH, P2SH or BECH32 allowed at once)
Ignoring prefix "3KJgr9Eof" (P2PKH, P2SH or BECH32 allowed at once)
....
..........
..........
............
..............
[Building lookup16 100.0%]
[Building lookup32 100.0%]
Search: 1100540 prefixes (Lookup size 62937) [Compressed or Uncompressed]
Start Fri Sep 17 12:03:01 2021
Base Key: E7F12B7FED9FBE430CA759D3004F54C6319EB8B7D28933B11CB2AF9F07762248
Number of CPU thread: 8
GPU: GPU #0 NVIDIA GeForce RTX 3060 Ti (38x0 cores) Grid(2424x128)
[4.63 Mkey/s][GPU 0.00 Mkey/s][Total 2^23.18][Prob 0.0%][50% in 1.9d][Found 0]
Warning, -633598779 items lost
Hint: Search with less prefixes, less threads (-g) or increase maxFound (-m)
[611.66 Mkey/s][GPU 610.23 Mkey/s][Total 2^40.29][Prob 70.5%][80% in 00:10:02][Found 113]

Results after 35 Min

and NOW, without CPU:
(it is the same query, Except -t)

Code:

vanitysearch.exe -b -gpu -t 0 -o results.txt -g 2424,128 -i input.txt
Ignoring prefix "33ETnbLHH" (P2PKH, P2SH or BECH32 allowed at once)
Ignoring prefix "34X4htRFX" (P2PKH, P2SH or BECH32 allowed at once)
Ignoring prefix "3C8jo9mjw" (P2PKH, P2SH or BECH32 allowed at once)
Ignoring prefix "3GwoqxGsY" (P2PKH, P2SH or BECH32 allowed at once)
Ignoring prefix "38dz18J41" (P2PKH, P2SH or BECH32 allowed at once)
Ignoring prefix "3QWY3TyAs" (P2PKH, P2SH or BECH32 allowed at once)
Ignoring prefix "3KcxxV9z6" (P2PKH, P2SH or BECH32 allowed at once)
Ignoring prefix "3QdXcHSgH" (P2PKH, P2SH or BECH32 allowed at once)
Ignoring prefix "3KJgr9Eof" (P2PKH, P2SH or BECH32 allowed at once)
....
..........
..........
............
..............
[Building lookup16 100.0%]
[Building lookup32 100.0%]
Search: 1100540 prefixes (Lookup size 62937) [Compressed or Uncompressed]
Start Fri Sep 17 13:08:00 2021
Base Key: 926BA4B1C940344A84ACE6BBEFA0CA0898D8A0A03CFC7BE172661EEDA509175
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce RTX 3060 Ti (38x0 cores) Grid(2424x128)
[0.00 Mkey/s][GPU 0.00 Mkey/s][Total 2^-inf][Prob 0.0%][50% in infy][Found 0]
Warning, -633612519 items lost
Hint: Search with less prefixes, less threads (-g) or increase maxFound (-m)
[585.86 Mkey/s][GPU 585.86 Mkey/s][Total 2^40.11][Prob 66.0%][70% in 00:03:52][Found 0]

Results after 30 Min

I think it's weird, and that it should give "almost" the same results.

WanderingPhilospher

full member

Activity: 1162

Merit: 237

Shooters Shoot...

Quote from: Andre_25 on September 17, 2021, 11:35:54 AM

Hello again guys
I leave a new question, please help me to understand.

I am trying multiple options when I launch the vanitysearch, and I realize that if I "execute" it with -t 0 (which is the same as using it without a processor, and therefore, it would only be with a video card) it does not find anything, even after 10 minutes

Testing with a list of 1,000,000 prefixes, each with a size of 9 letters.

on the contrary, if I try with -t 6, there if I find values. (an average of 1 every 10 seconds)

Could it be that in the end only my processor works and not the gpu?
Shouldn't I find something with GPU alone?
thanks

The short answer, yes, you should find something with GPU, especially if you are finding it with CPU.
Long answer, we would need to see your full command line/batch script flags that you are using.

Andre_25

newbie

Activity: 18

Merit: 7

Hello again guys
I leave a new question, please help me to understand.

I am trying multiple options when I launch the vanitysearch, and I realize that if I "execute" it with -t 0 (which is the same as using it without a processor, and therefore, it would only be with a video card) it does not find anything, even after 10 minutes

Testing with a list of 1,000,000 prefixes, each with a size of 9 letters.

on the contrary, if I try with -t 6, there if I find values. (an average of 1 every 10 seconds)

Could it be that in the end only my processor works and not the gpu?
Shouldn't I find something with GPU alone?
thanks

Andre_25

newbie

Activity: 18

Merit: 7

Quote from: WanderingPhilospher

You can play around with the grid size to see if you can tweak out more MKey/s, but here's the deal, IMO, most of these programs were releases prior to 30xx cards so the programs probably do not best optimize the use of the cards GPU structure. I have only used one program that did and that was an OpenCL program versus Cuda.

thanks again friend.

Topic: VanitySearch (Yet another address prefix finder) - page 10. (Read 32072 times)