Skip to main content
The TRDRS testnet provider service wraps an existing venue connection behind the same public contract used by every third-party provider. It currently supports Binance USD-M Futures testnet and Hyperliquid testnet. There is no mainnet switch in this service.

​
What stays inside the service

Keep the venue API key or wallet, symbol conversion, quantity rules and stream details in the provider process. TRDRS receives the normalized manifest, accounts, snapshots, events and command receipts. The service writes session generations, command receipts and replay cursors to its own persistent volume; it does not write venue credentials there.

​
Configure one provider account

Deploy one process for one testnet credential and account. Start from packages/testnet-provider-app/fly.toml.example in the engine repository, create the provider_data volume, and set the provider-specific secrets listed in packages/testnet-provider-app/README.md. Required common settings: The service refuses to start if required credentials or account identity are missing.

​
Qualify it

Set PROVIDER_ENDPOINT to the deployed service and provide the minimum testnet order described in the app README. Then run:
The command runs the same provider self-check used for outside providers. It checks session fencing, account isolation, event replay, payload hashes and command retry behavior. The order must use the provider’s minimum testnet size. Save the resulting JSON as test evidence. A local fixture proves the contract code; only a passing run against the remote testnet proves the venue integration. Production remains disabled until that evidence and the operating controls are reviewed.