Documentation

Hedgix, documented.

Everything you need to understand what Hedgix does — and, just as importantly, what it doesn't.

Overview

Hedgix is a crypto market protection protocol built on GenLayer. It offers defined coverage products against price drops and stablecoin depeg events, with verified market data and transparent on-chain settlement.

Products

Two products are available: Price Drop Protection for BTCUSDT, ETHUSDT, SOLUSDT, and BNBUSDT; and Stablecoin Depeg Protection for USDT and USDC, measured directly against USD through USDTUSD and USDCUSD.

Supported markets

See the Markets page for a full breakdown per asset, level, and duration.

Purchase guide

Connect a wallet, choose a product, pick asset / event level / duration, review the summary, and submit. The contract verifies registry terms, checks the premium, and fetches the Binance live ticker during transaction execution.

Coverage timing

Coverage starts on the next UTC day and lasts 7, 14, or 30 days. Aligning to UTC days ensures every observed candle is fully closed.

Locked reference price

The locked reference price is fetched from Binance during purchase and stored in the policy record. For price-drop products it anchors the calculated trigger price. For depeg products it confirms the asset was above the absolute USD threshold when purchased.

Trigger calculation

For price drops, trigger = reference × (1 − pct). For depeg, the threshold is a stored absolute USD value such as 0.998, 0.996, or 0.994.

Settlement process

Each settlement transaction checks the exact next expected UTC date. Open daily candles cannot be settled. The contract fetches the closed Binance daily low and compares it against the stored trigger.

Claim process

The policyholder of a Triggered protection can submit a claim transaction to receive the reserved payout from the pool. Once claimed, status becomes Paid.

Cancellation

ACTIVE policies can be cancelled by the policyholder. Cancellation releases the reserved liability but does not imply an automatic premium refund.

Policy statuses

ACTIVE, TRIGGERED, PAID, EXPIRED, CANCELLED. All transitions are stored on-chain.

Pool accounting

The pool holds premiums, reserves maximum payouts against active policies, and lets the operator withdraw only what is not reserved.

Registry

The registry lists every supported product term. The contract independently verifies the selected product, asset, event level, duration, premium, payout, trigger rule, and Binance symbol. Existing policy records preserve the terms stored at purchase.

GenLayer validation

GenLayer validators reach consensus on nondeterministic fetches (registry, Binance data), producing deterministic on-chain values.

Wallet ownership

Policies are wallet-scoped. Only the owning wallet can claim or cancel.

Error states

Common errors include insufficient premium, unsupported term, mismatched registry version, insufficient pool capacity, settlement not yet ready, open daily candle, and already-claimed payout.

Risks and limitations

MVP uses Binance as the only market data source, an externally hosted versioned registry, and transaction-submitted settlement. See the Transparency page for trust assumptions.

Frequently asked questions

  • Is this a stop-loss? No. It is a defined-payout protection product settled from a reserved pool.
  • Does the frontend influence outcome? No. Only registry + Binance data + the contract determine settlement.
  • Are payouts automatic? No. A Triggered policyholder submits a claim transaction to receive the reserved payout.
  • Can I be liquidated? No. There is no leverage and no collateral requirement.