Know what the
numbers mean.
Data sources and freshness
The configured Velocity program supplies contract metadata, margin requirements, oracle prices and account state through Solana RPC. The market registry checks the current confirmed slot against each oracle. It excludes new-trade eligibility when the oracle is more than 150 slots behind, reports insufficient data, or relevant fill operations are paused. Order books come from the protocol DLOB endpoint and are a separate source from oracle prices.
Prices, units and funding
Base quantities use 9 decimal places and prices use 6 in the existing SDK. Tick and quantity increments come from each market account. The last funding rate is a historical protocol value expressed against the current oracle; it is not a forecast. The chart shows observations collected in your browser session, not historical exchange candles.
Availability and limitations
Market pages render on the server from the current registry. Only eligible contracts enter the active directory. Known contract reference pages remain in the sitemap with a clear availability status. Unknown symbols return 404. During registry outages, existing physical reference pages remain accessible with a stale-data notice; pages without a saved reference return 503. No list, healthy API or simulated transaction proves that a future order will fill.
Wallet and protocol identity
Bitpont constructs and simulates unsigned transactions; the wallet signs and sends. Account balances belong to the configured protocol. An upgrade to another program is not an automatic transfer of accounts or collateral. Verify the effective program in the service configuration endpoint. Message signatures authenticate API requests; they are separate from transaction signatures.