Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not much safer warning #2

Open
k06a opened this issue Oct 18, 2022 · 4 comments
Open

Not much safer warning #2

k06a opened this issue Oct 18, 2022 · 4 comments

Comments

@k06a
Copy link

k06a commented Oct 18, 2022

Hi, it seems your implementation is not MUCH safer than original, see this issue: johguse/profanity#61. Original profanity could be hacked in seconds/minutes with few hours of precompile. I suspect precompile table can be increased thousands of times algorithmically. Using 1000x bigger table and having 1000x more GPU core than average computer would allow to hack every 4000-th vanity address if I count correctly.

Consider calling rd() eight times in a row for achieving 256 bits of non-deterministic seed private key.

Or check out version of @1inch: https://github.com/1inch/profanity2 – it introduces “safety by design” by non-generating any private keys anymore, but finding shift for private key by provided public key of it.

@evmcheb
Copy link
Owner

evmcheb commented Oct 19, 2022

Hey @k06a! Thanks for looking over the repo. I've added your suggested changes, and updated the README to point to 1inch's profanity2.

@k06a
Copy link
Author

k06a commented Oct 19, 2022

Hi @evmcheb BTW, I meant not to use mt19937_64 at all, because it adds nor safety, nor randomness :)

@jacklevin74
Copy link

@evmcheb -- wanted to see if this was fixed.. thanks!

@k06a
Copy link
Author

k06a commented Nov 25, 2022

@jacklevin74 you can use this version https://github.com/1inch/profanity2 to avoid any security concerns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants