Skip to content
Get ProGet Pro

Paper, testnet and mainnet

The three modes Guard runs in, what each one sends where, and why mainnet needs you to type it.

Guard has three modes: paper, testnet and mainnet. Installation starts in paper mode. Check your integration with paper and testnet before explicitly activating mainnet.

PaperTestnetMainnet
PricesHyperliquid mainnet, realHyperliquid testnetHyperliquid mainnet
Orders sentnoneto api.hyperliquid-testnet.xyzto api.hyperliquid.xyz
Moneynonetest USDC, no valuereal
Stops rest on the venueno (simulated)yesyes
How you get therethe defaulta testnet setup, then run --network testnettype the network, confirm the account

Paper mode reads real prices and judges every order exactly as it would on mainnet, then records the decision instead of sending it.

Example. Your bot buys ETH. Guard answers “resized to 0.41 ETH, rule: max loss at the stop”, writes it to the journal and the event log, and sends nothing.

Testnet is a separate Hyperliquid network with test money. Orders are real orders there: stops rest on the venue and fire.

Native Windows supports paper and testnet in Guard 1.0. The website setup wizard offers these initial modes; AWS launches start in paper mode.

Things that differ from mainnet (docs/testnet.md, “What differs between the networks”):

  • Signatures. Orders are signed for one network. A testnet signature is rejected on mainnet and the reverse: the “phantom agent” carries source "b" on testnet and "a" on mainnet.
  • API wallets, asset ids and nonces are per network. An API wallet approved on testnet does not exist on mainnet.
  • Prices on testnet are not mainnet’s.

Mainnet trades real money. Guard never gets there by itself.

For a managed mainnet service, use Linux with systemd 250 or newer and systemd-creds. The installer requires encrypted credentials and refuses mainnet setup when that support is absent. On first setup without a mainnet journal it leaves the service stopped for you to initialise the journal and start it. With an existing journal, reconfiguration can restart the service immediately: stop your bot first and verify the final config and licence before reconnecting it. Native Windows is limited to paper and testnet.

Each mode has its own journal. Moving from testnet to mainnet starts a new journal with a new peak. Your limits carry over in the config; the risk state does not.

This page as plain Markdown, for people and LLMs: /docs/concepts/networks.md