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

Tip: Getting a totally "vain" address #22

Open
richb-hanover opened this issue Jun 8, 2020 · 0 comments
Open

Tip: Getting a totally "vain" address #22

richb-hanover opened this issue Jun 8, 2020 · 0 comments

Comments

@richb-hanover
Copy link

richb-hanover commented Jun 8, 2020

Sometimes I find it hard to locate the desired string in many of the generated public keys. So I extend the search string with a "/" to give a visual separation. For example, search for "DELL/" instead of just "DELL"

If I have time, I will think about piping the output into a filter that only passes along uppercase characters in positions 1..n of the string (to make it even easier to identify).

Since we're talking about vanity here :-) burning a few CPU cycles seems like a good tradeoff. Thanks for making a delightful tool.

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

1 participant