AuditEncodedDigest event that the contract emits after every transaction.
Privacy Pools
Learn how zero-knowledge proofs, commitments, and stealth addresses power private asset transfers on Stellar/Soroban — and how every transaction automatically produces an encrypted audit payload.
Auditing Portal
Learn how the Auditing Portal indexes on-chain audit events, manages disclosure workflows, and gives compliance teams scoped access to interpreted transaction data.
The two domains
Privacy Pools and the Auditing Portal are designed to run independently. Your application can submit on-chain transactions without the Auditing Portal being involved in the execution path. The Auditing Portal can index and manage disclosures for registered contracts without being part of the end-user wallet flow. Each domain has a distinct purpose and a distinct set of components.| Domain | Purpose | Key components |
|---|---|---|
| Privacy Pools | Execute private asset movements on Stellar/Soroban, verify zero-knowledge proofs, and emit encrypted audit data | Soroban contract, Circom circuits, client SDK (PrivacyPoolSDK) |
| Auditing Portal | Index audit events from registered contracts, manage disclosure workflows, and provide compliance teams with scoped transaction review | Arcane Scanner, interpretation worker, backend API, Audit UI |
How they connect
Every time a private transaction is executed on-chain, the Soroban contract emits anAuditEncodedDigest event containing an encrypted audit payload. The Arcane Scanner continuously monitors the Stellar ledger for these events from registered contracts, indexes them, and passes them to the interpretation worker. The Auditing Portal then surfaces the interpreted data to your compliance team through disclosure workflows and scoped case review.
The privacy pool executes transactions independently of the Auditing Portal. The
AuditEncodedDigest event is the only point where the two domains intersect — everything before it is on-chain, and everything after it is off-chain.Personas
Five types of users and integrators interact with Arcane. Each persona has a distinct role, distinct permissions, and a distinct primary tool.| Actor | Role | Primary tool |
|---|---|---|
| End user | Signs and submits private-pool transactions | Your application (built on the Privacy Pool SDK) |
| Privacy-pool integrator | Builds the user-facing application flow around the SDK and the transact entrypoint | Privacy Pool SDK and Soroban contract |
| Auditor | Creates disclosure requests, reviews assigned case transactions, generates reports | Arcane Auditing Portal — application workspace |
| Application Administrator | Reviews and approves disclosure requests, manages case auditors | Arcane Auditing Portal — application workspace |
| Organization Administrator | Manages applications, team members, and organization-level access | Arcane Auditing Portal — organization owner workspace |