Skip to main content
The Arcium Network uses Multi-Party Computation (MPC) to execute computations on encrypted data across a Cluster of Arx nodes.
Arcium Network Architecture
  1. MPC eXecution Environments (MXEs)
MXEs group a Solana program, computation definitions, key material, and the Cluster that executes their computations. Each MXE is bound to one Cluster at a time. Its authority can migrate it to another Cluster through key recovery. Each Cluster maintains its own onchain mempool.
  1. arxOS
arxOS is the distributed, encrypted operating system powering Arx nodes and Clusters, responsible for coordinating and executing computations within the Arcium Network. Each node (like a core in a computer) provides computational resources to execute computations defined by MXEs.
  1. Arcis (Arcium’s Developer Framework)
Arcis is the Rust framework and compiler for writing circuits that run with Arcium’s supported MPC protocol.
  1. Clusters of Arx nodes (running arxOS)
Clusters currently run Cerberus, a dishonest-majority, detect-and-abort MPC protocol.
Clusters of Arx nodes

​
Chain-level enforcement

Solana stores network configuration, computation accounts, queues, staking state, payments, and callbacks. Arx nodes keep MPC key material and preprocessing data offchain and execute circuits offchain. Read more in Solana integration: orchestration and execution. Arx nodes stake to activate, join Clusters, receive rewards, and participate in leader selection. See Staking overview.