Opertus

Overview

Trade perpetuals from a private balance against a vault that hedges on HyperCore.

Opertus perpetuals let a shielded balance hold a leveraged position on HyperEVM. Each market is one OpertusPerpVault. Users trade against the vault, not an order book: a request fills at Hyperliquid's mark price plus or minus a spread, one or two blocks later. Separately, anyone can call hedge(), which sends immediate-or-cancel (IOC) orders so the vault's HyperCore position tracks users' net position. HyperCore is never on a user's critical path.

Experimental protocol

The perpetual vault is experimental. It has not been audited, and there is no production deployment. Do not use it to secure real funds.

What users get

PropertyHow
A fill at their price or betterEvery fill is within the request's acceptablePrice, or the request is refunded
Fast fillsA request executes in the next block or the one after
No failed-order costsA request that cannot fill is cancelled with a full refund and no fee
Unlimited concurrent ordersFills are internal to the vault, so they never wait for one another
An isolated positionEach position has its own margin, and no other user's action can change it

The protocol keeps almost no directional risk. Its only unhedged exposure is the short lag between a fill and the hedge, capped by maxUnhedgedUsdc.

Design rules

  • IOC only. Every HyperCore order the vault sends is immediate-or-cancel. Nothing rests on the book, so nothing has to be tracked or cancelled. A missed fill is simply a remaining gap that the next hedge() retries.
  • Isolated only. Each clone holds exactly one position with its own margin. There is no cross-margin. A clone opens once, so positions never merge.
  • No callbacks. Payouts and refunds are credited to claimable. The vault never calls into a clone; the clone collects with claim().
  • Few inputs. A user chooses size, collateral, and a worst acceptable price. The protocol tunes 12 economic parameters within hard bounds. Everything else is a constant.
  • Leverage ceiling. Each vault is deployed with an immutable LEVERAGE_CEILING, at most HyperCore's own maximum for the asset. No parameter change can raise leverage above it.

Actors

ActorRole
CloneA single-use Opertus clone holding one user's position, funded by unshielding a note
ExecutorAnyone. Executes pending requests at a later block's mark
HedgerAnyone. Calls hedge() and the HyperCore margin functions
LiquidatorAnyone. Calls liquidate(clone) and earns a reward
ProtocolA multisig. Pauses opens and proposes parameters and insurance withdrawals, each behind a one-day delay

Every call except the protocol's admin calls is permissionless, so the vault keeps working if the protocol's own bot stops.

Explore

On this page