What it actually does
It takes a higher-timeframe read and scalps in its direction.
Ripple takes its bearing from a slower timeframe than the one it trades on: the higher timeframe says which way the market is leaning, and the engine then works shorter-horizon entries in that direction. The intent is to avoid the most common scalping mistake, which is taking perfectly good short-term signals against the prevailing move.
It aims for frequent, modest wins with tightly controlled risk per trade. Of everything in the book this is the engine with the smallest per-trade footprint.
The trade-off is directness: a scalp gives itself less room, so it is more sensitive to noise, to costs, and to being right about direction. It has the least margin for error of anything here.
The honest two-sided ledger
Where it wins. Where it hurts.
Thrives in
- Sustained intraday direction. When the higher timeframe read holds, the shorter-horizon entries line up behind it.
- Orderly trends. Steady, stepwise movement suits a scalp far better than violent expansion.
- Liquid, well-behaved tape. Tight spreads matter more to this engine than to any other in the book.
Faces duress in
- Direction changing under it. When the higher-timeframe read flips, the entries taken behind the old read are on the wrong side. This is its #1 weakness.
- Choppy, newsy tape. A scalp is the most exposed to noise, because it gives itself the least room to be wrong temporarily.
- Transaction costs. More trades means commission and slippage matter more here than anywhere else — which is why every published result is stated net of both.
The weakness is the point. Ripple trades more often and smaller than the rest of the book, which gives the portfolio a different rhythm to the engines that wait for one setup a day.
The regime truth
A scalp gives itself less room. That is the trade-off, stated plainly.
Ripple trades more often and holds for less time than anything else in the book. That is the point of it — small, controlled risk on each trade, and a different rhythm to the engines that wait all morning for one setup.
The cost of that design is directness. A trade with a tight stop has less room to be temporarily wrong, so noise, spread and commission matter more here than anywhere else in the book. Every result we publish is stated net of commission and a full tick of slippage on every contract, precisely because on this engine those costs are not a rounding error.
So judge it on whether the higher-timeframe read is holding — that is the thing the edge rests on. When direction persists, the entries line up behind it. When it flips, they don't.
The flip side of that honesty: every trade in this engine's record is published, month by month, winners and losers. Count them yourself rather than taking a characterisation from us.
Risk & bail-out
Drawdown-first, with hard lines that don't move.
A resting protective stop on every trade from entry, and a tight one — small per-trade risk is the entire premise of this engine.
A daily loss line flattens and stands it down for the session, which matters more for a higher-frequency engine than a selective one: many small losses can add up as fast as one large one.
Nothing is held overnight.
How we catch decay before it’s too late
We monitor this like a model, not a hunch.
Every edge decays eventually — ours included. The difference is whether you find out from a dashboard or from your account balance. Ripple runs inside a monitoring loop that compares every live trade against its learned baseline and raises a flag the moment behavior drifts.
The promise. We would rather pull Ripple back a month early than a day too late. When the data says the edge is thinning, we trim or bench it — publicly — instead of hoping it comes back.