#circuit #model #transaction #phoenix #notes #privacy-preserving #deposit

phoenix-circuits

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

13 releases (5 breaking)

new 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

#484 in Magic Beans

Download history 168/week @ 2024-10-22 111/week @ 2024-10-29 116/week @ 2024-11-05 102/week @ 2024-11-12 103/week @ 2024-11-19 93/week @ 2024-11-26 61/week @ 2024-12-03 246/week @ 2024-12-10 434/week @ 2024-12-17 76/week @ 2024-12-24 69/week @ 2024-12-31 26/week @ 2025-01-07 97/week @ 2025-01-14 128/week @ 2025-01-21 97/week @ 2025-01-28 219/week @ 2025-02-04

548 downloads per month
Used in 11 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.

lib.rs:

Phoenix's circuits and gadgets.

Dependencies

~6MB
~129K SLoC