Privacy layer

Arcium MPC

SpectraQ uses Arcium threshold-encrypted MPC as the privacy backbone for all strategy computations. This is what enables the Shopify for Quants model — quants keep their alpha, investors get on-chain proof.

Mode
MOCK_MPC
set on agent boot
MXE pubkey
Arcium devnet MXE
Cluster offset
456
Arcium devnet cluster
Recovery set
4
threshold-decryption nodes

Signal computation flow

How a quant's encrypted strategy becomes an on-chain trade

1Encrypt

Agent encrypts the 50-close price window with the MXE threshold pubkey.

2Submit

request_signal_computation lands on-chain. Arcium nodes pick it up.

3Compute

MPC cluster co-computes the MA-crossover. No node sees plaintext state.

4Callback

MXE callback writes the decrypted signal integer into vault.signal_state.

Why MPC enables the Shopify for Quants

Traditional DeFi vaults face a dilemma: publish the strategy (alpha leak) or hide it (investor trust gap). Arcium MPC solves both sides.

For quants

Parameters are encrypted before leaving your machine. The on-chain program and agent never hold plaintext strategy state.

For investors

The computation circuit is fixed and published. Investors can verify that the on-chain signal matches what the quant described — without seeing the parameters.

For the protocol

Every vault's signal path is identical. One audited MPC circuit handles all strategies — reducing attack surface.

MOCK_MPC mode active

Set MOCK_MPC=false on agent restart to see real Arcium callbacks

Agent is running MOCK_MPC=true

The signal is computed locally by the agent instead of being sent to the Arcium cluster. The on-chain trade flow is identical — only the privacy guarantee is bypassed. Restart with MOCK_MPC=false to use the real MXE.

Live Arcium events

Queue txs and callback signals from the agent log

0 events
Loading agent log…