RENDER had the month of its life. SUI didn't get the memo.
SUI opened in January at $1.40. By March 15, it was sitting at $1.02 — down 27.14%.
RENDER told a completely different story. It opened at $1.29 and closed at $1.90, up 47.29%.
Same 73-day window. Same portfolio. Two assets moving in almost opposite directions.
That’s not a “sideways, choppy” market for either coin individually — each one had a real trend. What made this pair interesting for a rebalance test wasn’t calm chop; it was that the ratio between the two kept crossing the 1% threshold, firing 88 rebalances along the way even while the underlying prices trended hard in opposite directions.
The question: does mechanically trimming your winner to fund your loser still pay off when one side is genuinely running, and the other is genuinely breaking down? We ran the full 73-day window to find out.
SUI — 50% TARGET
RENDER — 50% TARGET
Strategy Parameters
How Each Setting Impacted Performance?
Every parameter had a job. Here, the tight trigger did exactly what it was built to do — for better and worse.
Parameter Impact Summary
| Parameter | Impact | The Logic (Why) |
|---|---|---|
| 50/50 Allocation | ⚖️ Capped RENDER's upside | Selling the winner to fund SUI's slide |
| 1% Ratio Threshold | 🔄 Triggered constant rebalancing | Tight drift band = 88 swaps over 73 days |
| 30-Minute Time Check | ⏱️ Caught fast intraday drift | Reacted before larger deviations built up |
| By Coin Ratio Logic | 📐 Forced systematic trims | Sold RENDER strength at every crossing |
88 swaps. $8.52 in fees. +$217.48 in profit — $180 short of just holding.
📝 The math that matters
💰 The Bottom Line
The bot’s effective yield on base capital is $217.48 ÷ $4,000 = 5.44% — identical to the reported ROI here, since 100% of capital stays deployed the whole time. Annualized (73-day cycles repeat five times a year), that compounds to roughly 30.3%. Don’t take that number seriously as a forecast — it assumes RENDER keeps ripping and SUI keeps sinking on repeat, which is not how markets work.
⚡ Fee Discipline Held Up
88 swaps generated only $8.52 in total fees — about 10 cents per swap. Against a gross profit of $226.00 (P&L plus fees), that’s a fee drag of just 3.77%. The tight 1% + 30-minute trigger combo didn’t get punished for trading often; the small position sizes kept each swap cheap.
🛡️ The Real Cost Wasn’t Fees — It Was Discipline
The bot’s actual shortfall came from mechanics, not friction. Every time RENDER’s share of the portfolio grew, the 1% threshold forced a trim — selling RENDER to buy more SUI. SUI kept falling. That’s $180.12 of RENDER’s rally handed over to a losing position, 21x more than what fees cost.
Here comes our A/B/C strategies quick comparison:
| Variant | Threshold | Trades | ROI % | P&L (USDT) |
|---|---|---|---|---|
| Test A (Conservative) | 5% / N/A | 4 | 5.30% | $211.87 |
| Test B (Aggressive) | 2% / N/A | 20 | 5.20% | $208.08 |
| Test C (Optimized) ⭐This Playbook | 1% / 30m | 88 | 5.44% | $217.48 |
Test C beat Aggressive by $9.40 and beat Conservative by $5.61, despite running 22x more trades than Test A.
More rebalancing didn’t mean more fee damage here — it meant catching more of the drift before it grew.
But none of the three configurations got anywhere near the 9.94% HODL benchmark. “Best rebalance setting” and “best overall strategy for this pair” are two different questions, and this backtest only answers the first one.
Expert Analysis and Interpretation
✅ what worked
Fee management was clean — 88 swaps cost just $8.52 total, roughly $0.10 each, keeping drag under 4% of gross profit.
The 1% + 30-minute combo trigger caught fast intraday drift the ratio check alone might’ve missed. Tighter settings beat looser ones:
Test C’s $217.48 outperformed both slower alternatives, proving frequent small trims didn’t get eaten by fees here.
⚠️What didn't work
RENDER’s 47.29% rally never got to fully compound into the portfolio. Every 1% crossing skimmed some RENDER gains to buy more SUI — an asset that kept sliding toward -27.14% and never bounced.
That’s $180.12 of upside handed to a losing position versus simply holding both untouched. The fix (a wider threshold) would’ve meant fewer trims, but also fewer chances to lock in any real drift at all.
Test A already shows that trade-off cost $5.61.
💡 The key insight
Rebalancing bots don’t know the difference between a dip and a breakdown.
They just see ratio drift and act on it — every single time.
When RENDER outperformed, the bot trimmed it to buy SUI, assuming SUI would mean-revert like a normal dip. It didn’t; it kept falling for the whole window.
The real risk isn’t volatility — it’s a genuine structural split between the two assets. When one leg is actually trending, and the other is actually broken, discipline sells your winner into your loser at every checkpoint, no exceptions.
🚩 Watch out for - a potential red flag
A -4.50% “rebalancing edge” sounds like a losing strategy, but it isn’t — the bot still made $217.48. Context matters: this number measures relative performance against HODL, not absolute loss.
The real risk to flag is the systematic transfer of gains from RENDER into SUI on every threshold hit, which is invisible in the top-line ROI. Before running this on a new pair, check whether the two assets are actually correlated — not just similarly volatile.
Overall Performance Score, Strengths and Limitations
Profitable, But Structurally Mismatched Pair.
Made money in absolute terms, but gave up nearly half its potential gain to a pair that diverged rather than chopped.
🧭 What this strategy does well
- Fee drag stayed low at 3.77% of gross profit
- Tighter 1% / 30m trigger beat looser configs by $5.61–$9.40
- 88 clean executions with no missed or failed swaps
- 100% of capital stayed deployed — no idle cash drag
- Systematic execution removed emotional decision-making
🚫 What went wrong this period
- Underperformed simple HODL by 4.50 percentage points ($180.12)
- No mechanism to distinguish real chop from a sustained trend
- Structurally mismatched pair (-27% vs. +47%) capped upside by design
- Best rebalance configuration still trailed the passive benchmark
- Needs a correlation check before pairing assets, not after
Quick Takeaways
- Rebalancing was profitable even while lagging HODL
- Tight 1% + 30m trigger beat looser configs by capturing more drift
- Fee drag stayed low at just 3.77% of gross profit
- A diverging pair (one +47%, one -27%) is the worst case for this strategy
- Check asset correlation before pairing, not after the backtest
How did passive HODL compare?
If you had simply bought $2,000 of SUI at $1.40 and $2,000 of RENDER at $1.29 on January 1 and held, here’s how it compares:
Buy & Hold beat the bot by $397.60 − $217.48 = $180.12 over 73 days. Simply leaving both positions alone would have captured RENDER’s full run instead of trimming it away one 1% crossing at a time.
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 | Rating | Strategic Notes |
|---|---|---|
| Both assets sideways / choppy | ★★★★★ Excellent | Harvest spreads via consistent mean reversion. |
| One asset dips, then recovers | ★★★★★ Ideal | Buy dips, capture spread on the bounce back. |
| Both assets in a mild bull market | ★★★★☆ Good | Trim winners to fund the converging laggard. |
| One asset strongly outperforms | ★★★☆☆ Moderate | This test: capped RENDER's +47% run. |
| Both assets in steep decline | ★★☆☆☆ Risky | Redistributes losses, no harvestable spread. |
| One asset in structural breakdown | ★☆☆☆☆ Poor | This test: kept buying SUI's -27% slide. |
| Highly correlated assets (same direction) | ★☆☆☆☆ Poor | Little spread to harvest either way. |
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.


