This report is meant to be a summary of the current state of Taiga.
They’ve renamed some concepts from the spec,
Resource (previously “Note”)
The object storing one unit of state that can be consumed and produced in transactions.
Compliance Circuit/Proof (previously “Action circuit/proof”)
This is the high-level circuit governing the creation/destruction of Resources
Resource Machine (previously “VP”)
Latest specification has renamed VP to Resource Machines, I will continue to use VP in this document.
The old specification, current codebase, and new specification are all out of sync. Names of concepts are different across all documents and some features are dropped in the latest specification, others have morphed so understanding where exactly Taiga is and where it’s going is a bit unclear. Moreover, it seems like Taiga is not being actively developed anymore, see the Health section for more.
Unimplemented Features
Data Format is tightly coupled with rust and unspecified
Function Privacy is not implemented.
No Recursion / Accumulation / Folding Scheme is currently being used (not even spec’d)
In November, the main engineer developing Taiga said:
optimistically, I may need three months to deliver a workable recursive proof verifier and integrate it to Taiga to achieve function privacy without distraction from other tasks. source
The repository still shows no signs that this work has started beyond upstream work in halo2 to build up support for recursion.
for more, see https://github.com/anoma/taiga/issues/258
A Taiga transaction is composed of a bundle of partial transactions, each of which has two types of proofs:
Each partial transaction has exactly 2 compliance proofs, 4 app VP proofs, unbounded number of dynamic VP proofs