Orders fill at the next oracle post (every 10 minutes), never at a price you can already see. Closes settle the same way. Liquidation when equity falls under 2.5% of position size.
| Lab | In | Out | Blend |
|---|---|---|---|
| Loading | |||
Trajectory
| Side | Size | Collateral | Entry | Mark | Liq. | Funding | P&L | |
|---|---|---|---|---|---|---|---|---|
| Connect a wallet to see your positions. | ||||||||
Tokenized stocks issued by Robinhood on Robinhood Chain, swapped against their Uniswap V3 pools. DEXSI takes a small fee on the input; the pool takes its own.
| Token | Price | 24h | Pool depth | Tier |
|---|---|---|---|---|
| Loading | ||||
The baskets are built around one question: who wins when intelligence gets cheaper? Compute, datacenters and power earn on volume, so they pair with a short on IQ. The labs set the prices, so they pair with a long. Each basket card says which.
Your stocks
| Connect a wallet. |
Vault
The vault is the counterparty to every position. Depositors earn open and close fees, liquidation remainders and net funding, and carry the traders' net P&L.
Deposit
Withdraw
Two steps: request, then withdraw after the next oracle post (≤ 10 min). Refused while open interest would exceed 50% of the remaining vault.
Milestones
Will the index cross a level before a date? Resolved by the oracle, nobody in the loop. Pools are parimutuel: winners split the losing side, less a 2% fee.
Loading
Methodology
Loading
Components
One flagship model per lab, so no vendor dominates the median. The list is versioned and changes are announced before they take effect.
| Lab | Model | Input $/1M | Output $/1M | Blend |
|---|
Execution
Opens and closes are requests that execute at the index posted after them, never at the current one. Nobody can trade on a price they already know, which is what makes it safe to publish every sample. LP withdrawals follow the same rule (request, then withdraw after the next post). Liquidations are immediate at the current index; the keeper fills, settles and liquidates after every post, and anyone else can call those functions too.
Oracle
Every 10 minutes the service reads the public list prices and takes the median blend. The on-chain index is the median sampled at each post, every 10 minutes. The oracle contract refuses a post that moves the index more than 5% from the previous one, and refuses posts closer than 10 minutes apart; a real repricing therefore reaches the index over several posts, which is what gives traders time and makes manipulation uneconomic.
Contracts
API
Read-only JSON, no key: /api/index (spot, TWAP, components, trajectory), /api/history?res=60 (candles, minutes), /api/onchain-history (posts), /api/markets (vault, OI, funding, milestones), /api/account/0x… (positions, shares), /api/stocks, /api/baskets, /api/stocks/quote?in=&out=&fee=&amount=, /api/hyperliquid, /api/keeper.
Risks
The vault can lose money when traders are net right. Positions can be liquidated. A provider can change list prices at any time. The contracts are unaudited. Nothing here is investment advice.