For each cryptographic primitive abstraction, we should have a testing and benchmarking framework for all of its implementations.

For example, consider the signature scheme APIs where we have a signature generation function and a signature verification function. Both of those functions should have a generic native performance benchmark framework and a constraint measuring framework, along with a randomized testing suite that confirms that all valid signatures are verifiable (and all invalid ones are not).

Requirements

For the cryptographic primitive abstraction we want the following (as library code that can be called by concrete implementations):

1. Correctness Test
2. Native Performance Benchmark
3. Circuit Constraint Measurement

For the concrete implementations, we want to have actual code that runs those frameworks executable by the following:

1. Test: cargo test --release
2. Benchmark: cargo bench + wasm-pack test
3. Constraint Measurement: cargo run --release --bin measure

Primitives

• Signature
• Encryption
• Permutation
• Accumulator
• Key-Agreement Scheme
• Password Hashing