bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 17쪽 중 1쪽
# Configuration and security
Source: https://docs.arcium.com/arx-nodes/configuration-and-security
How Node Operators protect Arx node key shares, preprocessing material, hosts, and access credentials
Each Arx node registers its declared **CU capacity** as metadata. Stake requirements determine whether it can activate and join a Cluster; see [Staking overview](/staking/overview).
### Protect key shares
Arx nodes store MPC key shares and preprocessing material offchain. Node Operators are responsible for protecting this data, the host, and access credentials.
When selecting Cluster members, evaluate each Node Operator's hosting, hardware, access controls, and key-management practices offchain.
# Arx nodes overview
Source: https://docs.arcium.com/arx-nodes/overview
Arx node metadata, jurisdiction, and registration on the Arcium Network
When launching an Arx node, the operator provides node metadata and associates the node with a *Node Operator*.
**Node Operators** are metadata entities that represent the party operating one or more Arx nodes.
<Frame>
<img alt="Node Operators and Clusters" />
</Frame>
## Node operators
Node Operators have a one-to-many relationship with Arx nodes, meaning that Node Operators may run multiple nodes. The following metadata fields are associated with a Node Operator:
* **Jurisdiction**: Follows the ISO 3166-1 alpha-2 code standard for jurisdictions, such as `DE` for Germany or `FR` for France.
* **URL**: A webpage representing the Node Operator, such as a website, social profile, or operator reputation page.
These metadata fields are self-declared. The Arcium Network does not verify that the actual hardware location matches the jurisdiction field, but the community can evaluate location claims along with the operator's team, security approach, transparency, and cross-network reputation.
## Metadata
An Arx node's metadata is unique to that specific node and may vary from an associated Node Operator's metadata since a single operator may run multiple nodes in, for example, different jurisdictions.
This node-specific metadata consists of the following fields:
* **IP address**: The node's IPv4 address.
* **Peer ID**: The node's peer identifier in the Multi-Party Computation (MPC) network.
* **Jurisdiction**: The same ISO 3166-1 alpha-2 code standard that Node Operators follow.
As with the Node Operator jurisdiction field, an Arx node's jurisdiction field isn't verified and, therefore, will also be independently evaluated by the Arcium Network's community.
# Performance and incentives
Source: https://docs.arcium.com/arx-nodes/performance-and-incentives
How offchain reputation and stake-weighted rewards affect Node Operators
Customers and delegators evaluate an Arx node's reputation offchain using criteria such as uptime, response time, operational history, and the Node Operator's security practices.
Program rewards follow the Arx node's stake and its Cluster's reward pot.
### Node incentives and rewards structure
Primary stake and third-party delegation contribute to an Arx node's stake-weighted reward share. The Node Operator can also configure a percentage fee on delegated rewards.
Epoch settlement records each Arx node's claim from its Cluster reward pot. Delegators claim their portion after the Node Operator's fee. See [Staking overview](/staking/overview) for settlement details and [Pricing and incentives](/computations/pricing-and-incentives) for customer charges.
Operational reputation informs Cluster invitations and delegation decisions.
# Cluster migration
Source: https://docs.arcium.com/clusters/cluster-migration
How an MXE authority moves an MXE between Clusters through key recovery
An MXE authority can move an MXE from one active Cluster to another through key recovery.
## Migrate an MXE
An MXE binds to one active Cluster at a time. Migration is an explicit action that changes this binding from the current Cluster to a destination Cluster.
The MXE's [Recovery Peers](/getting-started/network-stakeholders#recovery-peers) participate in key recovery so the destination Cluster can continue using the MXE's key material.
Migration changes the MXE's Cluster binding, not an Arx node's membership. An Arx node belongs to one Cluster at a time.
# Incentivization
Source: https://docs.arcium.com/clusters/incentivization
How stake affects Cluster eligibility, reward distribution, and leader selection for Arx nodes
An Arx node's primary and delegated stake determine its stake-weighted reward share and leader weight.
The two types of delegation are:
1. **Self-delegation:** Stake that Node Operators commit to their own Arx nodes.
2. **Third-party delegation:** External stakeholders who delegate their assets to Arx nodes.
## Rewards distribution
Computation rewards accrue in a per-Cluster pot. Epoch settlement records each Arx node's claim as `pot × node_stake / cluster_total_stake`. An Arx node participates in one Cluster at a time.
**Nodes must stake a minimum amount of collateral to participate.**
Node activation and Cluster eligibility have separate primary-stake requirements. See [Staking overview](/staking/overview) for the current floors and settlement behavior.
# Clusters overview
Source: https://docs.arcium.com/clusters/overview
How Cluster authorities assemble Arx nodes and provide execution capacity for MXEs
Clusters are groups of Arx nodes that jointly execute encrypted computations for MPC eXecution Environments (MXEs).
A Cluster is created with an authority, target Arx node count, mempool size, and initial CU price. The mempool size determines the separate mempool and executing-pool account sizes.
The Cluster account records its authority, target node count, CU price, pending invitations, and joined Arx nodes.
The authority invites Arx nodes separately. Each invited Node Operator accepts or declines, and every joining Arx node must meet the applicable [stake floor](/staking/overview). The program does not maintain a node-priority order or automatically replace unavailable Arx nodes.
The authority evaluates reputation, jurisdiction, and hosting security offchain when choosing whom to invite.
### Cluster participation and MXE initialization
After enough Arx nodes join and agree on the aggregated BLS public key, the Cluster authority activates the Cluster.
An MXE binds to one active Cluster, while the Cluster authority manages Arx node membership separately.
### Parallelization and scalability
Every computation is jointly executed by the Arx nodes in its Cluster. A Cluster can execute different non-conflicting computations concurrently when resources and preprocessing data are available. For queue behavior, see [Solana integration: orchestration and execution](/solana-integration-and-multichain-coordination/solana-integration-orchestration-and-execution).
# Permissioned clusters
Source: https://docs.arcium.com/clusters/permissioned-clusters
How Cluster authorities control membership and assemble internal, mixed, or external node sets
Every Cluster uses authority-gated membership. The Cluster authority invites Arx nodes, and each invited Node Operator accepts or declines.
Organizations can use this mechanism to assemble different operating models:
1. **Internal:** Invite only Arx nodes controlled by the organization.
2. **Mixed:** Invite both internal and selected external Arx nodes.
3. **External:** Invite eligible Arx nodes operated by third parties.
All three operating patterns use the same authority-gated membership mechanism onchain.
### Fully-permissioned clusters
An organization can invite only self-operated Arx nodes, giving it operational control over the hosts. The organization remains responsible for assessing its legal and industry requirements.
Despite the isolation, fully permissioned Clusters still use the Arcium program for onchain coordination, Cluster-level base-price voting, and fee distribution.
### Partially-permissioned clusters
An organization can combine its own Arx nodes with selected external operators. All members participate as peers in the same MPC protocol.
### Use external clusters
An authority can invite Arx nodes operated by unrelated third parties. Membership remains invitation-based, and eligibility still requires registration and sufficient stake.
Every joining node must meet the network's stake requirements; see [Sybil resistance](/clusters/sybil-resistance) for how these gates raise the cost of coordinated control.
A broader operator set can reduce dependence on one organization. Authorities should verify operator independence during selection.
# Sybil resistance
Source: https://docs.arcium.com/clusters/sybil-resistance
How Proof of Stake requirements raise the cost of Sybil attacks in the Arcium Network
Sybil attacks involve a single entity creating multiple false identities to disproportionately influence the network. Arcium's defense is Proof of Stake: every identity an attacker controls must be backed by real stake.
The program enforces these stake gates today:
* **Node activation**: activating an Arx node requires a primary self-delegation of 1,000 ARX. See the [Staking overview](/staking/overview).
* **Cluster eligibility**: joining a Cluster requires meeting the primary-stake floor for its mempool size. Because activation already requires 1,000 ARX, the effective minimum ranges from 1,000 to 10,000 ARX. The program checks the floor when an Arx node is invited and when its operator reduces primary stake.
* **Authority-gated membership**: Cluster membership is invitation-based. The Cluster authority chooses which Arx nodes to invite, and each Node Operator accepts or declines. See [Permissioned Clusters](/clusters/permissioned-clusters).
These gates make each participating identity costly. Base-price voting gives each Cluster member one vote, so every additional voting identity must independently satisfy activation and Cluster eligibility.
These controls raise the cost of coordinated identities. Cluster authorities can add offchain operator due diligence when membership independence matters.
# Computation tasks
Source: https://docs.arcium.com/computations/computation-tasks
Computation Units (CUs), task structure, and how computations are measured on Arcium
The **Computation Unit (or CU)** is a Network-wide constant that represents a fixed amount of computational work.
The CU is the smallest unit of computation in the Arcium Network, and all types of arithmetic operations on the Arcium Network (that Computations are made up of) are measured in CUs.
In particular, Computation base pricing uses CUs to set a baseline for Arx node compensation.
## Types of computation tasks
In the Arcium Network, computations fall into two broad categories:
**1) System Computations,** and
**2) Customer Computations**.
These task types serve different purposes on the Network, the first relating to the network's internal operations, and the latter handling external customer requests.
## System computations
System Computations are critical processes automatically generated by the network to maintain its health and operation. They include:
* **Distributed Key Generation (DKG) Computations**: Each Arx node within a Cluster receives a fragment of the overall cryptographic key, known as a key share. These key shares collectively form the key for the MPC eXecution Environment (MXE) in that Cluster, enabling secure joint computation tasks without revealing individual inputs.
* **Key-recovery and migration computations**: Support MXE key recovery during Cluster migration (see [Cluster migration](/clusters/cluster-migration)). These computations let an MXE resume on a destination Cluster without re-keying from scratch.
## Customer computations
Customer Computations are tasks submitted by **Computation Customers** to execute private and confidential operations. These tasks are highly configurable to meet the diverse needs of developers and businesses.
# Defining and commissioning computations
Source: https://docs.arcium.com/computations/defining-and-commissioning-computations
How to register a circuit as a computation definition and commission it for execution on Arcium
Before commissioning a computation, register its circuit as a **Computation Definition** on an MXE.
The definition stores:
1. **Circuit source:** The onchain or offchain source used to load the compiled circuit. Local sources are reserved for internal MXE circuits.
2. **Circuit interface:** The circuit definition and parameter signature produced by the Arcis toolchain.
3. **CU amount:** The amount used to calculate base and priority charges.
4. **Lifecycle state:** The slot when the definition was explicitly deactivated, when applicable.
The MXE's Solana program defines authorization and validates callers and inputs before queueing a computation.
## Commissioning a computation
Commissioning creates a computation account and queues it against the MXE's Cluster.
Key steps in commissioning include:
1. **Provide arguments:** Pass the plaintext and encrypted inputs expected by the Arcis instruction.
2. **Choose a priority price:** Higher values improve queue position; queued computations remain subject to the mempool's 180-slot expiry.
3. **Configure callbacks:** Define the onchain instructions for successful and failed outcomes.
4. **Queue the computation:** Add the computation account to the Cluster's mempool.
When a valid leader choice is available, it can take one dispatch slot. Otherwise priority-fee and account-lock ordering apply. See [Leader weight](/staking/overview#leader-weight).
# Lifecycle of an Arcium computation
Source: https://docs.arcium.com/computations/lifecycle-of-an-arcium-computation
How computations transition from definition to commissioning, execution, and completion
The **Computation Lifecycle** in the Arcium Network governs how computations transition from definition to execution and completion. This structured process ensures reliable coordination, resource optimization, and precise post-execution handling.
## Lifecycle overview
The lifecycle of a computation in the Arcium Network follows a clear progression of steps. These steps ensure computations are securely defined, efficiently commissioned, and accurately executed.
Here are the five key stages:
1. **Definition**: A computation is defined within the context of an MXE, providing a blueprint for its execution (see the [Defining and commissioning computations section](/computations/defining-and-commissioning-computations) for details). This includes specifying inputs, outputs, logic, versioning, and access permissions.
2. **Commissioning**: A defined computation is instantiated by specifying arguments, callback requirements, and fee parameters required for queueing.
3. **Mempool Placement**: Commissioned computations are queued in the Cluster's mempool, where they stay eligible until a Node picks them up or they expire after 180 slots. If a computation is still queued when it expires, the payer can reclaim its computation fee.
4. **Execution**: Nodes execute the computation securely, ensuring privacy and accuracy.
5. **Post-Execution Callbacks**: Following execution, actions defined for success or failure cases are carried out so downstream programs can update state or notify clients.
## Post-execution callbacks
Once a computation is executed, the system triggers callbacks based on the outcome:
* **Success Callbacks**: Handle actions for successfully executed computations. These may include:
* **Dynamic Onchain Actions**: Triggering onchain processes based on computation results.
* **Static Onchain Actions**: Fixed onchain processes to address success scenarios.
* **Failure Callbacks**: Manage actions when a computation fails. These are always static and include:
* **Static Onchain Actions**: Fixed onchain processes to address failure scenarios.
Callbacks ensure that the system remains flexible and responsive, even in the event of unexpected outcomes.
# Pricing and incentives
Source: https://docs.arcium.com/computations/pricing-and-incentives
Base pricing, priority fee markets, and economic incentives for Node Operators
Computation charges combine the Cluster's base price, an optional priority price, and a fixed reserve for submitting the callback transaction.
## Base pricing
Each Cluster has a base price per [Computation Unit (CU)](/computations/computation-tasks). The program multiplies this price by the Computation Definition's CU amount and rounds down to lamports.
## Computational units
The execution cost of a computation is measured in CUs. The Computation Definition stores the CU amount used for pricing.
The cost per CU is determined for each epoch through a voting process. Node Operators cast one vote per Arx node to decide the price of a CU in the upcoming epoch. Abstaining counts as a vote for maintaining the current price.
Voting authority belongs to each Arx node's Node Operator.
The resulting CU price becomes the Cluster's base price for the next epoch. Customers can add a priority price when commissioning a computation.
## Priority fee markets
Priority prices raise a computation's position in its Cluster's mempool. Queued computations remain subject to the mempool's 180-slot expiry.
Priority-fee ordering is scoped to the Cluster's mempool. Computations compete only with other computations queued for the same Cluster, which prevents unrelated tasks from interfering with resource allocation.
When a valid leader choice is available, it can take one dispatch slot. Otherwise the program uses priority-fee and account-lock ordering. See [Leader weight](/staking/overview#leader-weight).
## Economic incentives for Arx nodes
Base and priority charges contribute to computation revenue. The program allocates this revenue to Cluster members, Recovery Peers, and the protocol fee pool as described in [Fee allocation](/staking/overview#fee-allocation).
Stake lockups commit Node Operators and delegators for a minimum period.
## Cluster-level competition
Fee competition is local to a Cluster. Computations in different Clusters have independent fee markets.
## How customers optimize costs
The customer charge includes:
* The Cluster's base price multiplied by the computation's CU amount
* The selected priority price multiplied by the computation's CU amount
* Callback priority cost based on the callback compute budget
* A fixed callback submission reserve that scales with the Cluster's Arx node count
Computation Customers can optimize their costs by carefully managing execution parameters:
1. **Choose submission timing:** Submit non-urgent work when demand is lower.
2. **Set the priority price:** Increase it when queue position matters, while accounting for the callback compute budget.
# Queue ordering and fault handling
Source: https://docs.arcium.com/computations/queue-ordering-and-fault-handling
How queue ordering, expiry, and Cerberus fault detection affect computation liveness and results
Queue rules determine which computation executes next, while Cerberus protects integrity after execution begins. Applications should handle queue expiry and failed execution as normal lifecycle outcomes.
## Order queued computations
Priority prices, account-lock ordering, and an optional leader choice determine which computation is selected from a Cluster's mempool. A queued computation can expire after 180 slots if it is not promoted for execution. The payer can then reclaim its computation charge.
These rules make ordering explicit. Applications can resubmit or apply their own fallback after queue expiry.
## Handle execution faults
Once execution begins, [Cerberus](/multi-party-execution-environments-mxes/mpc-protocols) detects protocol faults and aborts instead of producing a corrupted result under its stated trust assumption.
For a failed computation, the program allocates half of the base-plus-priority프로젝트로 돌아가기