You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been trying to generate multiple vanity Safe addresses. In particular finding a case sensitive match word (0xca1f vs 0xCA1F). For this it's good to run the script multiple times, until you find the right vanity Safe address. Doing this manually is tedious.
Perhaps it could be mentioned in the README.MD file you could run the script multiple times and write the output to a (text) file. E.g. using this bash one liner.
for i in {1..200}; do ./deadbeef --owner 0x0000000000000000000000000000000000000000 --owner 0x0000000000000000000000000000000000000000 --threshold 1 --prefix 0xCa1f00 >> deadbeef-output.txt; done
This will run deadbeef 200 times and write the output to the same directory in file deadbeef-output.txt. You then can manually case-sensitive search the output file for the desired Safe address.
On my machine it happened to run the tasks in parallel (utilizing all CPUs, also a moment to appreciate https://github.com/aristocratos/btop :) ).
The text was updated successfully, but these errors were encountered:
I've been trying to generate multiple vanity Safe addresses. In particular finding a case sensitive match word (
0xca1f
vs0xCA1F
). For this it's good to run the script multiple times, until you find the right vanity Safe address. Doing this manually is tedious.Perhaps it could be mentioned in the README.MD file you could run the script multiple times and write the output to a (text) file. E.g. using this bash one liner.
This will run
deadbeef
200 times and write the output to the same directory in filedeadbeef-output.txt
. You then can manually case-sensitive search the output file for the desired Safe address.On my machine it happened to run the tasks in parallel (utilizing all CPUs, also a moment to appreciate https://github.com/aristocratos/btop :) ).
The text was updated successfully, but these errors were encountered: