-
Notifications
You must be signed in to change notification settings - Fork 961
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
Add ECDSA public key format #556
Comments
Is there a specific need for this? In the spec ECDSA is optional and does not seem particularly attractive on its own. |
We don't have any need for this, but let's have an issue open. |
Hi @tomaka , I've started working on this issue. I already have a working implementation compatible with the go-libp2p one but, before PR submission, I would like to ask some opinions wrt multiple curves support. Preliminary:
I was wondering if we would like to keep a door open for more curves that may be inserted in the future. For example: my current implementation has introduced the following function in
Maybe could be good to define a
And then define As I said, for the moment there is only one possibility (i.e. p256), but maybe is a good idea to keep a door open for future extensions. Thank you |
@burdges and @dignifiedquire, as experts on rust crypto, do you have any opinions on this?
I am not too worried making breaking changes at the in-process API level in the future in case we do decide to support other curves. (Quite the opposite for network level breaking changes.) |
* Inform application layer of slow peer * Implement 1.1-like scoring for slow peers * Fix initialisation bug * Add scoring for queue maxing out queue lengths * Appease clippy
libp2p/specs#100
The text was updated successfully, but these errors were encountered: