Swift Server

Infrastructure for the Server order pipeline.

Architecture

There are 3 server components:

• Swift Server: HTTP server for receiving signed order messages from takers e.g. via the UI
• Ws Server: Ws server for broadcasting taker orders to market makers
• Confirmation Server: Provides API for server progress tracking

graph TD
    A[Taker]
    B[Server Server]
    C[WebSocket Server]
    D[Market Makers]
    E[Kafka]
    F[Blockchain]
    G[Confirmation Server]
    H[Redis]
    I[Fillers]
    A -->|Post signed OrderParams| B
    B -->|Publish verified orders | E
    C -->|Broadcast new orders| D
    D -->|Send PlaceAndMake Tx| F
    E --> |Subscribe new orders| C
    A -->|Poll order status|G
    G -->|Fetch order hash|H
    C -->|Place taker + fill txs| I

Loading

Build

ensure an x86_64 toolchain is configured for building swift-server

rustup install 1.83.0-x86_64-apple-darwin
# run inside swift-server directory
rusutp override set 1.83.0-x86_64-apple-darwin

cargo build --release

Run it

./target/release/swift-server --help

Run

The server stack uses kafka for sending messages between the swift_server and the ws_server.
docker-compose up to run a local kafka instance.