examples/trading_client/README.md

# Trading Client Construction

[中文](README_CN.md)

Shows two client-construction patterns: `TradingClient::new` for one wallet and `TradingClient::from_infrastructure` for wallets sharing RPC and SWQoS clients.

This is a configuration template. Set `PRIVATE_KEY`, RPC, and every enabled provider credential; it initializes network clients but does not submit a trade.

The Glaive entry uses QUIC by default. Its credential must be a UUID v4 API key from Glaive. Replace the fourth argument with `Some(SwqosTransport::Http)` to use binary HTTP instead.

```bash
cargo run --package trading_client
```

Initialize the client before subscribing to events. Do not construct it in a trading callback.
feat: harden trading SDK examples 2026-07-12 14:35:58 +08:00			`# Trading Client Construction`

			`[中文](README_CN.md)`

			Shows two client-construction patterns: `TradingClient::new` for one wallet and `TradingClient::from_infrastructure` for wallets sharing RPC and SWQoS clients.

			This is a configuration template. Set `PRIVATE_KEY`, RPC, and every enabled provider credential; it initializes network clients but does not submit a trade.

feat(swqos): add Glaive transaction sender 2026-07-18 23:20:57 +08:00			The Glaive entry uses QUIC by default. Its credential must be a UUID v4 API key from Glaive. Replace the fourth argument with `Some(SwqosTransport::Http)` to use binary HTTP instead.

feat: harden trading SDK examples 2026-07-12 14:35:58 +08:00			```bash
			`cargo run --package trading_client`
			```

			`Initialize the client before subscribing to events. Do not construct it in a trading callback.`