Optimize usage of privacy management components

[skarred14]

Overview

As a user of the Radish34 use case, I would like to improve performance and availability of the privacy enabled interactions with the Zero Knowledge Service. Currently on a local development set up, it is often required to up the Docker Preferences for resource configs (CPU cores, RAM), in order to ensure successful execution of zero knowledge proofs on the ZKP service that leverages the Zokrates utility. In addition, the privacy of merkle tree service (timber) can be further optimized by increasing the Merkle depth of the tree stored in the Shield contract

Reference

Questions

Assumptions

• This issue's scope of privacy management utility is currently limited to usage of Zokrates. It would be better to limit the scope of this issue to performance of the existing ZKP component by substituting with other modes of performance management

Acceptance

• Measurement and test completion of proof generation and verification times by varying proving schemes
• Measurement and test completion of verification on chain with changes in the Shield contract
• Pluggable options to include additional proving schemes and hashing mechanisms

Tasks

• [ ] Build components in api for secure management of keys used for signing processes
• [ ] Substitute current hashing mechanisms with other mechanisms (Poseidon, Mimc, and Pedersen), with related changes that need to be made with zkp/circuits and contracts/ levels

**Disclaimer: This is a broad stroke and a sample feature request. It would need to be further updated (potentially broken down into further feature requests), based on discussions with other members of the Oasis community

[ognjenkurtic]

Closing due to inactivity and in light of new developments related to Simple Reference Implementation. Feel free to reopen if\when there is a need to revisit this.