RISEx
Mainnet-only RISEx perpetual market data through Furge's shared processor and aggregation.
RISEx public feeds are mainnet-only. Trading and account connections are available starting with runtime 0.1.145. Furge indexes selected public perpetual markets under risexf. Public ingestion requires no account, API key or builder code.
| Feed | Support |
|---|---|
| Trades | Native execution IDs, taker side, base quantity and RISE block time |
| Order book | Full snapshots and absolute-size updates, verified with full-book CRC32 |
| Oracle | Live mark and index prices |
| Funding | Estimated next funding rate, with its native interval |
| Open interest and statistics | One shared REST refresh per minute, preserving provider observation time |
| Candles, profiles and volume delta | Derived by the existing processor from indexed executions |
| Aggregation | Compatible multi-venue books, tape, profiles, delta, OI and OI-weighted hourly funding |
Discover markets first
On the market-data node:
python3 scripts/markets.py discover --exchange risexf
python3 scripts/markets.py select snapshots/mainnet/risexf.json --symbols BTC,ETH,SOLOmit --symbols to select all active listings in the snapshot. Selection preserves other exchanges in the curated catalogue. The initial committed snapshot and mainnet selection contain 56 active, unlocked markets.
Add risexf to market_data.consumers alongside the node's existing consumers. For example, a node already using Hyperliquid and Extended can use:
{
"market_data": {
"consumers": ["hyperliquidf", "extendedf", "risexf"]
}
}Keep the node's other configuration fields. Startup uses the selected local catalogue; discovery is an explicit operation.
RISEx is rejected in testnet consumer configuration and testnet catalogues. There is no fallback from a testnet node to RISEx mainnet. No spot consumer is registered.
Market identity and units
The snapshot preserves RISEx's numeric provider market ID, native base/quote identity, decimal tick and lot sizes, minimum base quantity and funding interval. The published base minimum is not a fixed USD minimum: min_notional remains 0. The node derives execution rules from selected native increments, and the trading adapter separately validates minimum base quantity.
Scaled contracts such as 1000PEPE retain that identity. Token artwork does not change subscription symbols or imply compatibility with a single-token contract during aggregation.
Book and trade prices and sizes arrive as human-readable decimals. Oracle prices use 18-decimal integers and are converted separately. Funding rates retain their native interval before aggregate hourly normalization. Estimated funding is a market quote, not a record of account funding payments.
Streams and recovery
One public WebSocket subscribes to configured market IDs across books, trades, oracle prices and estimated funding. Book snapshots can arrive before subscription acknowledgements and are processed immediately. Acknowledgements must confirm the requested market filter.
Book updates replace quantities at changed levels; zero removes a level. Checksums use exact integer arithmetic across the entire sorted book, before publication to the processor. A checksum failure or backwards ordering invalidates depth and reconnects for a new snapshot. Coalesced updates can skip block/log indices, so a missing consecutive index is not treated as a sequence gap. Transport heartbeats do not manufacture fresh book timestamps.
The trade channel has no execution timestamp. Furge resolves the RISE block time through mainnet RPC, using a bounded cache shared across the consumer's trade worker. Temporary RPC failures keep queued fills pending and retry; buffers and deduplication caches are bounded. A live trade can arrive before its block is indexed by the public RPC. A null block result is retried as pending, without warning for brief delays. A delay lasting five seconds or an actual RPC failure produces warnings, limited to one per 15 seconds for the pending fill. Furge does not substitute ingestion time for execution time. Several distinct fills can share a block and log index, so deduplication retains the complete execution identity.
REST observations preserve cached_at. Live oracle updates retain independent quote timestamps and do not make an old OI/statistics observation appear fresh.
Indexed history and terminal
Executions enter the existing processor, storage and serialized streaming format. Subscribe through the existing market-data protocol:
{"type":"candles","exchange":"risexf","symbol":"BTC","tf":"1m"}Compatible venues can be combined:
{"type":"vd","exchange":"hyperliquidf,risexf","symbol":"BTC","tf":"1m"}History accumulates from live ingestion. This release does not backfill missing executions after an outage or reconstruct trade-side volume and profiles from exchange candles.
The terminal lists RISEx with its exchange logo for charts, books and aggregation. Trading and account connections use the separate RISEx execution provider; public data remains independent of credentials.
See the official RISEx API reference, order-book channel and trade channel.