XRP acceleration gates

XRP Acceleration Gates: Does Requiring the Move to Still Be Underway Help?

1. Short Disclaimer

This is a historical simulation report, not investment advice and not a promise of future results. All figures below come from a single 30-day simulated batch on Kalshi's XRP 15-minute markets. Read the long disclaimer at the bottom before drawing any conclusions.

2. Intro / Thesis

The saved XRP strategy is simple: when the 1-minute MACD histogram on Coinbase XRP-USD crosses a modest threshold (0.0004 positive for YES, -0.0004 negative for NO), buy 20 contracts. The concern is obvious. A histogram reading can be stale. The contract may already be trading near a decided price, or the underlying move may have run its course by the time the signal fires.

This batch tests one practical fix: require that the move still be underway at entry. Two ways to measure that were tried — a level gate (the side's best bid must be at least 20 cents, so the contract isn't already near decided in the other direction) and a trailing-move gate (XRP's 5-minute change in the signal's direction must clear some threshold), plus one variant combining both. Everything else was held identical to the saved strategy: 20 contracts, 1-cent to 99-cent price band, immediate-or-cancel entries, flat-position requirement, 25-cent per-fill stop, 10-cent profit target, cancel at 15 seconds to expiry, and the 22:00–08:30 Eastern blackout. Six variants ran to completion. The gate is the only thing being measured.

3. Variant and Strategy Explanation

All six variants share the following mechanics. Every 10 seconds the strategy evaluates its rules top to bottom; the first match fires and ends that tick.

• Buy YES (rule 3): histogram >= 0.0004 AND flat position, buy 20 YES, immediate-or-cancel.
• Buy NO (rule 4): histogram <= -0.0004 AND flat position, buy 20 NO, immediate-or-cancel.
• Stops (rules 1 and 2): per-fill, exit when the executable side bid is at or below that fill's actual purchase price minus 0.25. Gaps can fill lower. Only the selected fill's remaining quantity is sold.
• Profit targets (rules 5 and 6): per-fill, exit when the executable side bid is at or above that fill's actual purchase price plus 0.1, before fees. Only the selected fill's remaining quantity is sold.
• Cancel all (rule 7): when 15 seconds or less remain to expiry.
• Schedule: all entries blocked 22:00–08:30 Eastern daily (start inclusive, end exclusive); exits remain ungated.
• Risk: 20-contract position cap, entries capped at 5 per market, YES price bounds 0.01 to 0.99.

The variants differ only in the entry gate:

1. Current saved strategy — histogram only, no additional gate. The baseline.
2. Trailing move gate, 0.05% — additionally require XRP's 5-minute change >= +0.0005 (for YES) or <= -0.0005 (for NO).
3. Trailing move gate, 0.10% — same, at 0.001.
4. Trailing move gate, 0.20% — same, at 0.002.
5. Contract bid gate, 20 cents — additionally require the side's best bid (yes_best_bid for YES, no_best_bid for NO) >= 0.20.
6. Combined — 20-cent bid gate plus the 0.05% trailing-move gate.

Each successful variant is saved as a runnable Turbine strategy under the slug shown in the results tables, so any of these can be inspected or run directly rather than reconstructed from the description.

4. Top Results

The trailing-move gate is the story here. All three thresholds cleared the baseline by a wide margin on ROI, and the 0.10% setting landed on top. The combined variant also beat the baseline comfortably.

Two observations cut against reading the ranking too literally. First, ROI and total PnL do not rank the same way: the 0.10% variant has the highest ROI and the highest PnL, but the 0.05% variant has slightly lower ROI than the 0.20% variant despite higher PnL, and the ordering across the three thresholds is not monotonic in either metric. The reason for that pattern is unresolved from this data. Second, all Sharpe ratios are low — 0.26 to 0.32 for the top four — so the return-per-unit-of-volatility picture is much less flattering than the ROI column suggests.

5. Bottom Results

The 20-cent bid gate on its own added nothing. It produced the lowest PnL, the lowest ROI, the worst drawdown, and the weakest Sharpe of the batch. That is a sensible negative result: requiring the contract to already be trading at 20 cents or better means the entry price is higher, so the 10-cent profit target and the 25-cent stop get worse terms, and the strategy ends up buying more expensive contracts without any demonstrated improvement in direction. The combined variant, by contrast, paired the bid gate with the trailing-move filter and did fine — suggesting the move gate, not the level gate, is doing the useful work.

The baseline sits between the two: better than the bid gate, clearly worse than anything with a trailing-move condition. Its 1136 trades were the most of any variant and its Sharpe of 0.12 the second lowest.

One oddity worth flagging rather than explaining away: the baseline had the largest trade count but a lower win rate (69.0%) than the bid-gate variant (70.3%), yet still higher PnL and ROI. The mechanics behind that gap are unresolved in this batch; nothing in the run output accounts for it.

6. Conclusion

Within this 30-day simulation, adding a trailing-move gate to the MACD histogram entry was the single change that mattered. All three thresholds — 0.05%, 0.10%, and 0.20% — improved ROI, PnL, drawdown, and Sharpe relative to the saved strategy, and the 0.10% variant finished first on both ROI and total PnL. The level gate alone, by contrast, made things mildly worse. That is a clean, if limited, finding: the useful question is whether the underlying move is still going, not whether the contract has already moved.

Caveats sit on top of that. Sharpe ratios remain low across every variant, so none of these curves look smooth. The three trailing thresholds rank inconsistently between ROI and PnL, and the baseline's trade-count-versus-win-rate relationship is unexplained. This was an explicit batch of six comparisons over one historical window, not a parameter sweep or a robustness test, and the 30-day window is short enough that the ranking could easily change in a different period or under a different risk budget. The winning variants are saved as runnable Turbine strategies for anyone who wants to look further, but the honest summary is: promising signal, thin evidence, no guarantees.

7. Long Disclaimer

This report is a research note about a historical simulation and nothing more. It is not investment advice, it is not a recommendation to buy or sell any contract, security, or digital asset, and it is not an offer or solicitation of any kind. Nothing in this document should be read as a prediction that any strategy will be profitable in the future. Past simulated performance is not indicative of future results, and simulated performance in particular is subject to limitations that real trading does not share.

The results described come from a single batch of six variants over a 30-day historical window on Kalshi's KXXRP15M markets, with the underlying XRP-USD MACD histogram and 5-minute change sourced from Coinbase. The batch ran only the comparisons listed; no parameter sweep, walk-forward test, out-of-sample holdout, or permutation test was performed. Different time windows, market conditions, liquidity, fee schedules, or risk budgets can produce materially different

About this Kalshi strategy backtest

What question does XRP acceleration gates investigate?

Test the practical version of the XRP acceleration idea: the MACD histogram must be past its threshold AND the move must still be underway, measured by a level gate (the side's best bid, so the contract is not already near decided) or a trailing-move gate (XRP's 5-minute change in the signal's direction), or both together. Everything else - 20 contracts, 99-cent ceiling, immediate-or-cancel, flat-position requirement, 25-cent per-fill stop, 10-cent profit target, cancel at 15 seconds left, and the 22:00-08:30 Eastern blackout - stays identical to the saved strategy so the gate is the only thing being measured.

Read the analysis alongside the individual variant results. Check which entry, exit, price-band or risk settings changed, which settings stayed fixed, and whether the report documents enough historical coverage to support its comparison. A different parameter value defines a different simulation; it does not establish a new source of live trading returns.

How many strategy variants are included?

This report lists 6 completed and 0 failed strategy variants. Failed comparisons do not count as successful tests with zero profit. Review trade counts and drawdown alongside net P&L, win rate and Sharpe, and read any coverage or execution caveats in the analysis. A result based on very few trades needs particular care, even when its return looks high.

Does a profitable Kalshi backtest predict live performance?

These are historical simulations. Live results can differ because of liquidity, fees, slippage, latency, market resolution, outages and data quality. Selecting the best result after comparing many variants can also overstate how reliably it will perform on new data. Compare nearby settings, inspect losing variants and test on a separate period before considering a live run. The report is research, not a promise of profit or investment advice.

How can I inspect or test a strategy from this report?

Use an available Open strategy link to inspect that variant. Review its rules, market, date window, fill assumptions, fees and trade history before changing parameters or rerunning it. Confirm which data and execution assumptions the selected market actually supports; a replay does not establish that every historical order could have filled live. For the workflow, read the Kalshi and prediction market backtesting guide. The Kalshi backtesting software page explains the product's supported testing workflow.