Advisory research · Compute · Hedge program design · 29 July 2026

Hedging the GPU balance sheet

A specialty lender to the compute sector — the class of balance sheet advancing against GPU fleets and the rental cash flows they throw off — is short one price twice. The borrower's revenue is the GPU rental rate; the collateral's value is the same rental rate, capitalised. When that price falls, coverage deteriorates exactly as the collateral securing it does. The compute derivatives now listing are, on paper, the fix. But every instrument available forces three design decisions before the first trade: how the hedge settles, what unit it standardises on, and whether the index underneath it can be trusted. This works all three against the live venue landscape, with the power leg — the second-largest driver of borrower economics — grounded in ERCOT and Dominion examples from our settlement data.

Built on the practice's compute corpus: the implied forward curve and IOSCO assessment, the ComputeConnect EFP analysis, the measured GPU power work, and the load-shape study — 401,379 hourly settlements and the NLR measured traces underneath.

59.5%
of the rental price is scarcity premium
the volatile, hedgeable component — hardware amortisation and power are near-deterministic
0
published index methodologies
across all four administrators bearing settlement weight — the data-quality problem is structural
$1.23
per GPU-hour, financial vs physical term
the convenience-yield gap a settlement choice implicitly assigns to one side of the loan
12–21%
nameplate energy overstatement
measured duty factors 0.795–0.880 — the correction that reprices every underwriting model's opex line

01The exposure, before the instruments

A hedge program designed around instruments rather than exposures buys what is listed instead of what is owed. Decompose the book first.

The lender's risk stack. The scarcity premium line is where nearly all the variance lives — measured cost decompositions put hardware amortisation and power at near-deterministic shares, leaving the demand premium (63.7% H100, 52.4% H200, 62.4% B200 of rental price) as the risk.
ExposureWhere it hits the creditHedgeable factorToday's instrument
GPU rental rateBorrower revenue → DSCR covenant; collateral value = the same rate capitalised. The double exposureBenchmark rental index (scarcity factor)Kalshi ladders (live); ICE/OCPI, CME/Silicon Data, AIE/Compute Desk futures (pending)
Residual / resale valueRecovery on default; advance-rate justificationGeneration spread (Hopper vs Blackwell sub-index)None listed — proxy via SKU forward spreads
Power costBorrower opex → margin compression at fixed rental ratesHub/zone power price × measured load shapeNodal hourly futures (Aug 31), ICE TB4, blocks — deep and listed
UtilizationRevenue quantity, not price. Amplifies everything above during rampNot hedgeable; underwrite itCovenants, not contracts
The framing that simplifies everything downstream

A compute loan is a stream of GPU-hours sold forward against collateral marked in GPU-hours. The hedge program is therefore not "protection" bolted onto a credit — it is the synthetic forward sale the borrower's business never executed. Every design choice below should be scored against one question: when the borrower defaults in a falling rental market, does the hedge pay in a form and size that offsets what the collateral just lost? That framing is what makes the settlement question in §02 decisive rather than administrative.

02Decision one — how the hedge settles

Cash, physical, or cash with an EFP option. For a lender the answer is unusually clear once the default state is included in the analysis.

MechanismWhat the lender getsWhere it failsVerdict for a lending book
Cash-settled
index-referenced futures / swaps
Clean mark-to-market offset to index-linked deterioration; no operational capability required; margin-nettable across positions Pays the index, not the borrower's realised rate. The residual is tracking-error basis — real, but measurable and mostly diversifiable across a portfolio of borrowers Core program
Physically delivered
contract converts into capacity
Perfect convergence to deliverable reality; the discipline that forces basis-table publication A lender cannot schedule workloads against delivered racks. Taking delivery converts a financial hedge into an operating business — the exact risk transformation a credit fund exists to avoid Not standalone
Cash + optional EFP
the ComputeConnect pattern
Cash settlement in the ordinary course; the right to exchange futures for physical capacity when holding physical is the position you already have Only one venue pair (Architect × Compute Desk) has built the mechanism; exercising it requires the delivery network's SKU/location basis tables to cover your collateral profile The recovery leg

The default state is what elevates the EFP option from plumbing to program design. On enforcement, the lender becomes an involuntary physical holder: it owns racks it cannot operate, in a market that just fell — which is why it is enforcing. A pure cash hedge pays out and leaves the racks to be liquidated into a broker market at distressed spreads. An EFP-capable position lets the workout desk do what every physical commodity lender does with seized inventory: deliver it against the short futures leg, converting a fire-sale into a priced, scheduled exchange at a published basis. The crude, gold, and gas precedents in our EFP work all generalise: the physical option is worth the most to whoever holds unwanted physical — and a defaulted-on lender is the definition.

The convenience yield is a wrong-way risk in the loan

The financial forward and the physical term market price the same year differently — our curve work measured the gap at $1.23/GPU-hour, 23.6% of spot, against provider reserved-tier sheets. A cash hedge referenced to the financial curve leaves the lender exposed to that spread widening exactly when capacity access gets scarce and credit stress arrives. Sizing the hedge on the financial curve but underwriting recovery on physical-market values double-counts optimism. Use the financial leg for the hedge, the physical leg for the advance rate, and treat the spread between them as a monitored risk line, not noise.

03Decision two — what unit to standardise on

Chip-level contracts are where liquidity will concentrate. Rack-level SKUs are what the collateral actually is. The hierarchy resolves the tension — hedge the benchmark, quote the config as basis.

Borrower fleets are heterogeneous in exactly the dimensions a liquid contract must ignore: SKU (H100/H200/B200/B300), memory configuration, interconnect (PCIe vs SXM vs NVL rack-scale), cooling, and location. A contract specified to rack level matches the collateral but fragments liquidity across dozens of thin instruments — the failure mode our hierarchy work exists to prevent. A chip-level benchmark concentrates flow but leaves config basis unhedged.

The tiered answer, mapped to what exists. This is the CDS-index pattern: liquidity at the benchmark, everything else quoted as spread.
TierUnitLender's useExists today
T1 BenchmarkPer-GPU-hour rental index, capacity-weighted across SKUsThe core short — sized to portfolio-level index exposureOCPI / Silicon Data / Compute Desk publish; futures pending, Kalshi ladders live
T1b Sub-indexGeneration (Blackwell vs Hopper)Residual-value hedge — the generation spread is the depreciation risk on the collateralPublished, not tradable; proxy with SKU forward pairs
T2 NamePer-SKU forwardFleet-weighted overlay where a borrower is concentrated in one SKUCME (SDB200RT etc.) pending
T3 Config basisRack / memory / location differentialsNot hedged — priced. Marked off published basis tables and charged into the spreadCompute Desk publishes by SKU, memory, location — because delivery forces it

Two technical points from the measurement work belong in the standardisation decision. First, rack-scale systems change the energy content of a GPU-hour: measured duty factors run 0.795–0.880 on H100 SXM, and no equivalent public measurement exists for NVL-class racks — so a chip-hour hedge against rack-hour collateral embeds an unmeasured power basis. Second, the generation spread is not a detail: it is the collateral depreciation curve. A lender short the benchmark but long three-year-old Hoppers is long the Hopper–Blackwell spread whether it means to be or not. The two-factor structure from our curve work (scarcity + generation, hedge R² rising from 74.8% to 81.1% when the generation leg is added) is, for a lender, the difference between hedging revenue and hedging recovery.

04Decision three — whether the index can be trusted

Every candidate settlement index has strong design claims and zero published calculations. For a lender, index due diligence is credit due diligence — the hedge is only as good as the print it settles on.

Our IOSCO assessment across the four administrators reduces, for a hedging lender, to one uncomfortable sentence: the index with the best data claim (Ornn OCPI, transactions-only) carries the most settlement weight and has published no methodology, contributor set, or revision policy — and its competitors are no more disclosed. Principles 7, 9, and 11 are not abstractions here; they are the difference between a hedge and an unsecured bet on an administrator's judgment.

A lender's index-validation program. None of this requires the administrator's cooperation — which is the point.
CheckHowTrigger
Tracking errorMonthly: borrower realised $/GPU-hr (from servicing data — the lender's unique asset) vs settlement indexSustained divergence > the priced config basis → re-underwrite the hedge ratio
Cross-index dispersionOCPI vs Silicon Data vs Compute Desk vs Kalshi-implied, same SKU, same tenorDispersion widening without a physical-market driver → methodology divergence, not market
Physical anchorIndex vs provider term sheets and the Kalshi-implied forward (the convenience-yield line from §02)Index detaching from both legs at once → challenge the print
Methodology eventsContractual: methodology-change and cessation-fallback language in ISDA schedules / hedge documentation, per Principles 12–13Any unannounced revision → pre-agreed fallback index, not renegotiation mid-stress
ConcentrationTrack what share of the book settles on one administratorOne-administrator exposure across hedges and borrower revenue references → split venues deliberately
The lender's structural advantage

A specialty lender holds the one dataset no administrator has: audited borrower realised rental rates, monthly, across SKUs, configs, and regions. That servicing tape is an independent check on every published index — and, run properly, it is also the foundation of a contributed-data relationship that could earn fee income and early sight of methodology drift. The validation program above is not overhead; it is a research asset the lending business generates for free.

05The power leg — why ERCOT and Dominion books are different loans

Two identical fleets, one in ERCOT West, one in Northern Virginia, are not the same credit. The settlement data says so with numbers.

Dominion (DOM zone) example. Data-center alley's own zone carries the highest flat-block power price in our eight-location sample — $55.06/MWh over three years, against $32.92 at N. Illinois — and a winter-morning price structure: its most expensive average hour is 7 AM in winter ($118/MWh, p90 $231), not the summer evening. A NoVA borrower's opex line is structurally higher and its stress scenario is a January morning, when inference load (day-heavy, +2.1–5.2% shape premium at DOM) is exactly coincident. Underwrite the power passthrough on flat-block DOM and the model is wrong twice.

ERCOT example. The ERCOT hubs carry the largest shape premiums in the sample — up to +9.4% over flat-block at 40% utilization — and the premium peaks precisely in the ramp phase. For a lender this is not a curiosity: the ramp is the loan's riskiest period. A newly energised borrower is at peak leverage, minimum revenue, and — per the load-shape work — maximum exposure to the gap between the flat-block power hedge its PPA desk bought and the load-weighted price it actually pays. The covenant implication is direct: power-hedge requirements in credit agreements should be specified against the measured shape (or Nodal's hourly strip, listing 31 August), not a 7×24 block, and should tighten during ramp rather than after stabilisation.

The two power exposures, visualized

Three years of hourly DA settlements. Left tab: Dominion’s seasonal structure — the winter-morning spike an annually-averaged hedge never sees. Right tab: ERCOT North summer hour risk — the p90 tail sitting under the compute load shape, at the utilization of your choosing.

Why the two legs belong in one program

The compute heat rate — rental rate over power cost — is the borrower's true margin, and our denominator work shows the energy side of that ratio is misstated by 12–21% when modelled at nameplate. A hedge program that shorts the rental index and ignores the power leg has hedged the numerator of the margin and left the denominator naked — in the two ISOs where the denominator moves most. The instruments for the power side are the mature ones: this is the easy half of the program, and the half most compute lenders skip.

06Three more decisions the program cannot skip

Beyond the principal three — briefly, because each has bitten a commodity lender before.


07The program, assembled

ExposureInstrumentResidual basisTreatment
Rental index (revenue + collateral)Cash-settled benchmark short, split across two administrators; EFP-capable venue for the recovery legBorrower tracking error; convenience-yield spreadMeasured monthly off servicing tape; risk line, priced into spread
Residual value / depreciationGeneration-spread overlay (Hopper vs Blackwell SKU forwards)Config basis (rack, memory, location)Priced off published basis tables, charged, not hedged
Power (ERCOT / DOM books)Hourly strip or shaped block per measured load shape; tightened during rampWithin-hour covariance; PUE driftFloor-not-ceiling convention; covenant-specified
Roll / margin / venueCommitted margin liquidity; administrator-split; documented fallbacksCalendar spreads, methodology eventsSized down, papered in advance

The one-paragraph version. Settle in cash, on a transaction-anchored index, with the EFP option held for the state of the world where the lender owns racks it never wanted. Standardise at the benchmark tier and charge — never hedge — the configuration basis, using the basis tables that physical delivery forced into publication. Trust no index until the servicing tape has audited it, split administrator exposure deliberately, and paper the methodology-change fallbacks before the first trade. And hedge the power leg with the mature instruments that already exist, shaped to the measured load, tightened during the ramp — because that is when the borrower, the shape premium, and the lender's exposure all peak together.