DLOB Auctions

Sidepit's core market structure is DLOB — one-second deterministic auctions.

One-second epochs

During an open session, signed transactions are grouped into one-second epochs. Each epoch has a deterministic transaction sequence, then a central limit order book applies price priority and matching rules.

Within an epoch, arriving a few microseconds earlier does not buy priority over a better price. Participants compete on price and risk decisions rather than physical proximity to the matching engine.

What DLOB does not guarantee

DLOB removes the continuous speed race from the ordering rule. It does not guarantee:

• that an order will be accepted;

• that liquidity exists;

• that a market order will fill completely;

• that a limit order will fill; or

• that an order is resolved at the moment it is submitted.

Client rule

A successful network send means queued for an auction. Read the order and rejection feeds to learn the result.

Order data can contain multiple messages for one epoch because products are interleaved. A raw client must filter by ticker and drain port 12124 through more_in_epoch == 0 before acting on the completed book state.

The epoch echo and auction streams are public advanced surfaces for clients that need to observe the deterministic input sequence. See Public API and SDKs.