Arcium

Service overview

What is Arcium?

Arcium is a confidential computing network for running computations on encrypted data and returning verifiable results without exposing the underlying inputs. On robotic.sh, the live integration supports `score-shift-for-learning`: a robot or operator encrypts shift metrics locally, peaqOS submits the computation request, Arcium queues and finalizes it on Solana, and peaqOS stores the computation receipt for audit.

How it works

1. Step 1

   Encrypt shift metrics

   Use the Arcium client to build `encryptedInput` with `ciphertexts`, `publicKey`, and `nonce`. Keep raw fleet data out of the public payload.

2. Step 2

   Order the service

   Search `compute.confidential`, select `arcium-confidential-compute`, and send the public routing fields in `publicInput`.

3. Step 3

   Execute and confirm

   peaqOS calls the Arcium bridge, records the computation receipt, and the paired agent confirms the delivered order.

Adapter operations

• POSTscore-shift-for-learning

  Submit encrypted shift metrics. Returns computationId, queueSignature, finalizationSignature, encryptedOutput, and status.

Integration fields

Wire Arcium into peaqOS

serviceId

arcium:confidential-compute:native

skillKey

arcium-confidential-compute

serviceType

compute.confidential

operation

score-shift-for-learning

public input schema

peaqos.fleet.shift.v1

input.encryptedInput

ciphertexts[7], publicKey, nonce

input.publicInput

schema, machineId, shiftId, policyVersion

output.receipt

computationId, queueSignature, finalizationSignature

output.encryptedOutput

returned to the caller for local decryption

payment

not-required in peaqOS; Solana payer funds Arcium execution

FAQ

Questions agents ask about Arcium

• Does it require an API key?+

  No provider API key is required for the current peaqOS adapter path. The execution path still needs a funded Solana payer for Arcium network costs.

• What does the request include?+

  The request carries encryptedInput for the confidential values and publicInput for routing fields such as machineId, shiftId, schema, and policyVersion.

• What does peaqOS store?+

  peaqOS stores the order, run state, computation ID, queue signature, finalization signature, status, and audit events. Raw machine data stays outside the public payload.

• How does payment work?+

  peaqOS does not collect a separate market payment for this adapter. Arcium queue and callback transactions run on Solana.

• How deterministic are responses?+

  The same encrypted payload and public input produce the same computation request. peaqOS records the returned computation ID and signatures.

• What happens if execution fails?+

  The Arcium bridge error is returned to the agent and stored on the failed order run.