Skip to content

Open question: bech32m version characters #182

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.

Sign up for GitHub

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

Merged
casey merged 1 commit into from
Jan 19, 2026
Merged

Open question: bech32m version characters #182

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions DESIGN.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,14 @@ Open Questions
since deriving a key with an explicit context seems like good practice, but
`ed25519_dalek` doesn't support it.

- *Should bech32m-encoded strings add a version character?* Similar to segwit
addresses, we could add a version character to fingerprints, public keys,
private keys, and signatures. This would allow us to print a better error
message if for some reason these formats change in the future. It seems
unlikely public keys, private keys, and fingerprints would change, but it
does seem conceivable that it might be desirable to add additional data to
signatures, for example, a per-signature timestamp.

Closed Questions
----------------

Expand Down