Private transfers
Move value between registered recipients without leaving shielded state.
Protocol behavior is proposed. This release is an interface preview; no funds or wallet signatures are accepted.
Preconditions
- The sender has confirmed spendable notes covering value and fees.
- The recipient has a valid receiving key in the registry.
- The scanner is synchronized and the proving artifacts match the deployed verifier.
Transfer lifecycle
A signed wallet intent is interpreted by the RPC and funded with eligible notes. The proof establishes authorization and value conservation, and binds encrypted output to the registered recipient. A relayer submits the proof for verification.
The reference action creates recipient value, action-asset change, and fee-asset change. The recipient’s scanner discovers its new note; confirmation is complete only after the underlying chain and local index agree.
Transaction status
| Stage | User-facing meaning |
|---|---|
| Preparing | Selecting notes and constructing the witness |
| Proving | Computing the zero-knowledge proof |
| Submitted | Relayer has returned a settlement transaction |
| Confirming | Awaiting the required chain confirmations |
| Completed | Accepted on-chain and indexed |
| Failed | No successful transition; inspect the failure before retrying |
Limits of privacy
The goal is to conceal the internal sender–recipient–amount relationship from public observers. Correlation from deposits, withdrawals, network traffic, or a small anonymity set remains a separate concern.