You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

33 lines
868 B

crypto: Use a different library for ed25519/sr25519 (#6526) At Oasis we have spend some time writing a new Ed25519/X25519/sr25519 implementation called curve25519-voi. This PR switches the import from ed25519consensus/go-schnorrkel, which should lead to performance gains on most systems. Summary of changes: * curve25519-voi is now used for Ed25519 operations, following the existing ZIP-215 semantics. * curve25519-voi's public key cache is enabled (hardcoded size of 4096 entries, should be tuned, see the code comment) to accelerate repeated Ed25519 verification with the same public key(s). * (BREAKING) curve25519-voi is now used for sr25519 operations. This is a breaking change as the current sr25519 support does something decidedly non-standard when going from a MiniSecretKey to a SecretKey and or PublicKey (The expansion routine is called twice). While I believe the new behavior (that expands once and only once) to be more "correct", this changes the semantics as implemented. * curve25519-voi is now used for merlin since the included STROBE implementation produces much less garbage on the heap. Side issues fixed: * The version of go-schnorrkel that is currently imported by tendermint has a badly broken batch verification implementation. Upstream has fixed the issue after I reported it, so the version should be bumped in the interim. Open design questions/issues: * As noted, the public key cache size should be tuned. It is currently backed by a trivial thread-safe LRU cache, which is not scan-resistant, but replacing it with something better is a matter of implementing an interface. * As far as I can tell, the only reason why serial verification on batch failure is necessary is to provide more detailed error messages (that are only used in some unit tests). If you trust the batch verification to be consistent with serial verification then the fallback can be eliminated entirely (the BatchVerifier provided by the new library supports an option that omits the fallback if this is chosen as the way forward). * curve25519-voi's sr25519 support could use more optimization and more eyes on the code. The algorithm unfortunately is woefully under-specified, and the implementation was done primarily because I got really sad when I actually looked at go-schnorrkel, and we do not use the algorithm at this time.
4 years ago
  1. package batch
  2. import (
  3. "github.com/tendermint/tendermint/crypto"
  4. "github.com/tendermint/tendermint/crypto/ed25519"
  5. "github.com/tendermint/tendermint/crypto/sr25519"
  6. )
  7. // CreateBatchVerifier checks if a key type implements the batch verifier interface.
  8. // Currently only ed25519 & sr25519 supports batch verification.
  9. func CreateBatchVerifier(pk crypto.PubKey) (crypto.BatchVerifier, bool) {
  10. switch pk.Type() {
  11. case ed25519.KeyType:
  12. return ed25519.NewBatchVerifier(), true
  13. case sr25519.KeyType:
  14. return sr25519.NewBatchVerifier(), true
  15. }
  16. // case where the key does not support batch verification
  17. return nil, false
  18. }
  19. // SupportsBatchVerifier checks if a key type implements the batch verifier
  20. // interface.
  21. func SupportsBatchVerifier(pk crypto.PubKey) bool {
  22. switch pk.Type() {
  23. case ed25519.KeyType, sr25519.KeyType:
  24. return true
  25. }
  26. return false
  27. }