7 · Verify and go live

Redeploy the service from the latest code — an environment change alone reuses the old image. Then read the boot log. The runner prints the account it will sign as; it must be this bot's own address, not a sibling's.

[bot] runner started  account=0x2387398351…  hiveId=4238

If the account matches and the wallet is funded + deployed, the fuel manager wraps USDC.e to pUSD and the strategy begins ticking. Flip live trading on and redeploy once more:

BOT_LIVE_TRADING_ENABLED=true

Healthy signs

• Boot log shows the bot's own address in account=…
• [bot-fuel] wrapped USDC.e → pUSD (funds are tradable)
• [bot-fuel] above fuel floor … no refuel on later ticks (float is fine)
• A strategy tick that ends intent accepted / captain … filled

If it isn't trading

• BOT_LIVE_TRADING_ENABLED still false — an idle runner never spends.
• Not on the latest build — a plain restart reuses the old image; redeploy.
• Wrap refused (from 0x… does not match auth 0x…) — the relayer address isn't this bot's EOA. See step 2.
• Wallet not deployed / not funded — no pUSD to trade with. See steps 3–4.
• Cadence — some strategies fire on a schedule (e.g. once a day). A quiet log that shows healthy fuel and the right account is usually just waiting for its next window.

See Common mistakes »