Signal layer
Arcium MPC
SpectraQ uses Arcium threshold MPC to compute every trading signal. Secrecy alone isn't the point — trades are public, and a simple strategy can be inferred from them. Commitment is: the circuit and its sealed inputs are fixed before the signal exists, and the cluster signs what it computed.
Signal computation flow
How an encrypted price window becomes a signed on-chain signal
Agent encrypts the 50-close price window with the MXE threshold pubkey.
request_signal_computation lands on-chain. Arcium nodes pick it up.
MPC cluster co-computes the MA-crossover. No node sees plaintext state.
MXE callback writes the decrypted signal integer into vault.signal_state.
What MPC gives depositors — and what it doesn't
A strategy you can't inspect is a promise. MPC turns part of that promise into something checkable; the rest is on the roadmap, stated plainly.
Sealed today
The 50-close price window and the strategy threshold travel encrypted under the MXE key. No single node reconstructs them.
Public by design
The circuit is open source, including its moving-average windows (10 and 30 bars). The revealed signal is a single on-chain value, and every trade is visible.
Next
Bind every signal request to a strategy commitment registered on-chain, so the agent can only request signals from the strategy depositors were shown.
Live Arcium events
Queue txs and callback signals from the agent log