Nikolay Volf

Make verification and proving key format implementation-agnostic

2

Currently in zcashd they are just loaded as cpp blob from file? https://github.com/zcash/zcash/blob/871e1726c6d8ebb940f0a51260a00aea0a496bce/src/zcash/JoinSplit.cpp#L80 All should be in json (or other self-describing) format with group elements (alpha/gamma/whatever) stated clearly

Failing test for verify_batch

8

sometimes `verify_batch` return `Ok(_)` on this input, sometimes `Err(_)` Not sure if it is as designed

More flexible chained api

5

in addition to: https://pepyakin.github.io/wasmi/wasmi/struct.ModuleRef.html#method.invoke_export used in the following way ``` instance.invoke_export( "test", &[], &mut NopExternals, ).expect("failed to execute export") ``` something like `instance.export("test").with_externals(&mut NopExternals).with_args(&[]).invoke()` ?

Benching system

7

to address lack of benchmarks, we might want to use special wasm binaries which utilize specific benching api it should consist of: 1. start benchmark (`extern "C" fn start_bench(name_ptr: *const...

Put LEB encoding in separate crate

2

should be no-std and more generic

When generating sections from scratch, initialization from `Vec` for `ImportSection` and others would be handy

and elements::* should be at root

Before function body or initialization expression is accessed, it might be better to store it as a blob, without transforming to the `Vec` and provide just iterator over it (with...