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

[TASK] Generalize pallet to support non-ECDSA (Schnorr) signatures/keys #683

Open
drewstone opened this issue Jul 14, 2023 · 0 comments
Open
Assignees

Comments

@drewstone
Copy link
Contributor

Issue summary

If we in the future support Schnorr signatures over proposals we should ensure we build up the proper methods for verifying those signatures. Currently, everything is verifying against ECDSA signatures.

I think that it would be wise to have a signature type on the Proposal object to identify what signature a proposal is expecting. This way we can match over verifying it with the right scheme.

Other information and links

There are other areas of the codebase to ensure match with new schemes. Things like key storage, compression/uncompression of keys (if those same topics exist with other schemes). We should go through the codebase and find this logic to generalize over.

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

No branches or pull requests

3 participants