Leveraged Carry — Eye-Popping APR, Honest Kill-Zones
// Lever an HL perp at 40x to capture funding (UNHEDGED, default), or lock the rate via Pendle Boros for ~2x effective leverage. Same kill-zone in both modes — the slider just decides how loud.

The headline number on this strategy can hit triple digits. That's not a typo and it's not a marketing pitch — it's the real annualised funding rate of a Hyperliquid perp multiplied by the leverage you chose. The question this page wants you to answer honestly is: for how long does that number stay real? Funding floats. Price moves. The kill-zone sits about 3.7% away on a BTC short at 20x. The slider that raises the APR is the same slider that tightens that kill-zone. Both directions, every tick.
Two modes share one chassis. Pick based on which risk you're more comfortable owning.
// ⚡ UNHEDGED — DEFAULT, HIGH LEVERAGE, FLOATING
You short (or long) an HL perp on the funding-receiving side. That's it. No Boros. Your capital is the perp's initial margin and nothing else.
- Headline APR = current HL funding × your perp leverage. Live, hourly-changing, gross.
- Effective leverage = the slider value, up to the tier max (40x BTC, 25x ETH, 20x SOL/XRP, 10x HYPE/PAXG).
- Round-trip fee is shown separately as bps; break-even hours tells you how long you have to hold for the funding receipts to recover the open+close cost at today's funding rate.
The headline label on this page exists for a reason: "current funding annualized at Nx — UNSTABLE, not locked, changes hourly." When the funding rate moves, your APR moves with it. The eye-popping ceiling lives here. So does the volatility.
// 🔒 LOCKED — RATE-LOCKED VIA BOROS, ~2X EFFECTIVE
Toggle to locked and you add the Pendle Boros rate-lock leg on top of the same HL perp. Boros's SHORT-YU position pays you a fixed implied APR until maturity (Sep / Dec) and pays floating into the market — that floating cancels the funding you're receiving on the perp side. Net: you've swapped variable funding for a known rate.
The cost of the lock is margin. Boros requires ~47.6% kIM on BTC/ETH/XAU and ~90.9% on SOL/HYPE/XRP. That margin gets added to the perp's initial margin (see below). Effective leverage collapses to roughly 1.9x on BTC — about a tenth of the unhedged ceiling — but the rate stops fluctuating.
- Headline APR =
implied × effective_leverage − cost_drag. Locked. Realised by holding through maturity. - Cost drag is itemised: Boros settle fee + amortised perp open/close + the spot/perp basis cost.
- The Boros leg has its own liquidation rule, but we're not displaying a number yet — the gating math (TimeFloor / RateFloor) is still under verification. You'll see "boros rate-move liquidation: modeling pending" until that lands.
// THE TWO KILL-ZONES
Both modes carry directional perp risk. This is not delta-neutral. The page surfaces two independent triggers, the second of which only fires in locked mode:
- Perp price liquidation (always). The HL position liquidates when price moves against you by your isolated-margin buffer — about 3.7% on a 20x BTC short. This is the headline kill-zone. It sits next to the APR at every tier, in the same size class, by design: the louder the APR, the louder the kill-zone reads beside it.
- Boros rate-move liquidation (locked only, modeling pending). When (and if) we surface a number here, it will be the size of the rate move that drains the Boros leg's maintenance buffer. Independent of price. Today the page shows the USD cushion only.
First-to-trigger ends the strategy. Either trigger by itself wipes the position; you don't get to ride one out by relying on the other. The page flags whichever distance is tightest.
// THE ADDITIVE-MARGIN GOTCHA
This is the one that catches people. In locked mode the capital required is additive, not cross-margined:
capital = boros_IM + perp_IM
You can't net the Boros margin against the HL margin — they live on different chains and different platforms. If the perp eats its isolated margin and gets liquidated, the Boros position keeps running with its own margin until its trigger fires (or you close it manually). And vice versa. Each leg has its own bankruptcy.
That's why the "capital required" on the page jumps from $500 to about $5,260 when you toggle from unhedged to locked at $10k notional. Same exposure, vastly more capital posted. Effective leverage divides by the sum.
Also note: isolated mode is assumed throughout. If your HL account is in cross-margin, your perp here pools with everything else on the account, which is out of scope for this page's math. Switch isolated before mirroring any of these numbers.
// REAL BUT UNSTABLE
Every number on this page is computed from live data — HL funding, HL mark, Boros markets, the Coingecko + gold-api spot feeds. Nothing is fabricated, nothing is averaged across a window the page hides. But "real" doesn't mean "stable." In unhedged mode the funding rate that built the headline can halve in an hour. In locked mode the headline is steadier, but the perp liq-distance is the same 3.7% it ever was — it doesn't care that the rate is locked.
The colour rule on the headline tracks magnitude honestly:
- < 0% APR → rust, loss
- 0–20% → sage, modest
- 20–50% → sage with glow, eye-catching
- 50–100% → amber phosphor with glow
- > 100% → amber, max glow, biggest type — earned by an honest-to-the-math reading of live funding × your slider
If you see triple digits on this page, that's funding actually running that hot right now. Treat it like the kill-zone sitting next to it: real, loud, temporary.
// WHAT THE FORGE DOES NOT DO
This is a read-only surface. The Forge never signs. The math points at HL (always) and Boros (locked mode) via the buttons at the bottom of the page; you take the trade yourself or you don't. There is no built-in execution path because there is no built-in trust-me — you'd be wiring keys to a wasteland operator and that is not the bargain.
Cross-link from the Boros Carry card brings you here pre-loaded with that underlying's symbol. The slider remembers nothing across sessions. The kill-zone never goes away.
Once the trade is on, it belongs on a board that reads it the same honest way — real, tagged, read-only.
Track the position on one board — scanned legs the Forge confirmed, logged legs you typed, and a headline that never blurs the two.

