# Live execution verification preflight

Updated: `2026-07-29T14:23:05Z`

Status: `BLOCKED_CREDENTIALS_AND_EXCHANGE_CONFIRMATION`

No live container has been created or started. The existing RiskCap dry-run
container remains unchanged.

## Prepared

- Separate Compose overlay:
  `freqtrade/docker-compose.live-verify.yml`
- Separate remote config:
  `/data/freqtrade/user_data/config-live-verify.json`
- Separate future database:
  `/data/freqtrade/user_data/tradesv3-live-verify.sqlite`
- Separate future log:
  `/data/freqtrade/user_data/logs/freqtrade-live-verify.log`
- Local-only API binding: `127.0.0.1:8083`
- Strategy: `VolatilityBreakoutRiskCap`
- Profile: explicit `live`

The generated remote config is mode `0600`, SHA-256
`4c09d335e55b4166d3d74f0fe9ca8153ba33d3a07248a53955aa4429025e9a04`.
It differs from production behavior only by:

1. `dry_run: true -> false`;
2. removal of `dry_run_wallet`;
3. `force_entry_enable: true -> false`.

It preserves 5m, four maximum open trades, isolated futures,
`price_side=same`, ten-minute entry timeout, and exchange stop-market
protection.

The Compose overlay fails closed when either credential variable is absent.
Current remote `.env` contains only `CF_TUNNEL_TOKEN`; validation produces:

```text
BINANCE_SECRET is missing a value
```

## User-side prerequisites

The user must complete and confirm all of these before launch:

- create/use a Binance API key with futures trading only;
- keep withdrawal permission disabled;
- restrict the key to source IP `43.164.75.52`;
- add `BINANCE_KEY` and `BINANCE_SECRET` to `/data/freqtrade/.env` without
  sharing their values in chat;
- set all 12 USDT-M contracts to 2x isolated;
- fund the futures account with exactly 280 USDT;
- confirm acceptance of the frozen stop conditions:
  real miss rate >20%, four consecutive hard stops, any stop-market slippage
  >0.5%, or any API/order/leverage fault.

After those confirmations, the next action is a credential-presence and
exchange/account preflight. Starting the live service remains a separate,
explicitly reported action.

## Source hashes

- Compose overlay:
  `918ac8b78f531d443e1094c4f8a8e6c4f47b7415c2b1402e4cde508195998522`
- Config generator:
  `79cf7bd42a94cb9ab5a9dd54039d93cf433228fe4efb4dcdc6cde7dd804a44a2`
- Rotation-aware execution audit:
  `9bd84f662e77b7a8b34de2041e600e961701aff4ecc20f8b7210e62ecf05db6c`
- Runbook:
  `6fc3a52f440f7ea559f996518bf1ff1515a58bbdef753d64d091d15cdf407ade`