Skip to content
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

IF: BLS key/signature encoding #2061

Closed
Tracked by #2110
heifner opened this issue Jan 9, 2024 · 0 comments · Fixed by #2255
Closed
Tracked by #2110

IF: BLS key/signature encoding #2061

heifner opened this issue Jan 9, 2024 · 0 comments · Fixed by #2255
Assignees

Comments

@heifner
Copy link
Member

heifner commented Jan 9, 2024

Currently BLS public key and signatures are encoded as base64. This makes it difficult to copy/paste from terminals. Does this provide enough heart-ache to use a different encoding?

base64url would provide an easier to use format. We would want to change our base64url encoder not use the optional trailing = padding to make it easier to use. Specifically with --signature-provider which uses =KEY: as a separator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

5 participants