We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
npub checksums add high complexity to implementing the npub display names
are the npub checksums ever used or checked?
if not, we should consider sunsetting them to make implementations simpler and also compatible with bech32m which powers taproot
the only thing i can think of is if someone writes down an npub on paper and gets a character wrong, but I dont think anyone does this?
we could gracefully allow software to be more tolerant, and eventually turn the checksum from a MUST into a SHOULD
also are npubs used for anything other than display on the clients -- hex pubkeys are better to use in general as they are canonical on the back end
The text was updated successfully, but these errors were encountered:
No branches or pull requests
npub checksums add high complexity to implementing the npub display names
are the npub checksums ever used or checked?
if not, we should consider sunsetting them to make implementations simpler and also compatible with bech32m which powers taproot
the only thing i can think of is if someone writes down an npub on paper and gets a character wrong, but I dont think anyone does this?
we could gracefully allow software to be more tolerant, and eventually turn the checksum from a MUST into a SHOULD
also are npubs used for anything other than display on the clients -- hex pubkeys are better to use in general as they are canonical on the back end
The text was updated successfully, but these errors were encountered: