Trusted Setup Results

[GhostOfGauss]

The trusted setup is complete and so we must:

• Update the prover and verifier keys in manta-parameters
• Publish all ceremony data
• Release verification tools
• Change trusted setup ReadMe to verification instructions

The updated parameters are those generated in the final round (4328) of our trusted setup. They have been checked in the manta-pay simulation to ensure that proofs can indeed be generated and verified using them.

---

Before we can merge this PR, please make sure that all the following items have been checked off:

• Linked to an issue with discussion and accepted design OR have an explanation in the PR that describes this work.
• Added one line describing your change in CHANGELOG.md and added the appropriate changelog label to the PR.
• Re-reviewed Files changed in the GitHub PR explorer.
• Checked that changes and commits conform to the standards outlined in CONTRIBUTING.md.

[GhostOfGauss]

@bhgomes Should we change the manta-pay simulation to load the actual parameters instead of randomly generating them? I started doing this but ran into an issue with the need to specify a temporary directory to use the manta_pay::load_parameters function, so that's a WIP. But maybe we prefer to keep using random ones in the simulation?

[GhostOfGauss]

The list of contribution hashes is a reasonably small file so I decided to add it directly to this repo rather than only hosting it on the AWS s3 bucket with the other files. I placed it in manta-trusted-setup but maybe there's a better place for it?

[GhostOfGauss]

@bhgomes I know you started moving the code to prepare the phase2 parameters from phase1 from manta-trusted-setup to manta-pay but I think that was never merged. For now I've added manta-pay as a dependency to manta-trusted-setup, but that's what we wanted to avoid. Should we move the prepare function to manta-pay in this PR?

[SupremoUGH]

I didn't run the verify binary myself, but I trust you did and it worked as expected, right?

[bhgomes]

@bhgomes Should we change the manta-pay simulation to load the actual parameters instead of randomly generating them? I started doing this but ran into an issue with the need to specify a temporary directory to use the manta_pay::load_parameters function, so that's a WIP. But maybe we prefer to keep using random ones in the simulation?

Can use something like

manta-rs/manta-pay/src/test/compatibility.rs

Line 35 in ca9bef4

let directory = tempfile::tempdir().expect("Unable to generate temporary test directory.");

.