Pages:
Author

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

newbie
Activity: 13
Merit: 24
Thanks
Could you try: VanitySearch.exe -t 0 -g 16 -gpu 1*1111
I think I've found something.
Suddenly yesterday wildcard started to work well.
Speed 15MK/s is 5-6x slower than normal search which is perfect anyway.
During the time later the program behavior was going by random way. And I've closed firefox. Started to work well again.

In general I guess you could try debug the program in difficult memory conditions.
sr. member
Activity: 462
Merit: 701
Thanks
Could you try: VanitySearch.exe -t 0 -g 16 -gpu 1*1111
newbie
Activity: 13
Merit: 24
Thank you.
Hope to find solution for issue with my GPU. Feel free to contact. I will do everything what I can.

Could you give me the output of command that generate the performance/hanging problem ?


Just any command for wildcard search (* or ? symbols) with -gpu flag. I'm not even sure if the GPU works comparing to 100MK/s in normal mode. The OS is very lagging/hanging at the same time. GTX 750, Win10 and CUDA 10.1.

Quote
>VanitySearch.exe -gpu 1*1111
VanitySearch v1.14
Search: 1*1111 [Compressed]
Start Wed May 15 00:36:03 2019
Base Key: E5E821A5AD352A32F1C86A035864BABAEE2885031ED23CF77F267B63CEF0A5A0
Number of CPU thread: 7
GPU: GPU #0 GeForce GTX 750 (4x128 cores) Grid(32x128)
2.043 MK/s (GPU 0.000 MK/s) (2^24.30) [1]
sr. member
Activity: 462
Merit: 701
Thank you.
Hope to find solution for issue with my GPU. Feel free to contact. I will do everything what I can.

Could you give me the output of command that generate the performance/hanging problem ?
newbie
Activity: 13
Merit: 24
Hi there,

Yes new release is coming but still in dev, I added:
- Case unsensitive search (should run at almost nominal speed)
- Wildcard search (on my hardware ~5 times slower on CPU and GPU compare to single prefix search, mainly due to slow base58 and double sha checksum that have to be computed each time) Still need tests and improvements...
- Crypto Secure RNG for default seed


Thank you.
Hope to find solution for issue with my GPU. Feel free to contact. I will do everything what I can.
However I'm happy already. I can generate quickly a lot of suchlike addresses by VanitySearch (on CPU).
Pub Addr: 1333Q4HANHJM6G6XRGB4HV15LCGSUU93YM
Pub Addr: 1C27MV3VUKHR4FB9V3TXZ3PRRAJR3PCACM
Pub Addr: 1KWF2ZH7D3X7MMWWR56XV347TA9CKRD4CW
sr. member
Activity: 462
Merit: 701
Hi there,

Yes new release is coming but still in dev, I added:
- Case unsensitive search (should run at almost nominal speed)
- Wildcard search (on my hardware ~5 times slower on CPU and GPU compare to single prefix search, mainly due to slow base58 and double sha checksum that have to be computed each time) Still need tests and improvements...
- Crypto Secure RNG for default seed
newbie
Activity: 13
Merit: 24
There are new commits on github.
It is huge work has done there.
Thank you a lot.

I am testing wildcard search now.
It is 10x slower on my CPU.
And 100x slower on GPU with hanging system.
Guess something wrong there.
member
Activity: 117
Merit: 32

Code:
C:\Users\admin\Desktop\vanitygen-0.22-win>VanitySearchCUDA8.exe -gpu 1Testrrr
VanitySearch v1.10
Difficulty: 51529903411245
Search: 1Testrrr [Compressed]
Start Tue May  7 23:57:44 2019
Base Key:46F5C5C6A0516D088A2235E919FCD353E17FB474C15EBFB1166BDB08F74D976E
Number of CPU thread: 7
GPU: GPU #0 GeForce RTX 2080 (46x64 cores) Grid(368x128)
1427.967 MK/s (GPU 1424.946 MK/s) (2^35.46) [P 0.09%][50.00% in 06:55:50][0]


Code:
VanitySearchCUDA10.113.exe -gpu 1Testrrr
VanitySearch v1.13
Difficulty: 51529903411245
Search: 1Testrrr [Compressed]
Start Wed May  8 14:58:24 2019
Base Key: D9B739895D5996F3ECDFCB19B7F7947FBFAF2B9ED9AC2C6E55B8D99591CE4711
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
1419.327 MK/s (GPU 1402.748 MK/s) (2^35.30) [P 0.08%][50.00% in 07:16:45][0]

hello, I would have thought that the difference between the RTX 2080 and the RTX 2070 would have been more important ... you should try with the latest version 1.13 it seems to me that there is a slight increase in speed
jr. member
Activity: 32
Merit: 11

EVGA RTX 2080 XC ULTRA
1427.967 MK/s (GPU 1424.946 MK/s)



Code:
C:\Users\admin\Desktop\vanitygen-0.22-win>VanitySearchCUDA8.exe -check
VanitySearch v1.10
GetBase10() Results OK
Add() Results OK : 116.009 MegaAdd/sec
Mult() Results OK : 10.996 MegaMult/sec
Div() Results OK : 1.900 MegaDiv/sec
ModInv()/ModExp() Results OK
ModInv() Results OK : 145.967 KiloInv/sec
IntGroup.ModInv() Results OK : 2.476 MegaInv/sec
ModMulK1() Results OK : 3.621 MegaMult/sec
ModSquareK1() Results OK : 3.556 MegaMult/sec
ModMulK1order() Results OK : 1.807 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 RTX 2080 (46x64 cores) Grid(368x128)
Seed: 3019516956
1.604 GigaKey/sec
ComputeKeys() found 8735 items , CPU check...

Code:
C:\Users\admin\Desktop\vanitygen-0.22-win>VanitySearchCUDA8.exe -gpu 1Testrrr
VanitySearch v1.10
Difficulty: 51529903411245
Search: 1Testrrr [Compressed]
Start Tue May  7 23:57:44 2019
Base Key:46F5C5C6A0516D088A2235E919FCD353E17FB474C15EBFB1166BDB08F74D976E
Number of CPU thread: 7
GPU: GPU #0 GeForce RTX 2080 (46x64 cores) Grid(368x128)
1427.967 MK/s (GPU 1424.946 MK/s) (2^35.46) [P 0.09%][50.00% in 06:55:50][0]
legendary
Activity: 3500
Merit: 6320
Crypto Swap Exchange
Stock settings on the card.
It's not even using the EVGA drivers, just the latest one from nvidia.
Next time it crashes I will install the EVGA drivers and see if upping voltage helps.

Thanks,
Dave

You might want to use GPU stress tools (such as Furmark) to see whether your GPU is stable/not under heavy load rather.

Also, there's no thing such as EVGA driver. No matter GPU brand usage, you use either Nvidia/AMD driver. I think you're confused with GPU manager / overclock software provided by EVGA.
If you try to download GPU driver from EVGA website, you'll see the download link comes from nvidia.com

Yeah, my bad on wording. I was thinking utility but typed driver.

-Dave
legendary
Activity: 3500
Merit: 6320
Crypto Swap Exchange
A possible issue. I don't know if it's just my setup (probably is)
Offline PC so I don't have exact time of crash BUT it feels to be every 10 days or so.
I came into the office and VS just *stopped* no crash no error just sitting at the command prompt.

8 core CPU that I am running 4 threads on + gpu
Liquid cooled cpu never even gets warm
1200 watt EVGA power supply so I know that's not the issue.

It happened on 1.12 and now on 1.13. I never had the older ones running long enough to see this

What I am running (just restarted it):

C:\Users\Dave\Desktop>vanitysearch -gpu -t 4 1iamdavef
VanitySearch v1.13
Difficulty: 2988734397852221
Search: 1iamdavef [Compressed]


I had this problem. You probably have overclocking the graphics card chip. Although the game may not experience problems and even at work. On 10 day can crash . Lower the GPU frequency or increase the voltage on the video core.

Stock settings on the card.
It's not even using the EVGA drivers, just the latest one from nvidia.
Next time it crashes I will install the EVGA drivers and see if upping voltage helps.

Thanks,
Dave
newbie
Activity: 7
Merit: 1
A possible issue. I don't know if it's just my setup (probably is)
Offline PC so I don't have exact time of crash BUT it feels to be every 10 days or so.
I came into the office and VS just *stopped* no crash no error just sitting at the command prompt.

8 core CPU that I am running 4 threads on + gpu
Liquid cooled cpu never even gets warm
1200 watt EVGA power supply so I know that's not the issue.

It happened on 1.12 and now on 1.13. I never had the older ones running long enough to see this

What I am running (just restarted it):

C:\Users\Dave\Desktop>vanitysearch -gpu -t 4 1iamdavef
VanitySearch v1.13
Difficulty: 2988734397852221
Search: 1iamdavef [Compressed]


I had this problem. You probably have overclocking the graphics card chip. Although the game may not experience problems and even at work. On 10 day can crash . Lower the GPU frequency or increase the voltage on the video core.
legendary
Activity: 3500
Merit: 6320
Crypto Swap Exchange
A possible issue. I don't know if it's just my setup (probably is)
Offline PC so I don't have exact time of crash BUT it feels to be every 10 days or so.
I came into the office and VS just *stopped* no crash no error just sitting at the command prompt.

8 core CPU that I am running 4 threads on + gpu
Liquid cooled cpu never even gets warm
1200 watt EVGA power supply so I know that's not the issue.

It happened on 1.12 and now on 1.13. I never had the older ones running long enough to see this

What I am running (just restarted it):

C:\Users\Dave\Desktop>vanitysearch -gpu -t 4 1iamdavef
VanitySearch v1.13
Difficulty: 2988734397852221
Search: 1iamdavef [Compressed]
Start Sat May  4 10:13:32 2019
Base Key: 49B45ED3DCA15AC7892AA9EF1338DA185DC2D2ABC7730D2A4CB7ED8FD9F73ACB
Number of CPU thread: 4
GPU: GPU #0 GeForce GTX 1080 (20x128 cores) Grid(160x128)
726.926 MK/s (GPU 697.399 MK/s) (2^33.27) [P 0.00%][50.00% in 33.6d][0]

I ran the same thing before. But when I came into the office it was just sitting here:

C:\Users\Dave\Desktop>

Didn't find a thing....

Win10 all updates / 8GB RAM if it matters.

Thanks,
Dave
staff
Activity: 4284
Merit: 8808
Edit: I would just add the nuance that humans especially bad at password generation when they have to recall it, which is not the case here.
They are necessarily bad at it when they must remember it, but they are bad at it by habit otherwise-- at least if they think it's a password.  But really, using the OS is free, there is no reason to not use it in such cases. Smiley
sr. member
Activity: 462
Merit: 701
The OS is going to be much more random than the user, even if the OS has issues.  Moreover, if the user's OS rng is faulty then their security would be totally broken in every other respect as well.

If you want to be paranoid you can combine the OS randomness with user provided keyboard mashing using a cryptographic hash... but please don't just depend on users to provide a truly random value on their own: humans are notoriously bad at it, and that structure reliably results in funds loss.

OK for the paranoid mode.
Edit: I would just add the nuance that humans especially bad at password generation when they have to recall it, which is not the case here.
staff
Activity: 4284
Merit: 8808
OS random number are still coming from PNRG and a failure might always be found on them.
The OS is going to be much more random than the user, even if the OS has issues.  Moreover, if the user's OS rng is faulty then their security would be totally broken in every other respect as well.

If you want to be paranoid you can combine the OS randomness with user provided keyboard mashing using a cryptographic hash... but please don't just depend on users to provide a truly random value on their own: humans are notoriously bad at it, and that structure reliably results in funds loss.
sr. member
Activity: 462
Merit: 701
Every operating system offers a source of cryptographically strong random numbers. Why isn't it using 256-bits (or at least 128 bits) of OS provided entropy?

At the beginning the default seed was used especially to allow the program to be run easily and I always recommend to users to use a seed for generating safe keys. You're right, it is better to suppress the default seed and to force user to use a password or a split key. OS random number are still coming from PNRG and a failure might always be found on them.
staff
Activity: 4284
Merit: 8808
The default seed has an entropy of ~48bit (if you manage to guess the date of the address creation),

That is inexcusably small, and adding a PID to it wouldn't make it meaningfully better.

Strengthening can be a useful tool in the rare case where there isn't any alternative, but it doesn't replace having good entropy to begin with. The only systems that should use weak entropy (plus strengthening) are ones where the unrelated-to-you brute force attackers shouldn't exist (e.g. where they need a secret database to even begin the attack) and where there can be a strong nonce to prevent parallel attack speedups and precomputation.

Every operating system offers a source of cryptographically strong random numbers. Why isn't it using 256-bits (or at least 128 bits) of OS provided entropy?
sr. member
Activity: 462
Merit: 701
Yes if you don't use a seed, for very short prefix. But it will still require lot's of power.
Again, I recommend to use a strong password (-s option) to generate safe base key.

And I recommend to the community not to use this, if he doesn't modify it.

The default seed has an entropy of ~48bit (if you manage to guess the date of the address creation), so to guess a key generated by the default seed used by VanitySearch, you need to execute ~2^48 pbkdf2_hmac_sha512 and to run  ~2^48 times the search up to the desired prefix. I let you do the calculation of the necessary power to compute an address in a feasible time when you know the day of an address creation Wink
But ok, I will modify the code and add the PID, it will add 16 more bits to the default seed entropy.

There are 2 ways to generate safe addresses:

1) Use a strong seed.
2) Use a split key (-sp) with a public key generated by a third party software (In that case, VanitySearch cannot suffer from any vulnerability)
sr. member
Activity: 462
Merit: 701
On page ten of this thread, you concede there is at least one exploit for someone resourceful, assuming you know what you are saying or doing.

Yes if you don't use a seed, for very short prefix. But it will still require lot's of power.
Again, I recommend to use a strong password (-s option) to generate safe base key.
Pages:
Jump to: