The Compliance Platform separates confidential transaction execution from encrypted observation and authorized disclosure. Your application submits transactions directly to a supported blockchain or privacy stack. Arcane does not construct, sign, or submit those transactions. Arcane observes encrypted activity, stores encrypted records, and enables approved disclosure through its UI and APIs. Sensitive cryptographic operations run inside the Trusted Compute Module.
Arcane manages disclosure capability. You retain transaction-signing authority and control when your application initiates an on-chain action.
Architecture showing confidential transactions flowing to the blockchain, encrypted events entering Arcane, and authorized disclosure using trusted compute and managed keys.

​
Security properties

The architecture follows five primary security properties.

​
System components

​
Two independent paths

The transaction path and disclosure path remain separate.
  • In the transaction path, your application interacts with the blockchain. Arcane observes the resulting encrypted records.
  • In the disclosure path, an authorized user or system asks Arcane to reveal an approved scope. Arcane performs the protected operation and returns only that result.
This separation keeps Arcane outside the transaction-signing path while still supporting governed access to confidential evidence.

Follow the data flows

Trace encrypted indexing and authorized disclosure from end to end.

Understand trusted compute

Review the isolated execution boundary for protected operations.

Review key management

Learn how Arcane scopes, protects, and uses disclosure keys.

Review the security model

Understand the guarantees and shared responsibilities.