Understand the instruction. Follow the outcome.
Explore the order concepts shown in the current preview and the terms that must accompany a future executable instruction.
The examples below explain workflow semantics. They are not a promise that an instruction is accepted by a live Exchange market.
Published 14 October 2026 · Operating information v1 · No effective trading dateLimit order
Sets a maximum purchase price or minimum sale price. A limit controls the permitted price; it does not guarantee a fill. The preview supports reviewing a sample limit ticket. Live priority, lifetime and partial-fill rules remain instrument-specific release requirements.
Market order
Requests immediate execution against available eligible liquidity. The final price can differ from a reference or estimate. The preview illustrates a market ticket with fictional prices; live price protection, quantity limits and handling of insufficient liquidity must be specified before access.
Cancel instruction
Requests cancellation of the unfilled remainder. An accepted cancellation request is not yet a confirmed cancellation. Already executed fills still need settlement, and uncertainty must not prematurely release Core reservations.
OTC request and quote acceptance
An RFQ asks the Exchange desk for terms; it is not a completed trade. Future quotes need exact assets, amounts, fees, expiry, settlement and approval conditions. The demo uses a fictional timed quote and does not contact a liquidity provider.
Additional order features
Time-in-force variants, post-only, stop and conditional instructions require separate market-level acceptance and documentation. Engine source capabilities do not establish public product availability. No production support matrix for these features is published yet.