This page shows the main systems around an Arcane integration.

Actors

ActorUsesMain actions
End userPartner applicationConnects an external Solana wallet and starts product actions
Partner application teamBackend, database, and Solana SDKBuilds private payment flows and stores product state
Support or operations teamPartner backend recordsTracks transaction signatures, status history, and reconciliation state
AuditorAuditing PortalRequests disclosure cases, reviews approved case transactions, and creates reports
Application administratorAuditing PortalReviews disclosure requests, approves or closes requests, and manages case auditors
Organization administratorAuditing PortalManages organization users, applications, and administration boundaries

Systems

SystemOwnerBoundary
Partner frontendPartnerConnects wallet, shows funding instructions, and calls backend APIs
Partner backendPartnerOwns sessions, wallet state, scan state, SDK calls, and product reconciliation
Partner databasePartnerPersists wallet rows, UTXOs, encrypted outputs, scan state, and operation history
Solana SDKArcane package used by partner backendBuilds instructions, scans private state, generates proofs, and submits through relayer
Arcane APIArcaneProvides indexer and relayer APIs used by the SDK
Solana RPCRPC providerReads public balances and confirms transactions
Auditing PortalArcaneSupports scoped disclosure, case review, reports, and access control

Execution boundary

Partner frontend -> Partner backend -> Solana SDK -> Arcane API / Solana RPC
The SDK does not own the partner product model. The partner backend remains the system of record for product state and reconciliation.

Disclosure boundary

Product and transaction evidence -> scoped disclosure workflow -> approved review
The Auditing Portal is separate from the user transaction path.