Repository navigation
docs: add private balance proofs with EAS, Noir, and Mopro - #731
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
| - **Verifier deployment.** The generated Solidity verifier requires library linking. The scripts generate the verifier from the current verification key and deploy its linked library. | ||
| - **Native bindings.** We generated Swift bindings and verified the complete proof through Swift on macOS. | ||
|
|
||
| The iOS simulator build encountered a transitive `backtrace`/`libc` dependency issue. This balance circuit has not been executed on a simulator or physical phone. The repository records that failure alongside the successful native and Swift host paths. |
There was a problem hiding this comment.
thank you for reporting this!
We will check them
cc @moven0831
| | Merkle depth | Median adapter call | Median peak process memory | | ||
| |---|---:|---:| | ||
| | 8 | 4.62 s | 2.17 GiB | | ||
| | 12 | 6.19 s | 2.26 GiB | | ||
| | 16 | 7.90 s | 2.35 GiB | |
There was a problem hiding this comment.
You can also note that how big is the circuit (e.g. how many constraints)
There was a problem hiding this comment.
Thanks! Added the pre-padding Barretenberg circuit sizes to the table and noted that all three circuits have a padded size of 524,288 (2¹⁹).
Adds a blog post demonstrating private balance proofs using GIWA Dojang’s balance format, EAS, Noir, and Mopro, with Solidity verification. Includes implementation details, host benchmarks, limitations, and reproduction steps.
Summary by CodeRabbit