The interface is not the source of truth.
Every meaningful value in a Hedgix policy is fetched and verified by the contract itself. This page names each responsibility explicitly.
Trust model
The frontend is a display and interaction layer. RainbowKit connects an injected browser wallet; WalletConnect and QR pairing are intentionally not included.
GenLayerJS transactions
GenLayerJS submits Intelligent Contract reads and writes, then monitors GenLayer transaction status. A transaction hash alone is not treated as success.
Registry verification
The contract fetches the registry and verifies metadata, version, protected asset, protection type, event level, duration, premium, payout, Binance symbol, and trigger rule for every purchase.
Market data verification
Binance is the only market-data provider. The contract verifies ticker symbols during purchase and candle open time, close time, selected price field, and validator agreement during settlement.
Settlement verification
Each closed 1-day candle low is compared against the stored trigger. Policy transitions between ACTIVE, TRIGGERED, PAID, EXPIRED, and CANCELLED are stored on-chain.
Pool accounting
The pool tracks reserved liability for every active protection. Withdrawable balance is only what remains after reservations.
User ownership
Every policy is wallet-scoped. Only the owning wallet can claim payouts or cancel where allowed.
MVP limitations
This MVP still has trust assumptions: the versioned registry is hosted externally, Binance is centralized market data, the underwriting pool must remain funded, and settlement requires a transaction.
Policy evidence
Hedgix shows only verified records. Transaction hashes are omitted unless a specific purchase, settlement, trigger, or claim record has been confirmed.
Verified resources
Review the deployed contract, official product registry, and source code used by Hedgix. Transaction hashes are shown only after specific records are verified.