Levandor

PM is LIVE Real Money — Multi-Wallet + FAK (2026-07-02)

3 min read

As of 2026-07-02, PM is trading REAL money. Multi-wallet routing and the FAK re-priced retry path are executing live trades. Do NOT assume DRY/OFF — verify the actual pmv2_autotrade_config.mode before touching anything money-path.

PM is executing REAL trades right now

The autotrade global mode is live, wallet1 is live, and all 10 crypto sources are live. Multi-wallet routing + the FAK re-priced retry are placing real orders (observed ledger entries 3451 / 3452 / 3457). Treat any change to consumer, routing, mode, or execute paths as a live-money change.

How it went live

  1. Global mode = live — the autotrade config global mode was set to live during the crypto go-live (babylon deploys #895 / #896).
  2. Wallet backfill copied the mode — the multi-wallet backfill migration 20260701000200 copied config.mode → wallet1.mode = live. So wallet1 inherited live automatically.
  3. All 10 crypto sources are live — every crypto source resolves to live.

Net: with the 3-way clamp min(global, wallet, source) all three axes at live, the effective mode is live end-to-end. Multi-wallet routing and the FAK re-priced retry both execute real trades.

"mode stays OFF/current" in deploy chatter meant UNCHANGED = live, not off

During deploy discussion, “mode stays OFF” / “mode stays current” was interpreted by some as “disarmed.” It actually meant unchanged, and the unchanged value was already live. This wording nearly hid a live-money state. Never infer arming state from chat phrasing — query the DB.

Always verify actual mode before assuming DRY/OFF

Check pmv2_autotrade_config.mode (global), the per-wallet pmv2_wallets.mode (e.g. wallet1), and per-source pmv2_autotrade_sources.mode for the sources in play. Effective mode = min of the three. Do not assume OFF/dry from deploy notes.

Backlogged follow-up: FAK-retry v2 (live money-path change)

  • Change: FAK re-priced retry ceiling = directive.limit_price instead of the current hardcoded 0.88.
  • Status: backlogged, NOT started.
  • Gates: (1) crypto’s producer df6f500 (break-even limit pricing) must be deployed first; (2) explicit Andras go-ahead. This is a live-money-path change, so it does not land unilaterally.
  • Context: the FAK branch is the deliberate retry seam noted in pmv2-fak-no-match-reject-single-line-2026-06-30.

Also shipped today

  • Telegram 30-min aggregate feature — merged to main at a5f3604. Spec + plan live under docs/superpowers/ in the repo.

Graph View

Backlinks