bft blockchain consensus consistency cryptocurrency cryptography db distributed-systems go

History

Yawning Angel c5cc3c8d3f 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
..
armor	crypto/merkle: remove simple prefix (#4989)	5 years ago
batch	crypto: Use a different library for ed25519/sr25519 (#6526)	4 years ago
ed25519	crypto: Use a different library for ed25519/sr25519 (#6526)	4 years ago
encoding	crypto: add sr25519 as a validator key (#6376)	4 years ago
internal/benchmarking	crypto: API modifications (#5236)	4 years ago
merkle	crypto/merkle: optimize merkle tree hashing (#6513)	4 years ago
secp256k1	p2p: renames for reactors and routing layer internal moves (#6547)	4 years ago
sr25519	crypto: Use a different library for ed25519/sr25519 (#6526)	4 years ago
tmhash	linter: (1/2) enable errcheck (#5064)	5 years ago
xchacha20poly1305	correct spelling to US english (#6077)	4 years ago
xsalsa20symmetric	linters: enable stylecheck (#4153)	5 years ago
CHANGELOG.md	mv go-crypto files to crypto dir	7 years ago
README.md	crypto: reword readme (#5349)	4 years ago
crypto.go	crypto: Use a different library for ed25519/sr25519 (#6526)	4 years ago
doc.go	crypto: delete unused code (#3426)	6 years ago
example_test.go	crypto: delete unused code (#3426)	6 years ago
hash.go	linter: fix nolintlint warnings (#6257)	4 years ago
random.go	remove MixEntropy (#3278)	6 years ago
random_test.go	crypto/random: Use chacha20, add forward secrecy (#2562)	6 years ago
version.go	mv go-crypto files to crypto dir	7 years ago

README.md

crypto

crypto is the cryptographic package adapted for Tendermint's uses

Importing it

To get the interfaces, import "github.com/tendermint/tendermint/crypto"

For any specific algorithm, use its specific module e.g. import "github.com/tendermint/tendermint/crypto/ed25519"

Binary encoding

For Binary encoding, please refer to the Tendermint encoding specification.

JSON Encoding

JSON encoding is done using tendermint's internal json encoder. For more information on JSON encoding, please refer to Tendermint JSON encoding

Example JSON encodings:

ed25519.PrivKey     - {"type":"tendermint/PrivKeyEd25519","value":"EVkqJO/jIXp3rkASXfh9YnyToYXRXhBr6g9cQVxPFnQBP/5povV4HTjvsy530kybxKHwEi85iU8YL0qQhSYVoQ=="}
ed25519.PubKey      - {"type":"tendermint/PubKeyEd25519","value":"AT/+aaL1eB0477Mud9JMm8Sh8BIvOYlPGC9KkIUmFaE="}
sr25519.PrivKeySr25519   - {"type":"tendermint/PrivKeySr25519","value":"xtYVH8UCIqfrY8FIFc0QEpAEBShSG4NT0zlEOVSZ2w4="}
sr25519.PubKeySr25519    - {"type":"tendermint/PubKeySr25519","value":"8sKBLKQ/OoXMcAJVxBqz1U7TyxRFQ5cmliuHy4MrF0s="}
crypto.PrivKeySecp256k1   - {"type":"tendermint/PrivKeySecp256k1","value":"zx4Pnh67N+g2V+5vZbQzEyRerX9c4ccNZOVzM9RvJ0Y="}
crypto.PubKeySecp256k1    - {"type":"tendermint/PubKeySecp256k1","value":"A8lPKJXcNl5VHt1FK8a244K9EJuS4WX1hFBnwisi0IJx"}