You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With this issue we scope out from #91 the features and issues we want to address in the next zerokit release v0.6.0.
Reported items may change according to any eventual blocker found or re-prioritization of items.
Usage of arkzkey
compare circuit loading performance of a compressed arkzkey vs uncompressed arkzkey and report on the benchmark result, as well as the size of the file
instead of loading the zkey from file, investigate if the zkey can be defined in code, and if so, create a utility crate that accepts 2 inputs, one being the zkey from file, and the zkey defined in code, and compares the two, to return either a true or false. This will help in transparency as the result from the trusted setup is being defined differently.
create a new feature stateless in the rln crate, which has the following requirements
no merkle tree used
exposes only 2 APIs, via FFI and the public module, one to generate proofs (already exists), and one to verify them. Utility functions may be exposed, like the poseidon hasher.
Integrate stateless into rln-wasm, and subsequently, modify the rln-wasm api's to only include utilites, and to generate/verify proofs
rln-wasm
audit the current implementation to find performance pitfalls.
Bump dependencies of wasmer and benchmark against current implementation
TBD: results of the rln-wasm audit
The text was updated successfully, but these errors were encountered:
Bottom line: using uncompressed arkzkey allows you to significantly reduce the program runtime when reading from a file.
But there is a difficulty with the fact that the arkzkey library at this stage supports working only with compressed data, so I added an additional function to allow reading uncompressed keys
With this issue we scope out from #91 the features and issues we want to address in the next zerokit release v0.6.0.
Reported items may change according to any eventual blocker found or re-prioritization of items.
Usage of arkzkey
true
orfalse
. This will help in transparency as the result from the trusted setup is being defined differently.rln
stateless
in the rln crate, which has the following requirementsstateless
into rln-wasm, and subsequently, modify the rln-wasm api's to only include utilites, and to generate/verify proofsrln-wasm
wasmer
and benchmark against current implementationrln-wasm
auditThe text was updated successfully, but these errors were encountered: