taiga
taiga copied to clipboard
anoma
A framework for generalized shielded state transitions
The compliance constraint is a fixed circuit used to verify resource consumption and creation, along with other common logic. We can use accumulation to aggregate circuits with the same structure...
customer: @mariari performer: @XuyangSong deadline: null estimated: null started: null actual: null completed: null confirmed: null dependencies: - [ ] [Function privacy roadmap](https://research.anoma.net/t/taiga-function-privacy-roadmap/175) - [ ] [recursive zkp dependencies](https://github.com/anoma/anoma-pm-sync/issues/2) -...
customer: @mariari performer: @XuyangSong deadline: null estimated: null started: null actual: null completed: null confirmed: null dependencies: - [ ] --- Based on #246 VP proofs and public inputs are...
As Anoma spec evolved, there might be some inconsistencies between implementation and the spec. It's worth doing several sync rounds once the latest Anoma spec comes out.
Use the native circuit tool provided by Halo2 and other general performance tools to analyze our circuits and improve them.
Now, we have a straightforward blake2s hash circuit implementation, which could be more efficient. A lookup table with 8 bits would help. - [ ] convert the range check to...
We've Implemented a bunch of independent circuits used inside of Taiga.(e.g. conditional_equal, conditional_select, hash_to_curve, note_encryption, blake2 hash, etc, etc.). It would be better to refactor the circuits to an independent...
Create an example to elaborate on the process of minting and burning: - [ ] a simple govern sub-vp to control the minting and burning - [ ] Integrate the...
Create an example to indicate the resource transformation between shielded and transparent.
With the boundary of Taiga now being somewhat well specified, we can cut down a lot of the taiga codebase, and have it be focused on the tasks it actually...
