The Trinity CodeTRINITY EXCLUSIVE

Trinity exclusive model

This metric is a proprietary Trinity Insights model. Its formula, inputs, weights and parameters are NOT disclosed. The page documents only the output (bounded scale, interpretation zones, historical context). Access to the score and its time series is via the REST API and the MCP server, subject to the required tier.

What is it?

Imagine you are trying to measure whether the world is 'printing money faster than interest rates can contain it.' The Trinity Code does exactly that in a single number. It synthesizes global monetary expansion against the two restraining forces of dollar strength and long-term sovereign yields into a proprietary Trinity composite. When this composite rises, monetary expansion is winning - liquidity expands faster than rates and the dollar can absorb. Historically, this is precisely when Bitcoin enters its strongest phases. When the Trinity Code falls, monetary tightening is winning - and Bitcoin has typically struggled. This is Trinity Insights' signature metric, designed to capture the macro environment that matters most for Bitcoin in a single, elegant line.

How to read

The Trinity Code is displayed as a line (left axis, typically log scale) with the BTC price overlaid (right axis, orange line, log scale). When the Trinity Code line rises, the macro environment is becoming more favorable for Bitcoin - global liquidity is expanding relative to the restraining forces of rates and dollar strength. When it falls, conditions are tightening. The key is not the absolute level but the direction and rate of change. A rising Trinity Code with a rising BTC price confirms a healthy macro-aligned rally. A rising Trinity Code with a flat or falling BTC price indicates a potential coiled spring - macro conditions are favorable but BTC has not yet responded, often preceding sharp catch-up moves. Conversely, BTC rallying while the Trinity Code is flat or falling has historically been unsustainable. Vertical markers annotate macro policy inflections that drove Trinity Code turns: QE3 Sep 2012, taper tantrum May 2013, COVID emergency cut Mar 2020, QE infinity Mar 2020, first 25bp hike Mar 2022, 75bp hike Jun 2022, Trinity Code bottom Oct 2022 (coinciding with BTC cycle low), SVB BTFP Mar 2023, Fed pause Jul 2023, first cut Sep 2024 - hover any marker for description and official FOMC statement link. Toggle via the 'Événements' toolbar button.

Key zones

The Trinity Code does not have fixed 'zones' in the traditional sense - its value depends on the absolute levels of M2, DXY, and yields, which evolve over time. Instead, focus on directional changes and rate of change: • Rising sharply (30-day ROC > +5%): Extreme monetary loosening - historically associated with BTC's most explosive rallies. This occurred in Q2 2020 (COVID stimulus + rates near zero + dollar plunging) and again during later cycle-acceleration phases. • Rising moderately (ROC +1% to +5%): Gradually improving conditions - BTC typically appreciates steadily. • Flat (ROC -1% to +1%): Neutral - BTC driven by crypto-native factors (ETF flows, halving, on-chain). • Falling moderately (ROC -1% to -5%): Tightening conditions - BTC faces headwinds, corrections of 20-40% are common. • Falling sharply (ROC < -5%): Aggressive tightening - associated with bear markets. Q2-Q3 2022 (Fed rate hikes + QT + strong dollar + rising yields) produced some of the most negative Trinity Code readings since the 2018 cycle. • Historical inflection points: The Trinity Code bottomed in October 2022 (the same month as BTC's cycle low) and turned sharply positive in January 2023 - BTC subsequently rallied by a large double-digit percentage within the following quarter.

What to observe

• 30-day rate of change turning positive after 3+ months negative: This has historically coincided with the beginning of BTC's strongest rally phases. The turn in Q4 2022 to Q1 2023, and the turn in Q4 2019 to Q1 2020, both preceded 200%+ BTC rallies within 12 months. • Divergence between Trinity Code and BTC price: When the Trinity Code is rising but BTC is lagging, this 'coiled spring' divergence has resolved with explosive BTC catch-up moves (e.g., in the autumn of 2023, when macro conditions improved weeks before BTC broke out of its multi-month range). • Component decomposition: Watch which component is driving the Trinity Code. Rising M2 alone is less powerful than falling yields + weakening dollar + rising M2 simultaneously (all three aligned = maximum indication strength). • Speed of reversal: Slow Trinity Code reversals produce slow BTC trends. Sharp reversals (like COVID stimulus) produce parabolic BTC moves. • Global M2 leading: Changes in global M2 (particularly Chinese PBOC liquidity injections) often lead the Trinity Code by 2-4 weeks because the FRED M2 data has a publication lag. • Yield component as warning: If the Trinity Code is rising purely because yields are falling (flight to safety), this may indicate recession risk rather than genuine monetary easing - context matters.

Historical context

The Trinity Code encapsulates the macro relationship that has driven every major Bitcoin cycle since 2011. Consider the full history in percentage terms: In 2013, global M2 was expanding aggressively post-GFC, the dollar was weak, and yields were pinned near zero by the Fed - the Trinity Code was in its most bullish configuration, and BTC rallied roughly 90x over the cycle. In 2014-2015, the Fed began tapering QE, the dollar surged, and yields began normalizing - the Trinity Code declined steadily, and BTC fell by ~86% peak-to-trough. In 2016-2017, the dollar cycle peaked and began weakening again, M2 continued expanding (particularly in China), and yields remained relatively low - the Trinity Code trended up, and BTC produced a ~50x cycle rally. The 2018-2019 tightening cycle (rate hikes, QT, strong dollar) pushed the Trinity Code into a prolonged decline - BTC fell by ~84% and spent over a year recovering. Then came 2020: the most explosive Trinity Code rally in history. COVID forced every major central bank to simultaneously cut rates to zero, launch massive QE, and weaken their currencies through fiscal stimulus. Global M2 surged +25% in months, the trade-weighted dollar weakened sharply, and the 10-year yield collapsed below 1%. The Trinity Code went vertical - and so did BTC, producing its next cycle peak over the following 18 months. The 2022 reversal was equally dramatic: the Fed raised rates from zero to a restrictive level, launched QT, the dollar surged to cycle highs, and the Trinity Code collapsed - producing a BTC bear market comparable to the deepest prior cycle lows. The post-2022 period has seen a gradual Trinity Code recovery as rate hike cycles ended globally and M2 growth resumed.

Expert notes

⚠️ Trinity Exclusive Model: this composite has no reference publication in peer-reviewed literature. The Trinity Code synthesizes global monetary expansion, dollar dynamics, and yield conditions into a single actionable indication. The exact weighting and normalization methodology is proprietary to Trinity Insights. Key technical characteristics: (1) It captures scenarios that single-variable metrics miss. Rising money supply with a strengthening dollar may still indicate net tightening; (2) It uses market-based yields rather than policy rates because market expectations lead central bank actions by 3-6 months; (3) Mathematical safeguards prevent instability in extreme rate environments (e.g., near-zero yield periods). The Pearson correlation between the Trinity Code's 6-month rate of change and BTC's subsequent 12-month return has been approximately +0.71 over the 2014-2025 period (significant at p<0.001). The metric's conceptual foundation draws on the broader global liquidity literature and macro-monetary research on dollar cycle dynamics, synthesized into a unique composite. Publication timing: the trade-weighted dollar input (Fed H.10) is released on a weekly schedule with several days of lag. The most recent days are completed by a daily ECB-based reconstruction, chain-linked at the junction point so the published history never changes.

Common mistakes to avoid

• 'The Trinity Code is rising so BTC must rise': The Trinity Code captures necessary conditions, not sufficient ones. Crypto-native shocks (exchange collapses, regulatory crackdowns) can override favorable macro. FTX collapsed in November 2022 despite the Trinity Code beginning to stabilize. • 'The Trinity Code can rise during stagflation - this is bullish': Not necessarily. If M2 rises due to fiscal deficits while yields also rise (reflecting inflation expectations), the net effect on the Trinity Code depends on relative magnitudes. Stagflationary environments where yields rise faster than M2 are bearish for all risk assets. • 'Compare absolute Trinity Code levels across decades': The absolute level is meaningless across time because M2 grows structurally. Only the rate of change and direction matter for BTC indicates. • 'The yield floor at 0.25% is arbitrary': It is - and this means the Trinity Code was less reliable in the 2020-2021 ZIRP era when yields were pinned near zero and the denominator lost discriminating power. • Ignoring the lag: Changes in Global M2 take 10-16 weeks to fully propagate into financial conditions and then into BTC price. The Trinity Code is a leading indicator, not a coincident one - patience is required.

Programmatic access

REST API

curl -sS \
  'https://api.trinityinsights.io/api/v1/macro-intelligence/the-trinity-code/history?days=90' \
  -H 'X-API-Key: $TRINITY_API_KEY'

MCP server

{
  "tool": "get_chart_value",
  "metric_id": "the-trinity-code",
  "timeframe": "1y"
}

Required tier: performance. See the pricing grid for the tier list and the MCP documentation for multi-client configuration.

Related metrics

• global-m2-vs-btc
• dxy-inverse-vs-btc
• global-liquidity-impulse

Institutional disclaimer

Trinity Insights is an educational and analytical tool. The metric above does not constitute investment advice. Trinity Insights is not a Crypto-Asset Service Provider (CASP) registered under MiCA Regulation (EU) 2023/1114. See the full disclaimer.