You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I observed in the code, stronghold currently support Ed25519 signing and verification in relation to BIP39 mnemonics.
Due to the use of Ed25519 across the board we also need facilities to securely generate Ed25519 key pairs, storing them at rest, sign messages and verify them.
Motivation
Ed25519 has emerged in our discussion to be the selected standard we are gonna use pretty much for every signing purpose.
Requirements
Write a list of what you want this feature to do.
Key generation using good source of entropy (time bounded though);
Non-volatile secure storage of private key;
Memory guarantees for private key;
Sign arbitrary messages;
Verify arbitrary messages -- this may be optional as it is not a "secure" operation, but since the rest it is needed it kinda makes sense to implement this as well.
Open questions (optional)
Similarly to signing, we should establish an encryption standard that we want to establish across the board; so far I am only aware of Keccak-f[1600] sponges used by the Stream guys,
Are you planning to do it yourself in a pull request?
No.
The text was updated successfully, but these errors were encountered:
Description
As far as I observed in the code, stronghold currently support Ed25519 signing and verification in relation to BIP39 mnemonics.
Due to the use of Ed25519 across the board we also need facilities to securely generate Ed25519 key pairs, storing them at rest, sign messages and verify them.
Motivation
Ed25519 has emerged in our discussion to be the selected standard we are gonna use pretty much for every signing purpose.
Requirements
Write a list of what you want this feature to do.
Open questions (optional)
Are you planning to do it yourself in a pull request?
No.
The text was updated successfully, but these errors were encountered: