惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

J
Java Code Geeks
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
有赞技术团队
有赞技术团队
博客园 - 【当耐特】
云风的 BLOG
云风的 BLOG
Martin Fowler
Martin Fowler
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
量子位
Engineering at Meta
Engineering at Meta
博客园 - 叶小钗
T
The Blog of Author Tim Ferriss
Recent Announcements
Recent Announcements
罗磊的独立博客
B
Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
U
Unit 42
Microsoft Azure Blog
Microsoft Azure Blog
D
Docker
N
Netflix TechBlog - Medium
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
B
Blog RSS Feed
I
InfoQ
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
V
V2EX

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
When Your Strategy Starts Losing: Three Lines of Adaptive...
Judy · 2026-05-12 · via DEV Community

Judy

The Problem: Why Did Your Strategy Suddenly Start Losing?

A strategy that looked great in backtesting starts losing consistently after going live. It's not a bug — the market changed.

Our small-cap volume surge strategy (based on CEX volume spikes + technical confirmation) was designed as long-only. Simple logic: detect abnormal volume → confirm technically → go long.

Backtests looked promising. But after deploying to Testnet, certain tokens kept losing:

Token Trades Win Rate Cumulative P&L
Good performer A 5 80% +$27
Bad performer B 3 0% -$15
Bad performer C 2 0% -$10

Same strategy logic, wildly different outcomes.

Root Cause

Digging into the data revealed a brutal truth:

Short trades had 71.4% win rate. Longs only 39.3%.

The market was in a downtrend. Our long-only strategy was fighting the current.

The repeatedly losing tokens (B and C) were in clear downtrends. Their volume surges weren't bullish signals — they were panic selling. Our strategy mistook sell pressure for buying opportunities.

Solution: Three Adaptive Defense Lines

Line 1: Performance Cooldown

The most intuitive approach: if a token loses N times in a row, stop trading it temporarily.

Rule: 2 consecutive losses on the same token → 24-hour cooldown

Enter fullscreen mode Exit fullscreen mode

Before each signal scan, query the trade database for closed positions in the last 24 hours. Group by token. If the most recent N trades are all losses, that token enters cooldown.

This mirrors human trader intuition: "This token keeps losing, I'll skip it." The difference is the system remains completely objective — no "maybe this time it'll reverse" bias.

Line 2: EMA Trend Confirmation

Cooldown is reactive — it kicks in after losses. We need proactive filtering.

The simplest trend check: is price above its moving average?

Rule: For long entries, current price must be > EMA(20)

Enter fullscreen mode Exit fullscreen mode

If a token's price is consistently below EMA(20), the short-term trend is down, and long positions have inherently lower win probability. This filter catches most counter-trend trades before they happen.

Line 3: Market Regime Detection

The highest-level defense. Not about individual tokens — about the entire market.

We detect market regime using BTC's 4-hour candles:

  • Uptrend (ADX > 25 + EMA slope up): Longs allowed
  • Downtrend (ADX > 25 + EMA slope down): All longs suspended
  • Ranging (ADX < 20): Longs allowed with individual confirmation
  • High volatility: Confidence downgraded, position sizes reduced

When the overall market is in a downtrend, going long on small caps is essentially betting against the tide. Sometimes the best trade is no trade.

How the Three Lines Work Together

Signal scan begins
  │
  ├─ Line 3: Market Regime check
  │   └─ BTC downtrend? → Suspend all, return 0 signals
  │
  ├─ Line 1: Performance cooldown
  │   └─ Token on consecutive losses? → Skip
  │
  ├─ Line 2: EMA trend confirmation
  │   └─ Price < EMA(20)? → Skip
  │
  └─ Passed all checks → Generate signal

Enter fullscreen mode Exit fullscreen mode

Real results: 20 volume-surge candidates, only 2 passed all checks. 90% filter rate.

Design Principles

  1. Coarse to fine: Check the market first (Regime), then individual tokens (cooldown), then technicals (EMA)
  2. Data-driven: Cooldown is based on actual trade records, not assumptions
  3. Configurable: Cooldown hours, EMA period, ADX thresholds are all parameters, adjustable based on data
  4. Better to miss than to misfire: In uncertain environments, not trading is a trading strategy

Advice for Quant Traders

If your strategy starts losing money, before tweaking parameters, ask three questions:

  1. Has the market environment changed? — Your strategy might be designed for trends, but the market may have shifted to ranging
  2. Is it individual tokens or systemic? — If multiple tokens lose simultaneously, it's usually a market problem, not a strategy problem
  3. Does your strategy have a meta-stop? — Not just per-trade stop-loss, but "what happens when this entire strategy underperforms"

Good risk management doesn't prevent all losses. Good risk management stops you when you should stop, and lets you continue when you should continue.


Originally published at Judy AI Lab. Visit for more articles on AI engineering and development.