Rysk review

Rysk packages options as an income product — you deposit into a covered-call or cash-secured-put style vault and the protocol runs the strategy, instead of you picking strikes and expiries on a CLOB yourself. That framing (Rysk’s own language leans on phrases like “earn upfront income on any asset”) is the entire point of the product, and also exactly why it needs to be understood correctly before depositing: you are the seller of volatility, not a passive yield farmer.

What Rysk actually is

A hybrid AMM/RFQ options protocol built around vault strategies rather than a trader-facing order book. Live on Arbitrum, and expanded onto HyperEVM in 2026 — a deliberate move to sit next to Hyperliquid’s existing user base. The pitch is accessibility: deposit an asset, the vault sells options against it (or otherwise runs a defined strategy), and premium income flows back to depositors, without requiring the depositor to understand implied volatility or manage a position.

The mechanism, in plain terms

A covered-call style strategy sells call options against an asset the vault already holds; a cash-secured-put style strategy sells puts backed by stablecoin collateral. Either way, the vault is the writer — the counterparty that gets paid a premium in exchange for taking on the obligation if the option finishes in the money. That premium is where the “yield” comes from. It is compensation for real risk, not a fee-sharing mechanism or a subsidized reward.

September 2026 update: lower minimum sizes on HyperEVM

Per Rysk’s own public posts, minimum position sizes on HYPE and BTC strategies on HyperEVM were lowered (cited figures circulating: roughly 25 contracts for HYPE, roughly 0.025 for BTC), described as fully collateralized. Those figures remain unverified; confirm current minimums, collateral requirements, and live strategies in the app before depositing.

The income case—and the writer risk

• Pro: genuinely lowers the knowledge bar to participate in options — you don’t need to understand Greeks or manage a book to sell premium through a vault.
• Pro: deployment on HyperEVM is a real distribution advantage, putting the product in front of an already-active, sizable user base rather than starting from zero.
• Con: “income” framing can obscure that depositors are structurally short volatility — a vault can underperform simply holding the underlying asset, or lose value outright, during a sharp move or a volatility spike, regardless of how the product is marketed.
• Con: vault-model TVL is not directly comparable to CLOB-model TVL (see our onchain options guide) — don’t read Rysk’s TVL against Derive’s or Paradex’s as if they measure the same thing.
• Con: Rysk’s audit history, current minimum sizes, and live yield remain unresolved here — check all three directly before depositing.

Who should choose Rysk

Depositors who specifically want to sell option premium for yield and understand the downside (you can underperform the underlying asset, and in a bad move, lose principal), not traders looking for a book to express a directional or volatility view. If you want to actively trade options yourself rather than deposit into a strategy, see our Derive or Paradex reviews instead.

Risks specific to Rysk

Beyond the standard writer-side risk covered in options vs perps — a vault selling options can lose more than the premium collected if the underlying moves sharply against the position — Rysk adds vault-specific risk: contract risk on the strategy logic itself, and the accessibility framing potentially attracting depositors who don’t fully understand they’re taking on short-volatility exposure rather than a fixed yield. Multi-chain deployment (Arbitrum plus HyperEVM) also means verifying bridge and chain-specific trust assumptions separately for each.

What to verify before using Rysk

Rysk’s public product framing and team posts support the existence of the HyperEVM strategy changes, but they do not establish today’s minimum sizes, vault yield, or audit coverage. Read the current vault parameters, collateral rules, and maximum-loss scenario in Rysk’s documentation before depositing; treat any earlier team-post figure as historical until the app confirms it.