lightclient
lightclient
Currently, there is no logic for the client to send proofs of only the accounts in a particular package (actually, there is no logic for the client to send proof...
Blobs are currently constructed in a naive manner: build a multi-proof for `X` number of accounts, generate `Y` number of transactions, serialize proof. There is one stage that is missing...
There should be an in-depth guide on how to fork this repo and start hacking out your own transaction based EE.
It would be great if there was a single command to benchmark the performance of the EE against several different scenarios (small tree, large tree, many transactions, few, etc) in...
I think it would be beneficial to improve the "pluggability" of proof formats other than the offset-multiproof. I've been trying to open up the design of `Sheth` to allow for...
Right now, the client assumes that if it can successfully send a package to the shard node then the shard node was able to process it. Ideally, it waits until...
The CI system should also be running the wasm binary through scout to make sure everything is still in good shape.
A lot of derive macros in use right now are for testing convenience and should really not be compiling into the WebAssembly binary.
Since the EE does not currently support BLS signature verification, its okay that the client doesn't manage keys and signs transactions. Once add though, the client will need this behaviour.
Sheth should be verifying BLS signature. This likely means that some work needs to be done to add BLS to https://github.com/iden3/websnark.