ssb-verify-signatures
| Crates.io | ssb-verify-signatures |
| lib.rs | ssb-verify-signatures |
| version | 1.1.1 |
| source | src |
| created_at | 2020-10-16 08:10:07.578783 |
| updated_at | 2021-08-18 10:19:36.000923 |
| description | Verify signatures of scuttlebutt messages. In parallel. |
| homepage | |
| repository | https://github.com/sunrise-choir/ssb-verify-signatures |
| max_upload_size | |
| id | 300434 |
| size | 39,852 |
all (github:sunrise-choir:all)
documentation
https://sunrise-choir.github.io/ssb-verify-signatures/ssb_verify_signatures/index.html
README
ssb-verify-signatures
Verify Secure Scuttlebutt message signatures (in parallel).
How is this different to ssb-legacy-msg?
It's built on top of ssb-legacy-msg and ssb-legacy-msg-data but exposes a hopefully easier
api, and most importantly it lets you batch process a collection of messages.
Batch processing is good for two reasons:
- it means we can utilise multiple cores using rayon
- it means we can use the ed25519_dalek verify_batch function that takes advantage of processor SIMD instructions.
Benchmarks
Benchmarking on a 2016 2 core i5 shows that batch processing with par_verify_messages is ~3.6 times faster than using verify_message
Benchmarking on Android on a One Plus 5T (8 core arm64) shows that batch processing with par_verify_messages is ~9.9 times faster than using verify_message!
Benchmarks can be run with cargo criterion.
License
LGPL-3.0