The Privacy Layer adds confidential transaction execution to a client application. The client owns the product flow and system of record. Arcane provides the network-specific SDK and supporting infrastructure used to build, submit, and reconcile private operations.
Stellar and Solana use separate network-specific integration paths. Follow the documentation for the configured network; wallet, state, proof, submission, and reconciliation controls are not interchangeable.

​
Execution flow

1

The client application starts the product action

The client collects the user intent and applies its authentication, authorization, product rules, and customer-experience controls.
2

The client integration prepares the operation

The integration selects the configured network and wallet scope, loads the private state required by that network, and retains a stable product reference for reconciliation.
3

The SDK builds the private transaction

The SDK selects the required private inputs, creates the proof, and builds the transaction data from the approved client intent. Inputs must not be changed after proof generation.
4

The operation is submitted and settled

The configured wallet or relayer submits the operation. The blockchain verifies and settles it. Network-specific services then index or deliver the state required by the client integration.
5

The client reconciles product state

The client waits for chain confirmation and the required private-state update before updating its ledger and marking the product action complete.

​
System responsibilities

​
Transaction and product state

Private execution and product accounting are related but separate. The SDK can return a submitted transaction, but the client should not treat the product action as complete until the required state has been reconciled. For each client-visible money movement, the client should preserve:
  • a stable product reference;
  • the relevant wallet scope;
  • amount and asset context;
  • public funding or withdrawal identifiers when applicable;
  • private operation transaction hashes or relayer job identifiers;
  • private-state discovery and confirmation state;
  • status history, retry attempts, and errors.
This gives operations and support teams enough evidence to determine whether a transaction was funded, submitted, confirmed, made available to the required private-state flow, and reflected in the client product.

​
Integration boundary

The Privacy Layer does not own the client’s UI, application routes, sessions, database schema, business records, or ledger. The client application remains the system of record and uses Arcane for private transaction execution.

Stellar troubleshooting

Diagnose the Stellar wallet, Soroban, private-state, and audit flow.

Solana troubleshooting

Diagnose the Solana wallet, indexer, proof, relayer, and transaction flow.