The register, read live.
RPC · public · no wallet neededEvery basket on the floor — leverage against target, NAV per share, state and oracle freshness — numbered and read straight from the vault contracts. Pick a row and operate it in the Terminal.
| № | Basket | Leverage act / tgt | NAV / share | State | Oracles | |
|---|---|---|---|---|---|---|
| Reading chain… | ||||||
minted at NAV · redeemed at NAV · states are deterministic health() outcomes, never an operator's call
Four commands run the whole floor.
no discretion in betweenNumber the basket
Pick 2–8 legs from the price registry, set weights that sum to 100% (no single leg above 50%), choose a leverage target from 1.0× to 3.0×. The factory refuses anything outside the bands — checked on-chain, not in the frontend. Draft one yourself in the Terminal console.
Strike at NAV
The basket compiles to a vault contract. Wrap native ETH, deposit, and the vault strikes shares at the current NAV per share. No lockup, no whitelist — two transactions on first mint: approve, then deposit.
Hold the number
Keepers watch the drift. When actual leverage strays 0.25× from target, anyone may rebalance for a fixed bounty. Oracles mark every leg on a 300-second heartbeat; one stale leg halts the whole floor — failure is loud, never quiet.
Exit at parity
Burn any amount of shares at NAV, any time. Exit terms are declared at minting and can only improve. Selling the share is exiting the strategy — nothing settles off the record.
Mint at NAV. Redeem at NAV.
Parity is the whole pricing model — entry and exit share one number, struck by the vault contract, published every block. See the arithmetic ↗
Seven feeds, one register.
oracle registry · 300 s heartbeatprices are mock feeds on testnet · mainnet path maps to Chainlink stock & ETF data
Who stands under the leverage?
the floor · three answersThe counterparty pool
Liquidity providers deposit WNT and underwrite the synthetic exposure every basket runs on. Leverage never comes from borrowed assets or an off-book desk — it comes from the pool, priced by utilization, visible on the board in real time.
The published order
When a basket lands badly, losses absorb in a declared order — fees first, then the pool's buffer — never at an operator's discretion. The order is fixed in the contracts and cannot be rearranged after the fact.
Anyone, for a bounty
Rebalances and emergency deleverages are permissionless calls with fixed bounties. There is no privileged keeper to bribe or wait for — the floor keeps itself, one bounty at a time.
The deployment ledger.
chain 46630 · unaudited testnet- Network
- Robinhood Chain Testnet — Arbitrum Orbit L2 · chain 46630 · gas in native ETH
- Contracts
- 15 deployments — 6 core contracts, 7 mock feeds, 2 demo baskets · non-upgradeable
- Price feeds
- 7 mock feeds (BTC, ETH, NVDA, TSLA, AAPL, SPY, QQQ) · 300 s heartbeat · Chainlink path mapped
- Baskets
- MIX2X (BTC 50 / ETH 50, 2×) and TECH3X (NVDA 40 / TSLA 30 / SPY 30, 3×) live · backstop pool seeded with WNT
- Next season
- Short weights, liquidation incentives, fuzz & simulation reports · roadmap ↗
Paritex is experimental software on a public testnet. Contracts are unaudited. Leveraged baskets can lose all deposited capital. Nothing here is investment advice.
On the record, in public.
build logs · numbers · releasesOperate, not watch
Connect a wallet on Robinhood Chain Testnet: wrap ETH, mint a basket, redeem at NAV, underwrite the pool. Every write leaves your own wallet — the page holds no keys.
Every rule, numbered
Verified addresses, the five-fact primer, the worked example, the full parameter sheet, FAQ and roadmap — the protocol's whole paper trail, searchable in one page.
Follow the register
Deploys, basket launches and mechanism notes get posted as they ship — @paritex_xyz, same numbers as on this board, no other channel speaks for the protocol.