The orchestrator, the connection loop and the book thread's shell move to src/core/, generic over an Exchange and its loss rule (ADR 0004). Polymarket runs through it unchanged. Kalshi joins: a signed handshake (KALSHI_KEY_ID_FILE, KALSHI_PRIVATE_KEY_FILE), a reconnect on a skipped sequence number, first one wins by clock and rank, and its market listing with markets tracked from three hours before they open. Breaking: the exchange is now the first argument, `engineering-challenge <polymarket|kalshi|kalshi-demo> [OUTPUT]`.
Read before getting started!!
First, read src/main.rs. Then, some background on this repo:
This repo uses the FIX SBE standard
for writing binary messages. The rust code abstracts this away for you, and you can simply use the helpers, as demonstrated in main.rs.
More background, in case you are curious!
FIX SBE is defined in XML, which I find extremely cumbersome to edit, especially when updating schemas frequently. To solve this, I have also introduced some helper code that takes our own custom YAML format, and turns it into FIX SBE XML, which in turn is used to generate rust code to encode and decode the messages. You don't need to edit any of these files. This explanation is simply to help you understand the origins of the various files in this repo.
If you're curious to see the YAML schema, take a look at challenge_orderbook.yaml.
We also use a custom timestamp field, so that the Rust struct can use
chrono::DateTime in the generated struct, and in SBE schema, it is a uint64
representing the timestamp as the number of microseconds since unix epoch.