How It Works
4.1 Deposit Phase
A user generates a commitment (hashed secret).
The user deposits funds into the mixer contract along with the commitment.
The deposit is recorded on the blockchain in a Merkle tree.
4.2 Mixing Phase
The mixer contract introduces fake transaction noise.
Withdrawals are time-delayed to prevent transaction correlation.
Funds are pooled, making it impossible to link deposits to withdrawals.
4.3 Withdrawal Phase
The user generates a zero-knowledge proof that confirms ownership of the deposited funds.
A nullifier hash is used to prevent double withdrawals.
Funds are sent to a stealth address that is not linked to the depositor.
Last updated