The Compliance Platform uses separate flows for transaction activity and disclosure. Arcane observes encrypted on-chain records after a transaction. It does not route the transaction through its backend. This page describes technical data movement. For the case and approval workflow, see How the Compliance Platform works.

​
On-chain transaction and indexing flow

On-chain transaction flow from an application to confidential blockchain transfers, then through the Arcane Indexer to the encrypted data store.
1

Your application submits the transaction

Your wallet, protocol, or application constructs, signs, and submits the confidential transaction directly to the blockchain.
2

The privacy stack executes it

The supported blockchain or privacy stack validates the transaction and produces encrypted state, events, or audit records.
3

Arcane indexes encrypted evidence

The Arcane Indexer observes supported records and extracts encrypted payloads with the metadata needed to locate and interpret them.
4

Arcane stores the encrypted records

The encrypted data store persists the records without receiving disclosure key material or confidential plaintext.

​
Authorization and protected-key-access flow

Disclosure request flow from an Arcane UI or API through authentication and authorization to trusted compute and managed key custody.
A user, customer backend, compliance system, or Arcane interface can start a disclosure request. Arcane authenticates the requester and evaluates the request against organization permissions and disclosure policy. Only an approved request reaches the Trusted Compute Module. The diagram shows the authorization and protected-key-access path. The complete operation also loads encrypted records, returns the approved result, clears sensitive memory, and records an audit event.

​
Authorized disclosure sequence

Authorized disclosure sequence: authenticate and authorize, load encrypted records, perform protected decryption in trusted compute, return scoped data, and record an audit event.
The complete disclosure algorithm is:
1

Submit the request

An authorized user or system requests disclosure through the Arcane UI or API. The request identifies the protected data and requested scope.
2

Authenticate and authorize

Arcane authenticates the requester. It then evaluates organization roles, permissions, policy, and the approved disclosure scope.
3

Load encrypted records

Arcane loads only the relevant ciphertext from the encrypted data store. It forwards the authorized operation and scoped encrypted records to the Trusted Compute Module.
4

Obtain protected key access

The key-management provider permits the approved trusted workload to use the required disclosure key for this operation. The requester and ordinary Arcane services do not receive the key.
5

Perform the protected operation

Approved code parses the network-specific ciphertext and performs the required decryption or reconstruction inside the trusted environment.
6

Return the approved result

Arcane returns only the fields allowed by the authorization decision. It does not persist the returned plaintext during normal operation.
7

Clear and record

The Trusted Compute Module clears sensitive intermediate values after the operation. Arcane records metadata about the disclosure for auditability.
A user, User API client, customer backend, or ordinary Arcane service never receives a disclosure private key. The authorized requester receives only the approved disclosure result.