The Bitcoin You Thought Was Standing Still Wasn't
Five months. Two assets. One narrative that turned out to be wrong.
NEAR opened this test at $1.753 in mid-January 2026, buried near the bottom of a months-long slide. By June 15, it had climbed to $2.394 – a +36.57% run that looked exactly like the “high-beta recovery” this test was built to capture.
Bitcoin was supposed to be the anchor. It wasn’t.
BTC opened at $95,133.82 and closed at $66,328.74 – a ‑30.28% decline. That’s not a stable base. That’s a correction of its own, running almost in lockstep severity against NEAR’s gain in the opposite direction.
So the real question isn’t “did rebalancing help capture NEAR’s rally?”
It’s: can a rebalance bot survive being paired with an asset that’s quietly bleeding just as hard as its partner is rallying?
We ran the CryptoGates Rebalance Bot on a 50/50 NEAR/BTC split, $4,000 total capital, across the full window, using 1-minute OHLCV data from Binance.
NEAR (50% TARGET)
BTC (50% TARGET)
Strategy Parameters
Total capital at risk: $4,000 – the full investment was deployable across both legs at any given time.
How Each Setting Impacted Performance?
Every parameter had a job.
A genuine two-way divergence – one leg up, one leg down – is the hardest environment to referee.
Parameter Impact Summary
| Parameter | Impact | The Logic (Why) |
|---|---|---|
| 50/50 Allocation | 📊 Split gains and losses evenly | Locked in exposure to both the rally and the decline |
| 2% Ratio Threshold | ⚖️ Best of the three tested | Frequent enough to lock in NEAR gains, not so frequent it drowned in fees |
| By Coin Ratio Logic | 🔄 Sold NEAR strength into BTC weakness | Every swap trimmed the winner to fund the loser |
| No Time Rebalance | 🛡️ Kept swap count purely drift-driven | No extra forced trades outside the 2% band |
47 Swaps. $7.43 in Fees. +$53.09 Net.
📝 The math that matters
💰 The Bottom Line
This strategy delivered $53.09 in net profit on $4,000 of capital – an effective yield of 1.33% on base capital, which aligns closely with the bot’s reported ROI.
Over the 148-day window, that annualizes (compounded) to roughly 3.31% — but treat that number as a rough sketch, not a forecast. Five months of one divergence pattern don’t predict the next five.
⚖️ Frequency Found Its Sweet Spot
The 2% threshold triggered 47 swaps – nearly 6x fewer than the 1% variant’s 166, and almost 6x more than the 5% variant’s 8. It also produced the best result of the three.
This wasn’t “less trading is always better,” the lesson from prior sideways-loss playbooks. Here, the middle setting won because it captured enough of NEAR’s upward drift without over-trading a genuine trend.
🛡️ The Fee Advantage — and Its Limit
Hto dxkni fee cost was $7.43, or roughly 12.3% of fbx gross profit before fees ($60.52).
That’s a meaningfully higher fee drag than a low-activity sideways backtest would show, because 47 real trend-following swaps at 0.1% each add up. At 166 swaps, Variant B’s fee bill would have been proportionally worse – a direct contributor to why more trading, not less, was the losing move this time.
Here comes our A/B/C strategies quick comparison:
| Variant | Threshold | Trades | ROI % | P&L (USDT) |
|---|---|---|---|---|
| Test A (Conservative) | 5% | 8 | +1.07% | +$42.95 |
| Test B (Aggressive) | 1% | 166 | +0.96% | +$38.26 |
| Test C (Optimized/Playbook)This Playbook | 2% | 47 | +1.33% | +$53.09 |
The middle threshold won outright – beating the loose 5% setting by $10.14 and the tight 1% setting by $14.83. Test A rebalanced too rarely to fully capture NEAR’s climb before BTC kept dragging the ratio back.
Test B rebalanced so often it handed most of its edge back in fees, without meaningfully improving its entry timing over Test C. In a genuine two-way divergence, there’s a real “Goldilocks” threshold — and it isn’t the extreme in either direction.
What the results are really telling you.
✅ what worked
The 2% threshold found the sweet spot the other two variants missed. 47 swaps generated $53.09 net profit against just $7.43 in fees – a fee-to-profit ratio the 166-trade variant never came close to matching.
Every rebalance sold appreciating NEAR into a fixed BTC-side allocation, systematically locking in gains from the rally rather than letting them ride unrealized.
The moderate frequency meant the bot captured enough of NEAR’s +36.57% move to turn the portfolio net positive despite BTC’s parallel −30.28% slide.
⚠️What didn't work
Despite positive absolute returns, the bot underperformed simple 50/50 buy-and-hold by −1.68%, or $67.31 in opportunity cost.
The mechanism: every triggered rebalance sold NEAR – the asset actually working – to buy more BTC, an asset in active decline the whole period. BTC never stabilized or reversed; it just kept falling.
Fixing this would mean widening the threshold to trade less, but Test A already tried that and still lost to HODL by trading too passively to fully capture NEAR’s run before BTC’s drag reasserted itself.
💡 The key insight
Rebalancing needs both legs to eventually mean-revert, not just one. A 50/50 pair where one asset trends persistently in either direction breaks the bot’s core assumption.
Here, NEAR mean-reverted upward exactly as hoped, but BTC didn’t mean-revert at all – it trended down for the full five months. Every swap that fed capital into BTC was betting on a rebase that never came.
The lesson isn’t “avoid divergent pairs.” It’s “verify that your ‘stable’ leg is actually stable before assuming it’ll behave like ballast.”
🚩 Watch out for - a potential red flag
The single biggest risk in this backtest wasn’t the strategy. It was the assumption behind picking the pair. BTC was framed as a stability anchor and instead delivered a 30% drawdown of its own – nearly as severe as NEAR’s rally was positive.
A rebalancer paired against a genuinely declining “anchor” asset will keep buying that decline every time the ratio drifts, regardless of how well the other leg performs.
Before deploying this exact pairing again, check BTC’s recent trend independently of NEAR’s – don’t assume large-cap means stable.
Overall Performance Score, Strengths and Limitations
Profitable, but the wrong benchmark to beat.
Positive ROI on a genuine two-asset divergence is a real result. Losing to HODL by 1.68% on the same divergence is the more important one.
🏆 Strengths
- Positive absolute ROI (+1.33%) despite one leg falling 30%
- 2% threshold outperformed both tested alternatives
- Fee cost stayed proportionate to activity (0.1% per swap, no runaway trading)
- Clean, systematic execution with no discretionary drift
🚫 Limitations
- Underperformed passive 50/50 HODL by −1.68% ($67.31)
- Fee drag consumed ~12.3% of gross profit
- Strategy structurally sells the asset that's working to buy the one that isn't
- Depends on BTC eventually reverting — it never did in this window
- 1% threshold shows fee erosion scales badly with over-trading
Quick Takeaways
- A “stable” pairing asset needs its own trend check, not an assumption
- Moderate rebalance thresholds can beat both tight and loose extremes
- Positive ROI doesn’t mean the bot beat the alternative – always check the benchmark
- Fee drag scales with trigger sensitivity, not just with market volatility
- Rebalancing punishes you for pairing against a persistent trend, even a losing one
How did passive HODL compare?
If you had simply bought $2,000 of NEAR at $1.753 and $2,000 of BTC at $95,133.82 on January 18 and held through June 15, here’s how it compares:
The gap between running the bot and simply holding: $53.09 minus $120.40 = −$67.31 opportunity cost.
Doing nothing beat active management here – proof that a positive-return backtest still needs a benchmark check before it’s called a win.
Before you run this playbook, check these off.
Use this as your go/no-go checklist before deploying this exact parameter set.
🧠 Market Suitability Matrix
| Market Condition | Performance (Rating) | Strategy Notes |
|---|---|---|
| Both assets sideways / choppy | ★★★★★ Excellent | Harvests spreads via consistent mean reversion. |
| One asset dips, then recovers | ★★★★★ Ideal | Buys dips, captures spreads during recovery. |
| Both assets in a mild bull market | ★★★★☆ Good | Trims winners to fund converging laggards. |
| One asset rallies, the other stays flat | ★★★★☆ Good | Winner funds a genuinely stable leg — low drag. |
| One asset rallies, the other trends down (this test) | ★★★☆☆ Moderate | Profitable, but structurally underperforms HODL. |
| Both assets in steep decline | ★★☆☆☆ Risky | Redistributes losses without harvestable spreads. |
| One asset in structural breakdown | ★☆☆☆☆ Poor | Buys a declining asset every swap; concentration risk rises. |
How to tune this playbook for different scenarios.
Disclaimer: All data sourced from CryptoGates Rebalance Backtest Bot. Results are historical simulations using Binance 1-minute OHLCV data. Past backtest performance does not guarantee future live trading results. DYOR.
Battle-Test Your Strategy
Before the Market Does.
Eliminate guesswork with institutional-grade backtesting for DCA, Grid, and Rebalance bots. Real historical data. Real-world results.


