-
Notifications
You must be signed in to change notification settings - Fork 498
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
cant parse - cat 1.txt | xargs -n1 ku | grep hash160 #379
Comments
Note all base58 sequences are valid addresses. The last four bytes of the uudecoded binary form a checksum, which if it fails, rejects the address. There's not enough information here for me to know if that's what's happening due to truncation (and inability to cut-and-paste text from a graphic and my being too lazy to retype addresses if they were full anyway). |
Можете закрыть вопрос , я нашел аналогичное решение |
i copied/paste the text addresses you posted and worked for me cat tmp.txt | xargs -n1 ku | grep hash160 my guess is that there is a cr/lf issue with your file. Did you created in windows? |
yes , i create in windows |
Use something like to this to convert the file to unix/linux format |
The text was updated successfully, but these errors were encountered: