This week on Nexus 06.23.26 — This week on Nexus

This week’s work opens the Exchange up to programmatic and agent-driven trading, raises the bar on price-feed quality and safety, and makes the venue more resilient when something goes wrong. Most of this has merged and is rolling out — some pieces are still landing on the live Exchange.

Programmatic and agent trading

We’re building first-class support for trading the Exchange from code, including by AI agents. A new MCP server exposes the Exchange API so an agent can read markets and place orders through a standard interface, and a generated Rust SDK gives developers a typed client straight from the API spec.

Safety is built into how agents get access. Delegated agent keys can trade but cannot withdraw, so you can hand an agent authority to manage positions without ever handing it the ability to move your funds out. A new account deposit-target endpoint lets an agent fund itself into the right account to start trading.

An agent trades through the MCP server and SDK using a delegated key that can trade but not withdraw

Price-feed quality and safety

Accurate, honest prices are the foundation of a fair venue, and this release strengthens both. The Exchange is adding Pyth Pro (Lazer) as a low-latency oracle source over WebSocket, and the mark price now blends in a median of recent trades so it reflects where the market is actually trading rather than any single input.

Just as important is what happens when a feed goes quiet. Instead of papering over a dead feed, the Exchange now treats staleness as a first-class signal: a wall-clock poller watches each feed and a fail-closed gate stops trading on a market whose price source has gone stale, rather than letting orders match against a stale number. Trading resumes once the feed is healthy again.

A stale price feed trips a fail-closed gate that pauses the affected market until the feed recovers

Reliability under stress

Several changes make the venue tougher when conditions get rough:

Faster recovery. Engine snapshots moved to a more compact serialization format, so restoring from a recent checkpoint is quicker and lighter.
Automatic, contained crash handling. If a single market’s process crashes, the Exchange now detects it and halts just that market on its own — keeping the failure isolated instead of touching the rest of the venue.
Atomic pre-trade margin reservations. Margin is now reserved as one atomic step before a trade goes through, closing the gap where concurrent activity could race.

Snapshot size, write time, and restore time all drop after the move to a compact format

Engine snapshots moved to a more compact format (MessagePack): smaller files that write and restore faster, so recovery from a checkpoint is quicker. Debug-build benchmark — illustrative of the relative shape, not production absolutes.

Groundwork toward mainnet

Behind the scenes, the engine now supports per-environment configuration, including a dedicated profile for the mainnet instance — a quiet but necessary step toward running the Exchange in production.

To explore the latest, visit nexus.xyz, docs.nexus.xyz, or github.com/nexus-xyz.