The Databento team is currently working on this article.
Cboe EDGX Depth
Cboe EDGX disseminates full depth-of-book data for their exchange through their Pitch Feed, which Databento receives over UDP multicast in our NY4 data center.
The Multicast Depth of Book (Pitch) Specification is available as a PDF from Cboe's website.
Info
Timestamps
Cboe messages received by Databento will generally include one timestamp with nanosecond precision.
As with all of our datasets, we also collect a ts_recv
timestamp when the packet was received by our capture server.
Databento Field | Pitch Field | Description |
---|---|---|
ts_recv |
N/A | The capture-server-received timestamp. |
ts_event |
Time + TimeOffset | The matching-engine-received timestamp. |
ts_in_delta |
None | The difference between ts_recv and ts_event . Redundant and can be safely ignored. |
More details about our timestamps are available in our timestamping guide.
Flags
For Cboe EDGX Depth, the F_PUBLISHER_SPECIFIC
flag is used in the MBO schema to indicate Retail Priority Orders (RPOs). MBO messages with action A
will have the F_PUBLISHER_SPECIFIC
flag set if the order is an RPO. This flag will not repeat on subsequent modifications or cancellations.
Retail Priority changes the order allocation priority model on EDGX to price-retail priority-time priority. Thus, Retail Priority Orders will have priority ahead of all other available interest at a price level.