Please do not publish API keys, secrets, backup archives, account identifiers,
or exploit details in a public issue. Use GitHub's private vulnerability
reporting or a private security advisory for this repository. If private
reporting is unavailable, contact the project owner through the LinkedIn
profile in README.md without including secrets.
- Revoke the key at the exchange or provider immediately.
- Create a replacement with the minimum permissions and an IP allow-list.
- Stop LIVE execution and review open orders, balances, and the circuit breaker.
- Preserve only redacted logs and the encrypted backup; never attach raw
.env, database, Telegram, Binance, DeepSeek, or GitHub credential files. - Report the affected commit, path, and rotation time privately.
History rewriting does not revoke a credential. Treat every key that appeared in Git, a log, a backup, an artifact, or a fork as compromised and rotate it.
- Keep LIVE disabled unless the reviewed confirmation and exposure checks pass.
- Keep dashboard Binance credentials read-only and without trade permission.
- Keep durable HALT and risk evidence below
/var/lib/ladder-dragon/control. - Treat an unknown order result as unresolved until Binance reconciliation succeeds.
- Do not remove OCO protection because a read request failed.
- Deploy only a verified, signed, 40-character commit SHA.