Every order fills in a Crossing: the batch the Coprocessor runs whenever orders are sealed, as often as every 4 slots (about 0.8 s). A fill can have two parts, the crossed part filled against opposing orders inside the Pool at the mid, and the routed part filled through the Pool’s one Residual swap for the pair, and the app shows the share each part took, the average price and the fee.
Watch an order cross#
Sealed#
Right after you press the place button, the ticket and the Placed here tab show Sealing. Once intake takes the Intent they read Sealed, with the Coprocessor or Waiting for the next Crossing, until the enclave names its Crossing. The order drops into the capsule under the place button, “Your orders in the Pool”, as a drop with a ring.
Waiting for Crossing k#
An order the enclave accepts before the next cutoff joins that Crossing’s batch and shows Waiting for Crossing k; one accepted after it waits for the Crossing after. The wallet button in the nav counts your orders still waiting.
Crossed and routed#
At the cutoff the Coprocessor nets each pair at the mid, fills opposing size against each other inside the Pool, and routes the net remainder as one Jupiter swap from the Pool’s vault (Crossing). In the capsule, your drop’s crossed part merges with the drops it met and its routed part leaves through the right end.
Filled#
The Crossing’s Commit lands the new Ledger root. Your browser reads your leaf, checks it against that root and decrypts the fill. The order shows Filled at Crossing k (or Partly filled at Crossing k), the ticket sums the fill up, and your balances update.
The Crossing clock#
The market bar’s clock reads “An order now makes the next Crossing”, beside a ring with the Pool’s drop breathing inside it. A Crossing begins as soon as an order waits and 4 slots have passed since the last Commit, so there is no fixed time to count down: an order you place now joins the next cutoff, and its own state names the Crossing once the enclave assigns it (The batch).
Reading a fill#
Under the place button the ticket sums up the latest order’s fill: “n% at the mid, inside the Pool”, then Average, Cost for a buy or Received for a sell, and Routed size at price when part of it routed.
| Part | The app shows | Price | On chain |
|---|---|---|---|
| Crossed | Its share of the fill: “n% at the mid, inside the Pool” in the ticket, the percentage under In the Pool in Placed here, and size at price under Crossed at the mid in Fills | The mid the Crossing stored, the same for every crossed fill in the pair | Nothing: it settles inside the Pool. |
| Routed | Routed size at price in the ticket and in Fills, and a link beside the share under In the Pool, each linked to the Pool’s swap | The Residual swap’s executed price, shared by every routed fill in the pair | The Pool’s swap, signed by the Pool authority. |
| Fee | Counted into Cost or taken from Received in the ticket, and its own Fee column in Placed here, in the quote asset | φ on each part’s size times its price | Paid with the Crossing’s fees in its Commit (Fees). |
Sizes are in the base asset. Average is the volume-weighted price of both parts, each within its limit. Cost is what a buy paid in the quote asset, fee included; Received is what a sell brought, fee taken.
The routed link opens the Residual swap transaction. It names the pair, the amounts the Pool spent and received, and no trader; Pool lists the same swap in its Crossing’s row.
How an order is split#
Within a pair, the side with less total size fills in full at the mid. The side with more shares the crossed size in proportion to each order’s size, in whole base units (Allocation). What each order on the heavier side has left joins the Residual if its limit clears the route’s worst admissible price, and rests otherwise. When and in what order your Intent arrived inside the batch changes nothing, and neither does splitting one order into several.
A buy’s routed part receives its share of the base the swap delivered, which can be a little less than its routed size; the shortfall rests or expires with the order (How the routed part is priced and allocated).
Partial fills#
Partly filled at Crossing k means part of the order filled and the rest keeps resting. A limit order rests across Crossings until its limit is met or its time runs out; the Open tab shows it as “Partly filled, resting” with what is Left, its expiry slot and a Cancel button. A market order’s unfilled rest expires with the order, about one minute after it was placed. A pair whose mid fails its age or confidence check does not trade in that Crossing at all: its orders neither cross nor route, and rest for the next one.
Where fills show#
- The ticket: the latest order’s state and its fill summed up, under the place button.
- Placed here on Trade: every order placed from this tab, with its Size, Average, share In the Pool, Fee and Status.
- Fills on Trade: each fill with its Time, Crossing, Market and Size, the part Crossed at the mid and the part Routed. The refresh button beside the tabs reads the Ledger again.
- History on Account: each fill as “Fill pair” with “crossed at price” and “routed at price”, the size, Pool swap linked when it routed or “Inside the Pool” when it crossed in full, and the fee as its own Fee entry.
The SDK follows the same results with watchFills and reads past fills with readHistory.