-
Notifications
You must be signed in to change notification settings - Fork 481
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
xpoint mode & KEYFOUNDKEYFOUND.txt #49
Comments
Is not strange the puzzle 40 is always found in a second with subtracted keya what is your question? |
With the previous version it is working correctly. PrivKey: 00000000000000000000000000000000000000000000000000000080128a4bd6 |
The pubkeys that are writed in KEYFOUNDKEYFOUND.txt are not correct in the last version. They are not in hex format and they also start by 30 instead of 02 or 03. Therefore we can't find the corresponding pubkey index in the original file in order to make the math operation to get the final PrivKey. |
Ohh yes i didn't notice the bug in the publickey, Is alredy solved in this commit 1060958, Can you update your code to check if this fix solve your issue?, BTW don't forget backup your custom file please letme know if it solve the problem for you. |
Yeah it is working now! The pubkeys are correct and I can find the index to do the math operation. I get the right PrivKey at the end! Thanks for the fix! |
Hi Alberto,
I have made a file "40_xpoints.txt" with 1000000 values of the puzzle 40.
After running the xpoint mode with this command: ./keyhunt -m xpoint -f 40_xpoints.txt -n 65536 -t 8 -b 40 -q -R
I get a strange output for the pubkeys on the screen and in KEYFOUNDKEYFOUND.txt.
PrivKey: 6afe8390d6
pubkey: 303237373430313264653064656231376535643837363333303461623039366463
PrivKey: 75ea480456
pubkey: 303262326534306438646334386535303533356432313535346161323666653839
PrivKey: 79e7570856
pubkey: 303336373332653635636336386438323236303832366238323337646135646433
PrivKey: 781bac6bd6
pubkey: 303264336632393866343966663763373766646239363466633466343966396430
PrivKey: 7587523a56
pubkey: 303338633166363239343461383263313730643462303865616432633166386664
PrivKey: 7f2052e956
pubkey: 303361323236396137643365333536636337633762353266316266326566336638
...
The text was updated successfully, but these errors were encountered: