How Novrinex works
Novrinex runs one exchange product across several forms of market infrastructure. Traders use a common catalogue, terminal, account view, order record, and trade history. Orderly, Hyperliquid, and Ostium currently provide the underlying liquidity and settlement routes.
Novrinex-operated order books and Novrinex L1 are planned infrastructure. They do not execute current customer orders.
Operating boundary
Section titled “Operating boundary”Novrinex controls the systems between the trader and the active execution route:
- canonical market names and listing metadata;
- wallet login and account ownership checks;
- order entry, preflight, and order limits;
- trade-only execution authorization;
- durable order commands and duplicate prevention;
- submission, status tracking, and reconciliation;
- the combined portfolio and venue-verified trade ledger;
- Insights, creator profiles, and verified performance records.
The active route controls its own matching or contract execution, margin rules, mark price, funding, liquidation, and final account state. Novrinex reads those authoritative records and maps them into a consistent exchange account.
Three current execution models
Section titled “Three current execution models”Current markets fall into three operating groups.
| Market group | Current route | Trading model | Capital location |
|---|---|---|---|
| Crypto markets | Orderly | Order book | User-attributable, pre-funded market account |
| Global markets | Hyperliquid | Order book | User-controlled Hyperliquid account funded through its bridge |
| Wallet-collateral markets | Ostium | Oracle-priced contract execution on Arbitrum | USDC remains in the connected wallet until used as position collateral |
The selected market determines the route. Novrinex does not send the same order to several venues or switch routes after a submission becomes uncertain. Execution details remain available in transaction records and disclosures.
Order processing
Section titled “Order processing”1. Preflight
Section titled “1. Preflight”The backend checks the canonical symbol, market state, order type, size, minimum notional, leverage, live reference price, permitted price deviation, relevant account balance, and execution authorization. New exposure fails closed when required account or market data is stale.
2. Durable command
Section titled “2. Durable command”Novrinex commits the complete order command before it contacts an external system. A stable client request identifier makes exact retries return the same record. Reusing that identifier with changed economic terms is rejected.
3. Server submission
Section titled “3. Server submission”The exchange dispatches the command through the user’s scoped trading authorization. These credentials can place and cancel trades. They cannot withdraw from the user’s main wallet or market account.
4. Reconciliation
Section titled “4. Reconciliation”A network timeout can occur after an order reaches the execution route. Novrinex marks that result as unresolved and looks it up by its external identifier or transaction hash. It does not submit a replacement until authoritative state establishes what happened.
5. Account update
Section titled “5. Account update”Positions, orders, balances, fees, realized profit and loss, and liquidations are read back from venue or onchain sources. Novrinex stores a normalized, source-tagged record for the portfolio, activity feed, verified performance, referrals, and future Points calculations.
Capital remains separated
Section titled “Capital remains separated”The portfolio total is the sum of user-attributable balances across the connected wallet and market accounts. It is a reporting number. It is not one balance that can support every order.
The order ticket therefore uses Available for this market as its buying-power figure. A market may require a deposit, bridge, internal transfer, allowance, or account authorization before an order can proceed. Novrinex coordinates the required workflow and rechecks price, fees, capital, and market status before submission.
Read Capital and accounts for the current account model.
Public market data and private account state
Section titled “Public market data and private account state”Public prices, charts, books, and trades can update continuously without access to a trader’s account. Private balances, positions, authorizations, and orders come from authenticated account reads. A public price on screen does not prove that private account state or the execution route is ready.
Novrinex disables new execution when required private data, market data, or route services fail their checks. Risk-reducing actions receive separate handling, but they remain subject to the active route and network.
Path to Novrinex-operated markets
Section titled “Path to Novrinex-operated markets”The current gateway already treats execution as an adapter behind one order contract. The native Novrinex venue will enter through that same boundary. The terminal, canonical symbols, order records, and portfolio model do not need a separate customer product when native execution begins.
For Novrinex-operated markets, Novrinex will assume responsibility for matching, margin, funding, liquidation, insurance accounting, market-maker access, and settlement. Novrinex L1 is planned to carry those functions after the native venue has been tested under production trading requirements.
See the roadmap for the sequence and release gates.