foundry voting example<updated> #37
Conversation
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is a critical CVE?Contains a Critical Common Vulnerability and Exposure (CVE). Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
| // but including the vote as a public input is sufficient | ||
|
|
||
| // assert(vote <= 1); | ||
| let merkle_root = std::merkle::compute_merkle_root(note_commitment, index, hash_path); |
There was a problem hiding this comment.
If you want, you can replace the MT with the MTs from zk-kit, this would be a cool example of how they're used
There was a problem hiding this comment.
Just checkout out this package zk-kit, its cool, thanks for sharing it. yes I'll add it here as well.
Description
Updated foundry voting example for Ultraplonk
Problem*
Resolves
Summary*
Additional Context
PR Checklist*
cargo fmton default settings.