#phoenix #transaction #privacy-preserving #model #sender #nullifier #merkle-tree #dusk #deposit #commitment

phoenix-circuits

Circuit definitions for Phoenix, a privacy-preserving ZKP-based transaction model

13 releases (5 breaking)

0.6.0 Feb 7, 2025
0.5.0 Dec 18, 2024
0.4.0 Aug 14, 2024
0.3.0 Aug 14, 2024
0.1.0 May 22, 2024

#4 in #nullifier

Download history 80/week @ 2025-08-30 64/week @ 2025-09-06 64/week @ 2025-09-13 77/week @ 2025-09-20 538/week @ 2025-09-27 49/week @ 2025-10-04 43/week @ 2025-10-11 89/week @ 2025-10-18 327/week @ 2025-10-25 319/week @ 2025-11-01 102/week @ 2025-11-08 204/week @ 2025-11-15 145/week @ 2025-11-22 68/week @ 2025-11-29 52/week @ 2025-12-06 11/week @ 2025-12-13

290 downloads per month
Used in 13 crates (via dusk-core)

MPL-2.0 license

100KB
2K SLoC

Phoenix Circuits

Phoenix is the transaction model used by Dusk, an open-source public blockchain with a UTXO-based architecture that allows for the execution of obfuscated transactions and confidential smart contracts.

This library contains the implementation of the Phoenix-circuits, to prove, in zero-knowledge, that the following conditions hold true:

  1. Membership: every note that is about to be spent is included in the Merkle tree of notes.
  2. Ownership: the sender holds the note secret key for every note that is about to be spent.
  3. Nullification: the nullifier is calculated correctly.
  4. Minting: the value commitment for the newly minted notes are computed correctly.
  5. Balance integrity: the sum of the values of all spent notes is equal to the sum of the values of all minted notes + the gas fee + a deposit, where a deposit refers to funds being transfered to a contract.

Dependencies

~6.5MB
~139K SLoC