Trion Documentation Options live · Perps in open beta
Browse documentation

Risks and security

In one paragraph: Trion V2 is a derivatives system whose prices come from outside data, whose fills come from other users, and whose code has been reviewed internally but not independently audited. It is live on Robinhood Chain (4663) with USDG collateral: CMPT capped options from the activation time on the status page, traded on the desk at app.trion.market; the CMPT-USD perpetual runs as an open beta with real USDG. This page lists what can go wrong, in the order you are most likely to meet it, so that no later page can be read as a promise of safety. The plain-language disclosures are in Risk disclosures; this page adds the mechanism behind each.

Deployment status, stated plainly

Price and source risks

Liquidity and counterparty risks

Contract and software risks

Network and governance risks

What you should assume

AssumptionReality
"My funds are insured"No. Backstop is finite, possibly zero; for CMPT-USD there is none.
"I can always close"No. You need a counterparty and a healthy price. In the perp beta you also need Trion's matcher to be up.
"Someone else can force-close me if Trion is down"No. In the CMPT-USD beta only Trion's keeper liquidates; there is no permissionless closeout, ADL or slow mode.
"The mark can't be manipulated"In the general design it is bounded to ±0.5% of I and excludes self-quotes, but I itself depends on two signers. In the perp beta the mark is the index.
"The AI knows what I meant"No. It can misread a request. In the desk chat nothing is sent until you click Confirm; a connected MCP app with trion:trade acts on its own reading.
"The beta is play money"No. Beta balances are real USDG; losses and profits are real.
"Passing tests means safe"No. Local flows prove wiring, not security.
"This is audited"No. Internal review only; no independent audit exists.

Reporting problems

No public bug-bounty programme or dedicated security contact is documented in this repository yet; the benchmark statement records the bonded fixing challenge as the formal dispute route and a non-bonded complaints channel as work in progress. Do not send funds to any address claiming to be a Trion support or recovery address.

Source trail: docs/spec/V2_ARCHITECTURE.md §1.2, §2.1, §2.4, §3.6, §4.4, §5.4, §6.1; docs/RELEASE_V2.md §6 (REG-01..REG-14); overdrive/deployments/v2/4663.json (governance, quote, verification anchors); overdrive/deployments/v2/4663.perps.json (market CMPT-USD: closeoutRouterKind: "operator-eoa", zero adlQueue / backstopVault / slowModeEndpoint); overdrive/exchange/web/src/v2-config.ts (getV2PerpsDeployment, getV2OptionsDeployment), wallet.ts (requireV2Chain, switchChain); overdrive/exchange/core/src/deployments.ts (parseVerification), v2-bindings.ts; overdrive/exchange/oracle/src/signer.ts, v2-runtime.ts (assertProcessKeySeparation, rightsApproval), publication-evidence.ts (reserveSignature); overdrive/src/v2/options/OptionEngineV2.sol (severSeries, governanceSettle); overdrive/src/v2/FixingCouncilV2.sol.

Repository-owned documentation · October 2026 · Educational material, not investment advice and not an audit.