Vordium LabsDocs

Following an account

Keep a program's view of its orders, positions and history in step with the chain, and recover from a gap.

Start from the committed state

On start-up read the account's committed state:

  • GET /orders/{address} — open orders (filled_18dec, remaining_18dec);
  • GET /positions/{address} — positions and their liquidation prices;
  • GET /account/equity/{address} — what is free to trade.

Then follow it live

Subscribe to the account's orders and fills on the market-maker feeds. The orders snapshot is the open orders; apply updates by order_id. Every message carries seq and prev_seq: a mismatch means a missed message, so subscribe again and take the new snapshot.

Fill gaps from the records

Fills and order updates carry a cursor. After a reconnect, read the account's records from that point with GET /events/account/{address}. Every answer says which heights it covers — a height outside that range is unknown, not empty (State and records).

Confirm every write

A 202 means received. Count an order as placed when /orders/{address} lists it (find it by your client nonce), cancelled when it is gone, a session as open when /session/valid answers confirmed: true, and an agent change as applied when /agents/{account}/{agent} shows it.

Network facts last checked against the network 2026-10-22 13:00:37 UTC · mainnet spec v28 · testnet spec v8

On this page