System architecture
Separate the signer, private computation, and public settlement.
Protocol behavior is proposed. This release is an interface preview; no funds or wallet signatures are accepted.
Execution path
| Component | Responsibility |
|---|---|
| Wallet | Signs the exact action and retains the spending key. |
| Privacy RPC | Interprets supported intents, reads private balances, and selects funding notes. |
| Prover | Builds a witness and proves authorization, membership, encryption, and balance constraints. |
| Relayer | Submits proof data and pays base-chain gas. |
| Pool & verifier | Verify the proof, reject spent nullifiers, and append new commitments. |
| Scanner | Reads events, attempts note decryption, and updates local private state. |
The virtual network
The custom network is a compatibility abstraction. It is not a separate consensus system or a guarantee of cross-chain interoperability. Settlement still depends on the selected base chain and its deployed pool.
A wallet balance on this network represents indexed shielded notes. It is not necessarily the same as the publicly visible balance at the corresponding base-chain address.
Local versus hosted computation
A local RPC and prover keep viewing material on the user’s device. A hosted proxy can improve convenience, but an operator that processes viewing keys can inspect the associated history. Non-custodial spending does not imply that a remote service learns nothing.
Relaying separates the submitting address from the spending wallet. It does not, by itself, eliminate IP logging, timing correlation, or collusion between infrastructure providers.