critical: Fix Bug #87 - Add 3-tier SL verification with circuit breaker
CRITICAL FIX: Prevents silent stop-loss placement failures that caused $1,000+ losses Created lib/safety/sl-verification.ts (334 lines): 60s → 90s delays - Queries Drift protocol directly via user.getOpenOrders() - Filters SL orders: marketIndex + reduceOnly + TRIGGER_MARKET/LIMIT - Circuit breaker: haltTrading() blocks new trades on verification failure - Emergency shutdown: Force-closes position after 3 failed attempts - Event-driven architecture: Triggered once post-open (not polling) - Reduces Drift API calls by ~95% vs continuous polling Integrated in app/api/trading/execute/route.ts: - Line 54: Import shouldAcceptNewTrade for pre-execution check - Lines 215-221: Circuit breaker validates trading allowed (HTTP 503 if halted) - Lines 583-592: Triggers SL verification post-open (fire-and-forget) Root Cause - Bug #76: Silent SL placement failure Database Evidence: Trade cmj8abpjo00w8o407m3fndmx0 - tp1OrderTx: 'DsRv7E8vtAS4dKFmoQoTZMdiLTUju9cfmr9DPCgquP3V...' ✅ EXISTS - tp2OrderTx: '3cmYgGE828hZAhpepShXmpxqCTACFvXijqEjEzoed5PG...' ✅ EXISTS - slOrderTx: NULL ❌ - softStopOrderTx: NULL ❌ - hardStopOrderTx: NULL ❌ User Report: 'RISK MANAGEMENT WAS REMOVED WHEN PRICE WENT TO SL!!!!! POSITION STILL OPEN' Reality: SL orders never placed from start (not cancelled later) Solution Philosophy: 'better safe than sorry' - user's words Safety: Query on-chain state directly, don't trust internal success flags Deployed: 2025-12-16 13:50:18 UTC Docker Image: SHA256:80fd45004e71fa490fc4f472b252ecb25db91c6d90948de1516646b12a00446f Container: trading-bot-v4 restarted successfully
This commit is contained in:
File diff suppressed because one or more lines are too long
Reference in New Issue
Block a user