How fluxepay/fluxe works
Fluxe is a privacy-preserving, compliance-aware stablecoin protocol. Clients construct Groth16 proofs for mint, transfer, burn, or compliance-object updates, then submit proofs and public inputs through the HTTP API. The server verifier checks proofs and deterministically replays state changes, including Merkle roots and supply accounting. Core structures cover confidential notes, compliance objects, callbacks, and Merkle state. The README documents the major circuit capabilities; API routing and verifier internals were not sampled, so those connections reflect documented flows rather than inspected handler implementations.
Main entry points: src Transition Circuits · client.rs API Client · state_manager.rs State Manager · server_verifier.rs Deterministic Verifier
Components 14
Client Interface
- API Client
fluxe-api/src/client.rs - HTTP API
fluxe-api/src/api.rs
Proof Construction
- Transition Circuits
fluxe-circuits/src - ZK Gadgets
fluxe-circuits/src/gadgets - Proof Setup
fluxe-circuits/src/setup.rs
Protocol State
- Core Cryptography
fluxe-core/src/crypto - Confidential Notes
fluxe-core/src/data_structures/note.rs - Compliance Objects
fluxe-core/src/data_structures/compliance.rs - Callback Workflow
fluxe-core/src/data_structures/zk_object.rs - Merkle Structures
fluxe-core/src/merkle - State Manager
fluxe-core/src/state_manager.rs - Protocol State
fluxe-core/src/types.rs
Server Processing
- Deterministic Verifier
fluxe-core/src/server_verifier.rs
Other components
- Protocol Client
Connections 19
- Protocol Client → API Client: initiates
- API Client → Transition Circuits: constructs proofs
- Transition Circuits → ZK Gadgets: uses constraints
- Transition Circuits → Core Cryptography: uses primitives
- API Client → HTTP API: submits proofs
- HTTP API → Deterministic Verifier: forwards proof
- Deterministic Verifier → Transition Circuits: verifies proof
- Deterministic Verifier → State Manager: replays operations
- State Manager → Merkle Structures: updates trees
- State Manager → Protocol State: updates roots
- State Manager → Confidential Notes: tracks commitments
- Transition Circuits → Confidential Notes: proves note transitions
- Transition Circuits → Compliance Objects: proves policy
- Transition Circuits → Callback Workflow: checks callbacks
- Transition Circuits → Merkle Structures: proves tree operations
- Deterministic Verifier → Protocol State: recomputes state
- Protocol Client → API Client: queries state
- API Client → HTTP API: requests roots and proofs
- Transition Circuits → Proof Setup: uses setup