How Does Etherisc Work?

Parametric insurance: smart contracts automatically pay claims when predefined oracle-verified conditions trigger (flight delays, weather events, protocol exploits)

Parametric insurance removes subjective claim assessment by triggering payouts on objective data (oracle-confirmed events). Etherisc pioneered blockchain parametric insurance with $13M in flight delay insurance processed. Eliminates claims disputes but introduces oracle manipulation risk. 47% YoY growth in 2026 demonstrates market demand.

Chainlink oracle integration: decentralized oracle network provides flight status, weather data, and other parametric trigger data

Etherisc uses Chainlink's decentralized oracle network to access reliable external data (flight APIs, weather stations). Multiple data providers and node operators reduce single point of failure. However, Chainlink itself becomes critical infrastructure dependency—if Chainlink fails, all Etherisc policies become inoperable.

Insurance capital pools: liquidity providers deposit capital to back policy coverage in exchange for premium revenue

Standard insurance pool model where capital providers act as insurers. LPs earn premiums from policy purchases but bear claim payout risk. Similar to Nexus Mutual's staking pools. LPs must assess actuarial risk of covered events to avoid adverse selection.

Custom DAO insurance policies: bespoke parametric policies designed for DAOs and protocols covering unusual risks not fitting standard templates

Etherisc's $80M TVL includes custom policies for DAOs covering protocol-specific risks (governance attacks, smart contract bugs, oracle failures). Represents expansion beyond commodity risks (flight delays) into tailored coverage. Novelty lies in creating actuarially unproven insurance products for crypto-native risks.

Automated claim processing: smart contracts release payouts immediately upon oracle confirmation of trigger conditions

Deterministic claim payouts are a key value proposition—no human claim adjuster delays or disputes. Once oracle confirms trigger (e.g., flight delayed 2+ hours), payout executes automatically. Eliminates traditional insurance friction but removes fraud detection layer.

DIP token governance: token-weighted voting over protocol parameters, capital pool risk parameters, and oracle selections

Standard governance token model (assumed; may not exist). Governance likely controls which oracle providers are trusted, which policies can be created, and how capital pools operate. Critical for maintaining protocol security and actuarial soundness.

Etherisc's automated payouts occur immediately upon oracle trigger without human review. If Chainlink oracles are manipulated (compromised nodes, bad data providers, API failures), false claim triggers drain insurance pools before the manipulation is detected. The automation that creates UX benefit becomes an attack vector.

Parametric insurance only pays when specific trigger conditions are met (e.g., 'flight delayed 2+ hours'), but policyholders may suffer actual losses without triggering payout (e.g., 1h59m delay causing missed connection). This basis risk creates user dissatisfaction and potential regulatory classification as 'incomplete coverage,' undermining insurance product credibility.

Custom policies for novel crypto risks (DAO governance attacks, oracle failures) lack historical data for actuarial pricing. Capital providers may underprice risk due to insufficient precedent, leading to losses when claims exceed premiums. This adverse selection can make insurance pools insolvent.

Parametric triggers can fire simultaneously for many policies during correlated events (major weather event affecting multiple policies, flight system-wide outage). If insurance pools are under-reserved for tail events, mass simultaneous claims drain reserves causing payout failures for later claimants.

While Chainlink provides decentralized oracle infrastructure, underlying data may come from limited sources (e.g., one flight tracking API, one weather station network). If that data source fails or is compromised, all Chainlink nodes will propagate bad data, causing systemic failure. Decentralized infrastructure doesn't protect against centralized data sources.