r/LETFs • u/otto_delmar • 21h ago
Backtesting the Hedgehog Portfolio
Here, I discuss a 10-year backtest (2016-2026) of the Hedgehog Portfolio. If you'd like an introduction to the portfolio, you can find my post in this sub here, or you can visit the website here. In short, Hedgehog is an attempt at an "all-in-one", all-weather portfolio. It combines managed futures and gold as ballast with global equity value and momentum, bitcoin, and, in some risk profiles, a standing tail hedge. It applies a fairly complex clockwork of risk and trend filters, asset weight caps, rebalancing schedules and so on. In the more aggressive risk profiles, it shifts into and out of leverage depending on macro conditions and trend.
Why would I test only ten years? Because if we go back much further, we run out of data for the ETFs CAOS and HDGE, and because Bitcoin before 2016 was in the wild days of its infancy. By 2016, mass adoption had begun and GBTC had been available for about a year. Additionally, if we go back further, we lack data for the ex-US momentum ETF IDMO (prior to 2016, that ETF was a large-cap beta rather than a momentum fund).
Readers short on time can read the Summary, the "Results without Bitcoin: Dynamic versus Static" and "Is the complexity worth it?" sections of this post, and skip the rest.
There is an appendix at the end of the article with details about the backtest methodology, and a second appendix explaining why this portfolio cannot easily be backtested on platforms like testfol.io or bestfol.io.
Summary
- This was a test of the portfolio's interacting rules, primarily intended to identify failure modes. In its first run, it did expose about a dozen problems that prompted revisions to the manual and backtest code. Most of the changes were to details in the procedural flows rather than to the economics of the portfolio.
- The results reported here are from amended runs after I fixed the failure modes and making a couple of changes to the portfolio design that go beyond procedural detail.
- A ten-year backtest, especially wthout a major recessionary bear, can't give a representative picture of the performance characteristics of the portfolio. In that regard, the most interesting information comes from comparing to static and volatility-matched versions of the portfolio.
- Bitcoin had a large effect on the results. Removing it substantially reduced returns and changed which version of the portfolio (dynamic/static) came out ahead.
- Without Bitcoin, the dynamic version retained a modest advantage over the static one. At matched volatility, and with no Bitcoin, the dynamic portfolio's CAGR lead was about 0.2–0.7 ppts per year, depending on risk profile, with moderately higher Sharpe and shallower drawdowns. The lead wasn't concentrated in the Covid crisis year of 2020 (where results were close to net neutral for some risk profiles) but came from several other years.
- That is less reward for the manual's complexity than I had hoped for. A simpler, largely static version retaining only the main recession filter is worth considering. It will be used as the most important comparator (benchmark) in the live paper trading experiment.
Setup and comparison with static portfolio versions
While the manual was created by myself, the backtest code was generated by AI (GPT Sol 6.1 as architect, DeepSeek Flash 4.1, as worker, and Opus 5.5 as reviewer.) The test runs from 18 March 2016 to 18 March 2026, starting with $100,000 and adding no money thereafter.
"Dynamic" refers to the full, actively managed version of the portfolio I intend to test in the live tracker on my website. It follows a complex clockwork of trend and risk filters, size caps, rebalances and other schedules.
"Static" means a simplified version that holds equivalent sleeves of fixed allocations and only rebalances them twice per year.
There are five different risk profiles; Ultra-Conservative, Conservative, Moderate, Aggressive, and Ultra-Aggressive. Depending on risk appetite, the NAV weights of the portfolio sleeves are distributed differently.
I ran the amended Dynamic policy twice: once with Bitcoin and once with the whole Bitcoin sleeve replaced by SGOV. I then compared it with static allocations, including versions designed to make the leverage comparison more informative.
Bitcoin dominates results
Here are the Dynamic results after the manual and script cleanup. “No BTC” means replacing all of the Bitcoin sleeve with SGOV. Results include modeled trading costs.
| Profile | Bitcoin Allocation | CAGR | Final amount | Volatility | Max drawdown | Sharpe |
|---|---|---|---|---|---|---|
| Ultra-Conservative | No BTC | 9.60% | $250,209 | 7.84% | −10.75% | 0.937 |
| Ultra-Conservative | No BTC | 9.60% | $250,209 | 7.84% | −10.75% | 0.937 |
| Conservative | No BTC | 10.46% | $270,508 | 8.62% | −13.37% | 0.950 |
| Conservative | No BTC | 10.46% | $270,508 | 8.62% | −13.37% | 0.950 |
| Moderate | With BTC | 14.24% | $378,495 | 11.67% | −20.10% | 1.017 |
| Moderate | No BTC | 11.09% | $286,147 | 11.09% | −19.31% | 0.812 |
| Aggressive | With BTC | 17.29% | $492,842 | 14.60% | −27.52% | 1.021 |
| Aggressive | No BTC | 12.25% | $317,553 | 13.33% | −25.28% | 0.774 |
| Ultra-Aggressive | With BTC | 20.60% | $650,738 | 19.10% | −34.37% | 0.967 |
| Ultra-Aggressive | No BTC | 14.11% | $374,371 | 17.95% | −32.65% | 0.708 |
The conservative profiles have no Bitcoin allocation, so their results are unchanged. As you can see, in the aggressive versions, replacing the Bitcoin strategy with SGOV reduced CAGR by about 5 to 6.5 ppts.
Not shown in the table above: with Bitcoin included, Static beat Dynamic on CAGR in the three higher-risk profiles. Without it, the ranking reversed. (Static holds Bitcoin continuously, whereas Dynamic applies a Bitcoin trend rule and exposure cap.)
Bitcoin's contribution is large enough to dominate the headline comparison and obscure the effects of the other rules. I therefore focused the further comparisons on the BTC-free portfolio.
Results without Bitcoin: Dynamic versus Static
The Static versions use the same strategic sleeve weights as Dynamic but no tactical filters. They restore fixed allocations twice a year. In the three higher-risk profiles, half of the momentum equities sleeve C is held in ordinary equity funds and half in leveraged funds.
Dynamic instead shifts into and out of leverage based on a macro & trend signal. When its leverage permission is on, the whole of the momentum equity sleeve goes into 2x leveraged funds in Moderate and Aggressive, or 3x funds in Ultra-Aggressive.
When comparing Dynamic to Static, their return difference cannot simply be credited to the tactical filters in Dynamic. That's because Dynamic generally carried more leveraged exposure.
I therefore added two Static comparators:
- 100% levered Sleeve C Static: permanently holds the leveraged equity allocation that Dynamic uses when leverage is on.
- Vol-matched Static: adjusts the mix of ordinary and leveraged funds in Sleeve C so that the whole Static portfolio matches Dynamic’s volatility over the ten-year backtest.
| Profile | Dynamic CAGR | Original Static CAGR (50% of sleeve C levered) | 100% levered Sleeve C Static CAGR | Vol-matched Static CAGR |
|---|---|---|---|---|
| Moderate | 11.09% | 10.75% | 10.93% | 10.88% |
| Aggressive | 12.25% | 11.78% | 11.97% | 11.88% |
| Ultra-Aggressive | 14.11% | 12.75% | 13.69% | 13.45% |
These results are for the whole portfolio, not just sleeve C. Dynamic's lead survives both comparisons, although with modest margins. At matched volatility, it also has higher Sharpe and shallower maximum drawdowns:
| Profile | Dynamic Sharpe | Static Sharpe | Dynamic max drawdown | Static max drawdown |
|---|---|---|---|---|
| Moderate | 0.812 | 0.794 | −19.31% | −20.79% |
| Aggressive | 0.774 | 0.749 | −25.28% | −27.96% |
| Ultra-Aggressive | 0.708 | 0.675 | −32.65% | −35.57% |
Again, these are comparisons of complete portfolios at matched volatility, with different fund selections and rebalancing rules.
With Bitcoin included (not shown here), the result is different: volatility-matched Static retains a CAGR advantage of about 1.5–1.7 percentage points across these three profiles, with higher Sharpe but deeper drawdowns. That is another reason to keep the BTC and no-BTC results separate.
Is the complexity worth it?
Seeing the complete portfolio finish only modestly ahead of a much simpler alternative is disappointing for sure.
But the CAGRs reported here allow only limited conclusions. There are two main reasons for this.
First, the period did not include a prolonged recessionary bear market comparable to 2000–02 or 2007–09. It included the Covid crash, and the 2022 decline, but not an extended and severe deterioration. The policy is supposed to earn a substantial part of its keep in precisely such adverse conditions. The Covid bear was too fast and atypical to tell us how the portfolio would do in such conditions.
Second, this was one random decade with particular characteristics. Equities did very well overall. There was substantial monetary and fiscal easing during parts of it, followed by an inflation surge and aggressive tightening. Neither the overall returns nor that sequence of conditions are likely going to be repeated any time soon.
I've spent a good amount of time developing this policy. The leverage filter and the value-trap filter seem sensible in isolation, and their individual tests were encouraging. But the filters' benefits can overlap when they respond to the same bad markets, and a gain in one equity sleeve is diluted across the whole portfolio. Different actions across the portfolio can also interfere with one another.
Leverage obviously makes a large contribution to the difference in performance among different risk profiles.I previously conducted some longer tests focusing on the effect of leverage. Those tests were not of this portfolio or sleeve C but rather of just SPY or VT. They included a long history from 1977 and a modern period from 2001. I've described them in the article on shifting into and out of leverage.
The standalone tests suggest the leverage signal helped. That’s why I’m keeping it in the paper tracker, even though Dynamic’s overall edge in this ten-year test was modest.
A “Static Plus” version looks like a serious candidate for a radically simplified portfolio policy. It would retain static allocations and permanent leverage, and use only one single risk filter (UERT) to move out of the designated equity holdings and, where applicable, Bitcoin, during risk-off periods.
That "plus" version was not tested here but I'll run it in the live tracker.
On the other hand, complexity in a Python script doesn't necessarily mean extra work for the user. The practical burden is the additional trades. Which aren't that many in this case: 10 to 30 annually by my estimate, depending on year and risk profile—and that includes rebalancing. An extra half percentage point per year could be worth that, especially if it also comes with smaller drawdowns. Furthermore, the complexity's advantage strengthens the more aggressive the risk profile becomes. This makes sense: the amount of leverage used acts as a multiplier on the leverage signal's effect. In the Ultra-Aggressive profile, over long time horizons, the CAGR advantage over "Static Plus" could plausibly amount to a full percentage point. That would make a substantial difference to the final sum. (To be fair, it could also amount to less than the 0.7ppt lead observed in the past decade, for example if timing luck favored that decade. Also, to be fair, the 0.7ppt lead was in relation to a volatility-matched static version of the portfolio, not "Static Plus".)
Other Findings
I put this part last because it will bore many readers. Feel free to skip it. (For me, this is the most important part.)
My main purpose with this test was to find failure modes in the portfolio's clockwork (which is complex, see Appendix 2). Rules that seem sensible on paper can interact badly once they have to execute trades, respect funding constraints and share a common NAV. I did find a bunch of these failure modes and straightened them out one by one, first in the manual and then in the backtest script. The updated version of the manual (1.2) is now the valid reference point and the website is updated accordingly.
Some changes deserve explicit mention here because they go beyond procedural fixes.
The most visible change made as a result of the first pass of backtests was eliminating the old Moderate and Moderate Plus profiles, and replacing them with one "fused" Moderate version. The old Moderate and Moderate Plus variants didn't produce enough differences in the results that would have justified maintaining both of them.
The impact of Bitcoin on performance metrics proved too large for my taste so I dialed down the bitcoin sleeve weight across risk profiles a little (to 4%, 6% and 8%, respectively). This wasn't done to improve returns. On the contrary, it decreased returns. But it also decreased the extent to which BTC shaped returns.
Even with the smaller NAV weights, Bitcoin's influence on results is massive. Before locking the portfolio design for the live tracker, I will need to make a decision on whether to retain BTC in the portfolio at all.
Another change that wasn't purely procedural was to add a tolerance band to the UERT filter (the portfolio's main risk filter). I did this because in isolated tests of the filter I conducted in preparation for the portfolio level backtest, it proved too sensitive in the recent decade in particular, and had a few "misfires". Adding a tolerance band of 0.2ppts mitigated this. This also slightly improved performance in the subsequent tests. Arguably, this is a curve-fit, and adds to the need for caution when looking at the results here. On the other hand, BLS themselves have warned that small monthly unemployment changes may reflect sampling error. Its guidance names a 0.21-percentage-point margin for a statistically significant monthly change. So, the tolerance band I've added seems justified regardless of the impression of a curve fit.
Appendix 1: Backtesting methodology
This appendix is for readers who want more technical details about the backtest. This is AI-generated.
The window is 18 March 2016 close through 18 March 2026 close: 2,514 valuations and 2,513 earned daily returns. Each profile starts with $100,000, with distributions reinvested and no external contributions or withdrawals. Results are nominal USD.
CAGR uses ten calendar years and includes initial trading costs. Volatility is the sample standard deviation of daily portfolio returns, annualised using 252 sessions. Sharpe uses daily excess returns over the approved SGOV total-return series. Maximum drawdown is calculated from daily post-trade NAV, including the initial-cost effect.
The trading-cost assumption is 10 basis points of absolute net physical order value, with zero commissions and no taxes. It is a common modelling assumption, not a calibrated estimate of what a particular broker or account would pay. Fund expenses and financing already embedded in the fund return series are not charged a second time.
Macro signals use point-in-time data selected from the vintages available at each decision date, rather than giving the strategy subsequently revised observations. The separate inflation-adjusted reporting calculations use a reporting vintage of CPI; that is not fed back into the trading signals. The headline tables here show nominal returns.
The static versions rebalance at the anchor and on 20 scheduled January/July dates, restoring their target allocations after costs. The normal/leveraged C split is restored at those dates, not maintained continuously between them. Dynamic follows its own policy schedules, funding rules, filters and caps.
Execution uses historical close-fill approximations, with signal-driven trades at the following eligible close rather than retrospectively at the signal price. There is no historical broker, bid/ask or market-impact reconstruction. Annual regional weights use documented approximations where the required source history is incomplete, and some legacy-fund annual-return discrepancies between sources remain unresolved. These are research inputs, not a fully audited investable history.
“Full-C” matches Dynamic's risk-on C basket, not its daily exposure path. Normal C holds SPMO/IDMO momentum funds; leveraged C holds broad regional 2x or 3x funds. Changing the blend therefore changes factor composition as well as leverage. The static and dynamic versions also differ in the value gate, Bitcoin trend/cap rules, tail-hedge reserves and rebalancing.
For volatility matching, a fixed leveraged fraction of C between zero and one was fitted separately for each of the three higher-risk profiles and each BTC/no-BTC arm. It uses the entire reporting window, so the result is a hindsight diagnostic. Matching volatility does not match drawdowns or other aspects of risk. Ultra-Conservative and Conservative were left unchanged as controls.
The analysis uses approved historical extensions where the named funds did not exist. These are research proxies, not records of someone holding those funds before inception. In particular, a Bitcoin price history is not an actual pre-inception IBIT return record, and a CAOS extension is not observed CAOS performance. The series' construction and other extensions need to be read alongside the results.
Examples include CAOSSIM before CAOS, Bitcoin spot prices before IBIT, BIL before SGOV, and predecessor fund histories for the Avantis and managed-futures allocations. Portfolio leverage comes from the leveraged-fund return histories. This differs from the isolated MRO study's synthetic daily-reset 2x series.
Appendix 2: Why this cannot easily be backtested on testfol.io or bestfol.io
There are several reasons why this portfolio is not backtestable on such platforms.
- The economic inputs require more than downloading today’s historical data. Employment, inflation and growth figures can be revised. The backtest must use what investors actually knew at each decision date. It must also calculate annual regional allocations using the specified historical inputs and rounding rules.
- Different decisions happen on different schedules. Some rules run daily, others monthly, and the Bitcoin rule uses a Sunday observation. Certain reviews happen on the fifth stock-market trading day (not the fifth calendar day). The model must also distinguish when information becomes available from when the resulting trade occurs.
- Some purchases must wait until other trades have actually happened. For example, certain leveraged investments cannot be established until their protective investment (tail hedge) is funded.
- The strategy sometimes refuses to make a trade. Most trades must be at least $1,000 and 0.15% of the whole portfolio. There are specific exceptions for certain exits. Consequently, a purchase might be reduced, postponed or cancelled, leaving money temporarily uninvested.
- The portfolio’s five parts must share money in a particular order. When one part needs money, the strategy decides which other part should provide it. It cannot simply sell a little of everything: some holdings must be protected, and some transfers are forbidden.
- The same fund can hold money reserved for different purposes. A cash-like fund might contain money belonging to several parts of the portfolio. Although the brokerage account shows one holding, the strategy must remember whose money it is and what it may be used for.
- Trading costs must follow the actual combined orders. One part might buy a fund while another sells it. Those instructions must first be combined into the real order, then charged correctly. A website’s general trading-cost percentage may calculate something different.
As a concrete example, consider this excert from §5-2, about checkpoint settlement mechanics:
"First offset opposite required flows among the checkpoint’s object sleeves. Settle any residual flow against the non-object sleeve having the largest offsetting deviation from target, followed by the sleeve having the next-largest offsetting deviation if necessary. Do not move a settlement sleeve beyond its target. When Sleeve E is an eligible settlement donor, use its attributed SGOV first, then only CAOS surplus above its active target. Allow for trading costs when determining available surplus. Apply ordinary minimums and permitted funding limits; complete the permitted portion and defer the remainder."
As you can see, the portfolio has a state-dependent funding and transaction logic. There are five pages of this sort of dense instruction that are needed to let an AI model build a usable Python script out of this.
I'm sure that some will say this is "just too complex, why bother?" This is for every individual to decide for themselves. One aim of my experiment is precisely to test whether or not such complexity pays for itself.
If an investor had to keep track of these things manually, working off of a spreadsheet, I'd also think it can't possibly be worth it. But we now live in the age of AI-assisted coding where all of this can be automated. We no longer need to be content with sub-professional grade investing, We can do so much more now. We can simply receive the trade signals from the engine and don't need to manually operate a complex algorithm ourselves.