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.
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.
A boosted carry trade with the price taken out.
How it works in 3 steps
- 01Buy Berachain rewards
Your USDC buys a Berachain reward token (oriBGT) that earns yield while you hold it.
- 02Borrow 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×.
- 03Net result
Boosted rewards minus the borrowing cost minus small trading fees = your annual return.
- Berachain reward rate
- What the underlying token earns, before any boost
- Borrowing cost
- What the protocol pays to borrow on Berachain's lending market
- Earnings boost
- How much we amplify the base reward
- Estimated annual return
- Boosted rewards minus borrowing cost minus fees
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.
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
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
- 01Split your deposit
75% opens the leveraged Berachain position; 25% is set aside as Hyperliquid hedge margin.
- 02Open 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.
- 03Price 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 allocation | 75% |
| HL margin allocation | 25% |
| HL leverage | 3× |
| Net BERA exposure | ~0 |
| Auto-rebalance band | 12–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).
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.
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.
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
- 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
- 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
- 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
- 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