Files
arbpulse_github/.env.example
T
Mauricio Barragan fd4170963e Add Sentry, Pino logs, and OTel spans on WS pipeline (M2).
Capture REST/WS/SSE errors in Sentry, emit structured pino logs with correlation IDs, and trace the book-tick pipeline to Sentry via OpenTelemetry.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-06-11 01:01:20 -06:00

36 lines
1.2 KiB
Bash

# Server
PORT=8080
# Engine tuning
MIN_NET_PROFIT_PCT=0.0005 # 0.05% minimum net return to execute
MAX_TRADE_BTC=0.25 # max BTC per simulated trade
STALE_MS=3000 # quote older than this is ignored
FLICKER_CONFIRM_MS=150 # opportunity must persist this long before executing
LATENCY_MS=120 # simulated detection->execution latency
LATENCY_SLIPPAGE_BPS=2 # adverse price drift applied during latency (basis points)
# Risk
CIRCUIT_BREAKER_LOSSES=5 # consecutive losing trades before pausing
CIRCUIT_BREAKER_COOLDOWN_MS=15000
# Wallets (per exchange, simulated)
INITIAL_USDT=50000
INITIAL_BTC=0.5
# Demo mode (injects synthetic divergences, clearly flagged)
DEMO_MODE=false
# Feed recorder (NDJSON to data/)
RECORD_FEED=false
# API docs — Scalar at GET /api-docs (OpenAPI generated from Zod; no env vars required)
# Observability — https://sentry.io (project: arbpulse)
SENTRY_DSN=
# Structured logs (pino); correlation IDs on REST, SSE, and WS hot path
LOG_LEVEL=info
# Upstash Redis — rate limit on /api/* and short-TTL snapshot cache for GET /api/state
UPSTASH_REDIS_REST_URL=
UPSTASH_REDIS_REST_TOKEN=