The Privacy Layer protects the transaction path. The separate Compliance
Platform governs authorized review and disclosure when private evidence must
be examined.
Why the Privacy Layer exists
Public blockchains provide verifiable settlement, but they can also expose balances, payment amounts, counterparties, and patterns of financial activity. This creates an unacceptable information boundary for many payment, treasury, payroll, and digital-asset products. Clients need transaction confidentiality without losing the ability to:- reconcile product and blockchain state;
- investigate failed or disputed operations;
- support authorized compliance and audit workflows;
- retain control of customer records and accounting;
- move value between public and private environments when required.
Core capabilities
Private balances and transfers
Maintain shielded value and execute protected transfers without exposing
private transaction details as ordinary public payment records.
Public and private movement
Shield value into private state, transfer it within the Privacy Layer, and
withdraw it to a public blockchain address when required.
Integration infrastructure
Use the network-specific Arcane SDK and the supporting services required by
the configured deployment.
Reconciliation evidence
Preserve transaction signatures, confirmation state, private-state scan
progress, and operation history for client operations and support.
Product model
The Privacy Layer is integrated into a client-controlled financial product. End users interact with the client’s interface. The client integration uses the Arcane SDK and deployment services to prepare and execute private transactions.| Layer | Primary responsibility |
|---|---|
| Client interface | Customer experience, authenticated product actions, balances, and transaction status. |
| Client application and storage | Business rules, wallet scope, product records, private-state material required by the integration, and reconciliation. |
| Arcane Privacy Layer | Network-specific SDK, proof and transaction construction, plus the indexing, delivery, or relaying services used by the deployment. |
| Blockchain network | Transaction settlement, confirmation, and public network state. |
The client product remains the system of record. Reconcile a submitted
private transaction with chain confirmation, the required private-state
update, and the client ledger before treating the product action as complete.
Privacy and visibility
The Privacy Layer separates confidential transaction data from the public settlement layer. Private balances and protected operations use private state and cryptographic proofs, while the blockchain verifies and settles the result. Privacy does not remove every public signal. Funding and withdrawal operations that interact with public blockchain addresses remain part of public network state. Clients must also protect integration keys, wallet mappings, product references, logs, and other metadata that could reveal sensitive context. When an approved compliance, audit, support, or investigation workflow needs private evidence, the Compliance Platform provides a separate, scoped review path. The Privacy Layer does not make private transaction data generally visible to platform users.Who the product is for
Product and engineering teams
Add private transaction capabilities to wallets, payment products, and
client applications.
Treasury and payment operations
Operate protected payment, payout, and treasury flows while retaining
reconciliation records.
Support and investigation teams
Trace product status and transaction evidence without using private data as
a general operational analytics feed.
Compliance and audit teams
Use the separate governed review path when specific private evidence is
required for an authorized purpose.
Common use cases
The Privacy Layer can support financial workflows such as:- wallet and stablecoin payments;
- payroll, contributor payments, and partner payouts;
- treasury and corporate payment operations;
- private funding and withdrawal flows;
- protected digital-asset transfers;
- financial actions embedded in client applications.
Product boundary
The Privacy Layer provides transaction privacy infrastructure. It does not replace the client’s:- interface, authentication, or customer accounts;
- business logic, product approvals, or accounting rules;
- database, ledger, or transaction history;
- key-management and application security controls;
- operational monitoring, reconciliation, or support procedures;
- legal, compliance, or risk-management responsibilities.
Stellar and Solana use separate network-specific integration paths. Select
the path that matches the client’s configured network and deployment.
Next steps
How it works
Follow the private transaction path and understand system responsibilities.
Stellar troubleshooting
Diagnose the Stellar wallet, Soroban, private-state, and audit flow.
Solana troubleshooting
Diagnose the Solana wallet, indexer, proof, relayer, and transaction flow.
Compliance Platform
Understand the governed review and disclosure path for private evidence.