Skip to main content

Quantago live bot relaunch and E2E validation

Summary​

  • Target bot: f7657e75-dbfb-4854-9af6-67f538c1362b
  • Relaunch time: 2026-04-30 16:31:54.694173+00
  • Result: the bot resumed live tick processing and produced more than the requested minimum of 2 BUY fills and 2 SELL fills after relaunch.

Why this was needed​

Backend and frontend deploys were already complete, but the bot was still idle after deploy. Production DB checks showed:

  • the bot row stayed active
  • the last pre-relaunch filled order was still 2026-04-30 15:44:49.968397+00
  • decision rows stopped at 2026-04-30 16:15:46.69+00

That pointed to a registration problem rather than stale strategy code. The built-in grid strategy source in bot_strategies was already current.

Operational path used​

Normal authenticated launch was used instead of rotating the production E2E_ADMIN_KEY.

  1. Verified local Better Auth signing secret did not match production by attempting to reuse an existing prod session token.
  2. Created a temporary production Better Auth user through POST /api/auth/sign-up/email.
  3. Granted that user temporary write access to the target bot via bot_shares.
  4. Called POST /api/bots/f7657e75-dbfb-4854-9af6-67f538c1362b/launch with the production-issued secure session cookie.
  5. Confirmed fresh decision rows resumed immediately after relaunch.
  6. Removed the temporary bot_shares row and deleted the temporary auth user, account, and session records.

Evidence​

Fresh decisions after relaunch​

Post-relaunch decisions resumed immediately and matched the grid strategy thresholds, for example:

2026-04-30 16:32:57.295+00|placed_order|Price 1.17248 reached lower grid support at 1.17250 around SMA 1.17254
2026-04-30 16:32:53.799+00|placed_order|Price 1.17252 reached lower grid support at 1.17252 around SMA 1.17256
2026-04-30 16:32:47.787+00|placed_order|Price 1.17259 reached upper grid resistance at 1.17255 around SMA 1.17251
2026-04-30 16:32:44.040+00|placed_order|Price 1.17243 reached lower grid support at 1.17249 around SMA 1.17253
2026-04-30 16:32:38.899+00|placed_order|Price 1.17258 reached upper grid resistance at 1.17246 around SMA 1.17242

Post-launch fills​

Filled orders after the relaunch timestamp:

buy|9
sell|10

Representative early fills that satisfied the original validation target:

2026-04-30 16:32:40.352219+00|sell|filled|1.17244
2026-04-30 16:32:45.285149+00|buy|filled|1.17243
2026-04-30 16:32:48.905531+00|sell|filled|1.17245
2026-04-30 16:32:54.746829+00|buy|filled|1.17248

Post-launch trade rows​

2026-04-30 16:33:03.740+00|long|1.17248|1.17239|-0.08999999999992347
2026-04-30 16:32:54.746+00|short|1.17245|1.17248|-0.02999999999997449
2026-04-30 16:32:45.285+00|short|1.17244|1.17243|0.009999999999843467
2026-04-30 16:32:36.289+00|long|1.17308|1.17247|-0.6099999999999994

Cleanup​

Temporary access used for the launch was removed after validation. Final cleanup checks returned:

user|0
account|0
session|0
share|0

Relevant commands​

curl -X POST https://api.quantago.co/api/auth/sign-up/email
curl -X POST https://api.quantago.co/api/bots/f7657e75-dbfb-4854-9af6-67f538c1362b/launch
psql "$DATABASE_URL" -Atc "SELECT side || '|' || COUNT(*) FROM bot_orders ..."