Skip to content
The strategy

Deploy your own smart vault.

A leveraged lending loop on Berachain, hedged dollar-for-dollar by a perp short on Hyperliquid. Capital sits in your own vault. Every number on this page is read live from chain.

Connecting…
Capacity

How much capital this strategy can absorb.

The ceiling shifts in real time with five live bounds: Dolomite WBERA borrow availability, oriBGT supply cap, Kodiak exit liquidity, Hyperliquid hedge depth, and the carry-breaks-even economic floor. Capacity is the minimum of all five at every block.

Strategy capacity
How much capital this strategy can absorb.
Partial · some defaults
Deployed
$0.00
Max · live model
$2.33M
0.00% used
Binding constraint · Dolomite · WBERA borrow availability
Why this number moves. Capacity tracks WBERA borrow availability on Dolomite — every $1 of TVL needs $1.50 of WBERA borrow at target leverage. As more WBERA is supplied (more depositors elsewhere on Dolomite) or less is borrowed (other strategies wind down), the ceiling climbs. Live read refreshes every ~60s.
The mechanic

A boosted carry trade with the price taken out.

How it works in 3 steps

every number below is read live from Berachain
modeled (rates fallback)
  1. 01
    Buy Berachain rewards

    Your USDC buys a Berachain reward token (oriBGT) that earns yield while you hold it.

  2. 02
    Borrow to buy more

    Using that token as collateral, the autonomous system borrows BERA on Berachain's lending market and buys more reward tokens — boosting your earnings ~2.5×.

  3. 03
    Net result

    Boosted rewards minus the borrowing cost minus small trading fees = your annual return.

Live ratesfallback snapshot
Berachain reward rate
What the underlying token earns, before any boost
43.1%
Borrowing cost
What the protocol pays to borrow on Berachain's lending market
23.8%
Earnings boost
How much we amplify the base reward
3.03×
Estimated annual return
Boosted rewards minus borrowing cost minus fees
74.8%

This is the math at today's rates. Actual rates move every few seconds, so your return floats with them. If Berachain rewards drop or borrowing gets more expensive, your return shrinks. The opposite too. Your actual earnings show up on the dashboard once you deposit.

The build

One atomic transaction stacks the loop.

Deposit collateral. Borrow against it. Deposit again. Each ring compounds the yield without moving the risk band. The whole stack lands in a single dolomite.operate() call — either every ring settles or none of them do.

How the position is built — one atomic transaction

3 rings · target HF 1.25× · liquidation line at 75% LTV
estimated · HF 1.25×
init
Collateral 1.000
LTV 0.0%
ring 1
Collateral 1.581 · Borrowed 0.581 · this step +0.581
LTV 36.8%
ring 2
Collateral 2.500 · Borrowed 1.500 · this step +0.919
LTV 60.0%
Collateral
2.500
× the USDC you deposited
Borrowed
1.500
× the USDC you deposited
HF at end of build
1.25
liquidation at HF=1.0 (LTV=75%) · target 1.25
3 rings = 1 seed + 2 leverage iterations, all packed into a single dolomite.operate() call. Each leverage ring Withdraws WBERA from the borrow account (creating debt), Deposits it into the main account, Sells it to oriBGT via the WavsTrader → kX route, and Transfers the proceeds back. Solvency is checked once at end-of-operate — no observable mid-state, so no liquidator can race the build-up. Math converges at 2.500× leverage on equity at HF 1.25× (the live rebalance target).
The hedge

A matched short cancels the price.

A quarter of the deposit bridges to Hyperliquid and opens a short sized to the loop dollar-for-dollar. Yield comes from the spread between collateral APR, borrow cost, and perp funding — not from BERA going up.

How the hedge cancels your BERA price exposure

why a leveraged Berachain position can still feel like a stablecoin yield
3× HL · 25% margin
  1. 01
    Split your deposit

    75% opens the leveraged Berachain position; 25% is set aside as Hyperliquid hedge margin.

  2. 02
    Open a matching BERA short

    Hyperliquid runs the 25% margin at 3× leverage. That produces a BERA short notional sized to match your Berachain leg dollar-for-dollar.

  3. 03
    Price moves cancel out

    If BERA price moves, the gain or loss on your Berachain leg is offset by the opposite move on the short. Your equity tracks the carry, not the price.

Bera leg allocation75%
HL margin allocation25%
HL leverage
Net BERA exposure~0
Auto-rebalance band12–40% MR
Funding rate (30d mean)≈ -32% APR (fallback)

The hedge is automated end-to-end: every Hyperliquid watcher tick checks margin ratio, trims if too thin (defender), grows if too fat (recovery). You sign once to open, once to close. Margin doesn't leave Hyperliquid until you withdraw — and when you do, the autoloop bridge brings it back to your Berachain wallet automatically (no gas required from you on HyperEVM).

Loop reactions

It trims itself. It optimizes itself.

Operators check the loop every ten seconds. If safety tightens, the loop trims down. If conditions improve, a layer is added. No human in the path.

Berachain · Loop autopilot

It trims itself. It optimizes itself.

Two reactions, same atomic-operate shape, opposite directions.

Loading…
A.

Liquidation defense

auto-deleverage
Trigger
When the oriBGT/WBERA peg slips and HF drops below 1.18×, the watcher fires within one polling tick.
Action
A single dolomite.operate() sells just enough oriBGT to repay just enough WBERA to land HF at 1.25×. Solvency is checked once, at end-of-operate — no observable mid-state.
Sizing math
s_USD = (HF·d − LT·c) / (HF − LT)
exact closed-form solution · V2.24 atomic-sizing
Stress test
The position absorbs a 16.0% sudden drop in the oriBGT/WBERA peg before the contract's hard floor at HF=1.05× blocks any further worsening — the watcher already starts deleveraging at the 5.6% mark.
Operating limits
Polling10s tick · 60s same-direction cooldown
RoutingkX router · 6 retries · clean revert if no route
PricingDolomite m41 oracle · 5% spot-divergence floor
B.

Yield optimization

auto-lever-up
Trigger
When the position drifts under-leveraged and HF rises above 1.35×, the watcher rebuilds leverage on the next tick.
Action
A single dolomite.operate() borrows just enough WBERA, sells to oriBGT, redeposits — landing HF back at 1.25×. Mirror of the deleverage path.
Sizing math
s_USD = (LT·c − HF·d) / (HF − LT)
mirror solution — same closed-form, opposite sign
Why it matters
Without lever-up, drift to 1.35× would cost roughly 4.8% of annualized yield while the drift sits unaddressed (leverage drops from 2.50× to 2.25×). The lever-up keeps the strategy at its designed leverage point.
Operating limits
Polling10s tick · 60s same-direction cooldown
Sizingborrows just enough to land HF at target — never overshoots
SolvencyDolomite end-of-operate check · no transient under-collateralization
Why one transaction matters. Dolomite checks solvency at the end of operate(). Between actions inside the same call the position can be transiently un-collateralized — but no other contract observes that state, so no liquidator can race the rebalance. Same pattern Dolomite's own Looped-oriBGT product uses; we just wire WAVS-signed envelopes into it.
Hedge reactions

The short resizes. The margin defends itself.

The Hyperliquid leg has its own watchers. They track the loop's size and the hedge's margin ratio independently — same cadence, same atomic shape, opposite venue.

Hyperliquid · Hedge autopilot

The short resizes itself. The margin stays in band.

Three reactions on the Hyperliquid leg keep the hedge sized, funded, and within the margin envelope.

Live thresholds
Margin ratio bands
Defender
< 13%
Top-up
13–22%
Healthy
22–55%
Draw-down
>55%
A.

Short tracks the loop.

auto-resize
Trigger
When the Berachain loop reaches its target leverage (3×) and the HL short delta no longer matches dollar-for-dollar, the resize watcher fires within one polling tick.
Action
A single ModifyOrder envelope signed by WAVS quorum is submitted to Hyperliquid. Notional moves to $loop ÷ 3 at the order book's mid price. Floor + ceiling slippage gates reject the order if the book is too thin to fill at the target size.
Sizing math
notional_HL = loop_USD × delta / 3
3× HL leverage keeps margin-on-margin lift exactly 33%
Why it matches
At 3× on the hedge and 4× on the loop, a 1% move in BERA produces equal-and-opposite PnL on both legs (loop loses $loop×0.04 ÷ 4 = 1% of equity · short earns $loop×0.04 ÷ 3 = 1% of equity). Yield carries through; price drops out.
Operating limits
Cadence5 min poll · 60 s same-direction cooldown
Slippage30 bps order-book mid · reject if book < $200
PricingHL mark · IOC fills only · no resting orders
B.

Margin stays in band.

auto-margin
Trigger
When margin ratio drops below 13% (TOP-UP zone) — typically because BERA rallied against the short — the controller fires a top-up before MR sags into the DEFENDER band.
Action
A BridgeAction signed by WAVS quorum ships USDC from the controller's pool on Arbitrum via CCTP to the HL spot wallet, then routes through to perp margin. Round trip under 15 min; controller treasury keeps a 30-day buffer.
Sizing math
top_up = margin_target − margin_live
target = 30% MR · controller-treasury-paid
Above the band
When margin ratio sits above 55% for a sustained window, the controller withdraws excess back to the Arbitrum pool. The hedge gets back to capital-efficient sizing without ever holding under-deployed USDC on Hyperliquid.
Operating limits
Cadence5 min poll · 30 min cross-chain cooldown
BridgeCircle CCTP · 8–14 min · 0 fees
FloorMR < 10% triggers TRIM (close + redeploy)
Why on Hyperliquid. HL is the deepest BERA-perp book by an order of magnitude, with funding rates that match the carry math autoloop targets. The hedge is opened as a sub-account of a controller multisig — autoloop can adjust size, but cannot withdraw user collateral from HL itself. Custody stays on chain.
The signature

Three operators. Same rules. Quorum signed.

WAVS is the execution layer. Three independent operators run the same deterministic component, sign their answer, and only an action with quorum lands on your vault. No discretion, no override.

Who decides — and signs

WAVS in four lines · the same cycle every reaction uses
quorum-signed
  1. 01Observe

    Independent operators read the same on-chain data at the same trigger block — no operator chooses what the others see.

    Berachain RPC + Origami HTTP API · cron trigger every 10s · block-height pinned

  2. 02Reason

    Each operator runs the same content-addressed WASM module on the same input. Same code + same input → same output, by determinism.

    module digest pinned in service.json + on-chain in the service manager

  3. 03Sign

    Each operator signs the resulting envelope with their own key. The envelope binds the action to its trigger, target HF, deadline, and reason tag.

    ECDSA over secp256k1 (POA middleware) · independent key custody

  4. 04Act

    Once the quorum threshold is met, one transaction lands on-chain. The SubmissionHandler verifies the signatures; the V3 factory dispatches the operate blob to the user's Dolomite sub-account, bounded by the operate-calldata validator + post-state HF floor.

    ecrecover at the SubmissionHandler · operate-calldata validator at the factory · single tx · revertible if any field is tampered with

No single party can move your position. Reactions are deterministic, content-addressed, and quorum-signed — the chain has the last word on every action. That's the property we built on, and it's the property that makes the live mechanics on the rest of this page trustworthy.