Exchange architecture
Current venues, execution control, settlement boundaries, and the move to native markets. How Novrinex works.
Novrinex operates a perpetual markets exchange for crypto, equities, commodities, indices, and foreign exchange. The live exchange combines one market catalogue and order system with liquidity from established execution venues. Novrinex-operated markets and Novrinex L1 are the next infrastructure stages.
Novrinex maintains the customer account, market catalogue, order workflow, execution records, portfolio view, and research products. Orders pass through Novrinex pre-trade checks and a durable server-side execution system. Current markets use Orderly, Hyperliquid, or Ostium for liquidity and settlement, depending on the product.
This architecture gives Novrinex a live exchange before its own matching and settlement systems enter production. It also creates one operating record across market types that otherwise use different collateral accounts, order APIs, and settlement models.
Crypto order books sit beside equity, commodity, index, and FX perpetuals. Each listing carries its own collateral, leverage, trading-hours, price-source, and execution rules.
The exchange checks authorization, current capital, size, leverage, market state, and price deviation. A timed-out or uncertain submission is reconciled against the execution venue before another order is allowed.
Funds remain in the trader’s wallet or user-attributable market accounts. The portfolio combines those balances for reporting, while the order ticket shows the amount available to the selected market.
The long-term exchange will operate its own core perpetual markets. Novrinex will control matching, margin, funding, liquidation, insurance accounting, and settlement for those markets. The first planned native listings are BTC, ETH, and SOL perpetuals, subject to legal clearance, liquidity commitments, security review, and risk testing.
Novrinex L1 follows that venue build. The network is intended to carry exchange state and settlement under a purpose-built validator design. Public specifications will be released before testnet. No mainnet date or protocol asset has been announced.
An accepted command is not a fill. The terminal distinguishes queued, submitted, working, filled, rejected, and unresolved orders throughout the process. See Orders for the state model.
Exchange architecture
Current venues, execution control, settlement boundaries, and the move to native markets. How Novrinex works.
Trading
Market structures, supported orders, capital preparation, margin, funding, and liquidation. Markets and venues.
Insights and performance
Structured market analysis, verified records, creator controls, and product limits. Insights.
Roadmap
Delivered systems, work in progress, native markets, testnet, and mainnet release gates. Roadmap.