Menu

Roadmap

The complete sequence: platform foundations, operational hardening, testnet, contract upgrades, terminal and API, security, mainnet, token utility and research.

Current release: browser-based practice trading. The infrastructure and on-chain stages below are plans for PUSHIN.

Platform foundations

C-VIX 30D index

A constant 30-day volatility index based on BTC and ETH options. PUSHIN currently displays generated practice values.

Planned

Funding data sources

Normalise Binance, Hyperliquid and Lighter rates to an eight-hour basis. Live collection is planned.

Planned

Simulation venue

Browser-local market and limit orders, virtual balances, positions and trade history.

Available locally

Session keys

A scoped authorisation design for a future relayer. Local practice accounts do not request signatures.

Planned

Settlement contracts

Specify the payout vault, oracle dampener, skew fees and settlement invariants.

Planned

Chain venue in the relayer

Planned keeper, settler, indexer and liquidator services.

Planned

Testnet release

Deploy and verify PUSHIN contracts before any public on-chain trading.

Planned

Production stack

The frontend is hosted on Vercel. A relayer and persistent database remain to be integrated.

Planned

$PUSHIN token

Token deployment, supply and distribution must be confirmed before a launch.

Planned

Harden the live venue

Alerting

Uptime checks on the health endpoint, the relayer's heartbeat and the keeper's and relayer's gas balances, paging a person instead of writing a log line.

Planned

Error reporting

Exceptions from the web app and the relayer collected within one system, each with the request or round that caused it.

Planned

Automated integration checks

Typecheck, lint, the core and contract suites, ABI drift, Slither and a production build on each push, and the API end-to-end suite against each preview. At present, each check is run by hand.

Planned

Rate limits

Per-address and per-IP limits on orders, sessions, nonces and collateral moves, so an open venue cannot be flooded.

Planned

One relayer, enforced

A lease in Postgres that the relayer must hold to write, so a second instance waits as a standby instead of sending each keeper transaction twice. At present, it is a convention.

Planned

Observed FR-BASIS history

Replace 90 days of seeded FR-BASIS rows with the venues' own published funding history. The backfill is written; it hasn’t been run on production.

Planned

Retire seeded C-VIX history

Live collection began on 20 September 2026 and covers 90 days on 19 December. That day the seeded rows are deleted, and nothing else is.

Planned

Technical references mapped to the codebase

Check each formula, rule and status line on the docs and protocol pages against the contracts, and rewrite what predates them.

Planned

Chain venue on testnet

Safe ownership

Move all four contracts to a Safe: transferOwnership from the deployer, then one Safe batch of acceptOwnership. At present, the deployer key owns them.

Planned

A public testnet site

A second deployment, such as testnet.the practice venue, with its own relayer and database on the chain venue, so the chain venue runs in public without moving the main site off paper.

Planned

Keys by role

Separate keeper, settler and liquidator keys, each funded for one job and watched for its balance, so a leaked key can do only that job.

Planned

Solvency monitor

Read isSolvent, isBacked and the pool's free liquidity each block, alert on any breach, and chart them on the risk dashboard.

Planned

A second options venue

Another option surface in the C-VIX aggregate, so the index, and each C-VIX position with it, doesn’t stop when Deribit does.

Planned

Liquidations on a live network

Exercise liquidation on testnet. It is proven so far only on a local chain, where the test can move the index itself.

Planned

Contracts v2

Add margin

Top up an open position to move its liquidation level away. At present, the only way to take risk off a position is to close it.

Planned

Partial close and reduce-only

Close part of a position, with its margin, escrow and accrued costs split pro rata. At present, each order opens a new position and a close takes all of it.

Planned

Stop-loss and take-profit

Closes signed in advance with a trigger level. The contract checks the trigger against the oracle, so the relayer cannot fire one early.

Planned

Configured markets

Markets as configuration, each with its kind, leverage cap, feed and limits, instead of three constants compiled into the contracts. A listing then needs no redeployment.

Planned

Open-interest caps

Limits per market and per account. At present, the only bound is the pool's free liquidity.

Planned

Keeper quorum

The oracle settles on the median of values signed by several independent keepers, so a single compromised keeper cannot move it. At present, any allowed keeper can push within the band.

Planned

Emergency settlement

If a feed stays stale past a long, fixed bound, anyone can settle that market's positions at its last fresh level. Today a stopped keeper freezes exits until it returns.

Planned

Timelocked parameters

Changes to the borrow rate, depth, liquidation bounty, oracle age and spread step wait out a public delay. Pauses stay immediate, since they only protect.

Planned

Fee router

The fee split on the tokenomics page, applied by a contract. At present, each fee goes to the payout pool.

Planned

Keeping paper and on-chain venues aligned

The paper matcher gains each v2 feature, and a differential test runs one order sequence through both venues and compares each balance.

Planned

Terminal and API

Position-management tools

Add margin, partial close, reduce-only, stop-loss and take-profit, from the order ticket and the positions table.

Planned

Liquidation warnings

A notification when a position nears its liquidation level, and when an order fills or expires.

Planned

Export account data

Fills, closes and each ledger row as CSV, for bookkeeping.

Planned

Public API and typed SDK

Documented REST and streaming endpoints and a typed client built on @prismperp/core, for bots and market makers trading through session keys.

Planned

Audit and security

Independent security audit

An independent firm reviews the tagged commit. Each finding is fixed with a regression test, and the report is published naming the commit it covers.

Planned

Longer fuzzing campaigns

The four invariants held over millions of random calls instead of 128,000, and checked again by a second fuzzing engine.

Planned

Bug bounty

A public bounty with rewards scaled to the funds at risk, live ahead of the first real deposit.

Planned

Keys in a managed signer

Keeper and settler keys held by a key-management service that signs without exposing them, not in environment variables, with a rotation runbook.

Planned

Incident-response runbook

Who can pause what, how fast, and what is posted on X, rehearsed on testnet with the Safe's real signers.

Planned

Mainnet

Audited deployment

The audited bytecode on Robinhood Chain (4663) with Paxos's USDG as collateral, owned by the Safe through the timelock starting with the first block, and verified on the explorer.

Planned

Committed pool capital

The payout pool funded with real USDG. Each position reserves eight times its margin from it, so the pool can back open margin up to an eighth of its size.

Planned

Controlled launch

Low open-interest and deposit caps at first, raised on a published schedule as the pool grows and the book stays two-sided.

Planned

Public system-status page

Feed freshness, keeper health, pool solvency and any pause, read from the chain and shown to everyone.

Planned

Use the simulation venue for practice

the practice venue moves to the chain venue, and the paper venue stays open for practice.

Planned

$PUSHIN utility

Staking

Stake $PUSHIN for the share of trading fees the tokenomics page describes, paid in USDG. Without token emissions: rewards come from fees, not new tokens.

Planned

Buyback

The fee router's buyback share spent in the $PUSHIN pool on a public schedule, with each purchase and burn visible on-chain.

Planned

Governance

Votes on oracle venue weights, dampener parameters and new listings, carried out by the Safe through the timelock at first and on-chain later.

Planned

Keeper subsidy

The keeper share of fees paying for the gas that keeps the oracle fresh and orders settling. There is no token treasury to draw on.

Planned

Research

Netted escrow

Reserve the book's worst case instead of the sum of each position's cap. Longs and shorts on one index largely offset, so the same pool could back more open interest, once the bound is proven.

Research

Third-party pool capital

A vault with shares, so others can fund the payout pool and take its side of the book. Who carries that risk is a design decision before it is a technical one.

Research

More markets

Further volatility tenors and underlyings where an option surface is deep enough to replicate, and further basis pairs as the native venue lists them.

Research

Cross-margin

One margin account across positions instead of isolated margin for each.

Research

Permissionless keepers

Anyone may run a keeper, bonded and paid per fresh push, so the oracle doesn’t depend on one operator.

Research