-
Notifications
You must be signed in to change notification settings - Fork 14
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
Misaligned address while searching #2
Comments
Hello! I have some more, regarding this issue. Please check these 3 attempts, using the same keyspace, throwing the same misaligned error at almost the same RUN time of 00:28:50 ~/VanitySearch$ ./vanitysearch -t 4 -gpu -o AVE.txt --keyspace 2B85729B280F12C27:+7FFFFFFFFFF 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5soVanitySearch v1.16 Linux with BitCrack integration ~/VanitySearch$ ./vanitysearch -t 4 -gpu -o AVE.txt --keyspace 2B85729B280F12C27:+7FFFFFFFFFF 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5soVanitySearch v1.16 Linux with BitCrack integration ~/VanitySearch$ ./vanitysearch -t 4 -gpu -o AVE.txt --keyspace 2B85729B280F12C27:+7FFFFFFFFFF 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5soVanitySearch v1.16 Linux with BitCrack integration |
Hello buddy. Firstly, thanks for your awesome tool, I love it that we can choose a range to look into.
Secondly, I wish to report this issue that just happened to me.
It started searching without any issues until it suddenly stopped.
Check details here:
~/VanitySearch$ ./vanitysearch -t 4 -gpu -o out.txt --keyspace 216AA8EB463497B74:+7FFFFFFFFFF 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so
VanitySearch v1.16 Linux with BitCrack integration
[keyspace] start= 216AA8EB463497B74
[keyspace] end= 216AA96B463497B73
Difficulty: 1461501637330902918203684832716283019655932542976
Search: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so [Compressed]
Current task START time: Thu Apr 25 12:54:58 2024
Number of CPU thread: 4
GPU: GPU #0 Tesla T4 (40x64 cores) Grid(320x256)
GPUEngine: Launch: misaligned address1) [01:47:54 RUN || END 02:09:14][0]
Current task END time: Thu Apr 25 14:42:58 2024
The text was updated successfully, but these errors were encountered: