← All posts
·GADUIN Researchblockchain flight insuranceaxa fizzyparametric insuranceflight delay event contractsmart contract flight insuranceetherisc

After AXA Fizzy: What's Next for Blockchain Flight Coverage

AXA Fizzy proved blockchain flight delay automation worked, then shut down. Why it failed, who took over, and how event contracts differ.

Last updated

When AXA launched Fizzy in September 2017, the idea was simple and new: buy blockchain-based parametric cover for your flight, and if the plane landed more than two hours late, a smart contract paid you automatically. There were no forms, no adjuster and no waiting on hold. The code moved the money.

By late 2019, Fizzy was gone.

What ended it, and what came after, matters today. The market for blockchain-based transport delay coverage didn’t disappear with Fizzy. It split into two paths. One kept the licensed parametric structure and tried to work around its limits. The other dropped the insurance model and tackled the same problem with event contract markets. The two paths serve different people, work differently and are heading in different directions.

What Was AXA Fizzy? A Brief History (2017–2019)

AXA Fizzy was one of the first live consumer products built on Ethereum. A passenger bought cover for a specific flight through a website. The smart contract checked a flight data feed. If the aircraft arrived more than two hours late at its destination, the contract paid the buyer directly, with no person involved in deciding the claim.

That was new. Traditional travel protection made the policyholder file documents after the event, wait for a review and, if there was a dispute, go through a formal process. Fizzy removed the adjuster for qualifying delays. Anyone could check the smart contract code on Ethereum, and the purchase flow was built for mobile.

AXA offered Fizzy only in France. It was discontinued in 2019, with AXA citing too little demand. The Ethereum contract, the data feeds and the distribution setup were all shut down.

The technology worked. The business didn’t.

Why Did Fizzy Fail? Three Root Causes

Post-mortems on Fizzy usually blame “low demand,” which is accurate but doesn’t explain much. Three factors explain why demand couldn’t build, whatever the interface or the price.

Distribution without reach. Fizzy was sold only through its own website, with no link to airline booking flows, online travel agencies or travel management platforms. The people most exposed to delays, travellers booking flights, only found Fizzy if they went looking for it. A new kind of product has to reach people where they make the decision. Fizzy was several clicks away from that point.

Regulatory perimeter. However automated its settlement, a parametric product is still a licensed financial product under insurance regulation. Fizzy ran under AXA’s French license. Expanding to Germany, the UK, Italy or the US would have meant a separate licensing process in each country, and sometimes separate capital requirements. One Ethereum contract couldn’t hold regulatory approval for several markets at once. The size of the market was capped from the start.

Settlement speed versus the promise. Fizzy’s marketing stressed automatic, blockchain-native payouts. In practice, settlement could take much longer than the near-instant payment the marketing suggested, because of blockchain finality, data feed processing and back-end reconciliation. For a product sold on “the money moves instantly,” that gap undercut the whole pitch.

None of these was an engineering failure. The smart contract did what it was designed to do. Fizzy failed because it was a licensed product in one country, sold through its own channel, with payout times that didn’t match its own marketing.

Who Picked Up the Torch: Etherisc and Others

Parametric flight delay cover continued after Fizzy closed. Several projects moved in, each with different design choices.

Etherisc FlightDelay is the most direct successor. According to Etherisc’s own product announcement, the protocol runs on Gnosis Chain (formerly xDai), uses third-party oracles for flight data, settles in USDC and sets its delay trigger at 45 minutes, much lower than Fizzy’s two hours. The code is open source and has been used for several product lines in various markets. Etherisc works as a decentralized insurance protocol rather than a traditional company.

Several operators have approached transport delay cover from the cargo and logistics side, building parametric structures for freight delays and port disruption. These products target operators managing revenue at risk on shipments, rather than individual travellers.

Enterprise integrations are a third direction. Enterprise distributed ledger platforms and established data providers have built compliant parametric frameworks for institutional buyers such as corporate travel programs, cargo operators and fleet managers, on permissioned infrastructure instead of public chains.

Each approach fixed some of Fizzy’s problems. None fixed all of them, because the core constraint isn’t technical.

The Fundamental Problem That Parametric Insurance Cannot Escape

Etherisc and similar projects work within the same limits that closed Fizzy. The blockchain infrastructure is faster and more flexible, and the product design is more sophisticated, but the regulatory constraints are the same.

Licensing is a regulatory problem. Parametric products covering consumer risk are regulated in every major jurisdiction. Each new market means another licensing process, with regulatory review, proof of capital adequacy and product approval. That’s why on-chain parametric cover is still unavailable to US persons and sold in a limited number of markets elsewhere. A better oracle doesn’t change that.

Counterparty risk remains. Even with full smart contract automation, a parametric product has a counterparty: the entity that issued the cover, holds the reserve capital and owes the payout. That entity’s solvency, regulatory standing and continued operation matter. Anyone holding a parametric product from a licensed issuer depends on that issuer’s operational and financial health.

There is still a process. In parametric products, “automatic” means a data value triggers the payout instead of a human adjuster. Process still exists. Oracle disputes, edge cases in how a delay is classified, data feed timing and product terms can all cause friction. In practice, settlement takes anywhere from hours to several days, depending on the protocol and its oracles.

Asset denomination. Most on-chain parametric products settle in USDC or a similar stablecoin. For anyone whose positions or risk management are in USDT, that adds a currency mismatch.

These limits come with the licensed parametric structure itself. They set a ceiling on what it can do, and that leaves a gap.

Event Contracts: A Different Approach to the Same Problem

The gap Fizzy left has been approached from a different direction: the event contract market.

An event contract on a flight delay isn’t a parametric cover product. Nobody underwrites it. There’s no policy, no cover note and nothing to claim. It’s a market on one question with three possible answers, fixed before trading opens: will this flight arrive on time, be delayed or be cancelled?

On platforms like GADUIN, you take a position on one of those three outcomes. A flight market settles on the destination airport operator’s published arrival time against its published schedule. If the flight arrives past the market’s delay threshold, it settles Delayed. Within the threshold, it settles On time. A flight that never operated settles Cancelled, which is a separate outcome from a long delay. Shares of the outcome that happened pay $1.00 each in USDT. Settlement runs automatically against terms fixed when the market opened, so there’s no form, no adjuster and nothing to file.

There’s also no issuer whose balance sheet you depend on. Each of the three outcomes has a live price showing the chance the market gives it, and the market has one settlement rule, fixed before the first trade and unchangeable afterwards. A share pays $1.00 if its outcome happens and $0 if it doesn’t.

If you’ve read parametric insurance vs prediction markets, this distinction is familiar. It matters especially for flight delays: event contracts on transport delays are open to institutional participants (airlines hedging revenue lost to schedule disruption, corporate travel programs managing total delay exposure, logistics operators protecting cargo transit windows) without going through the insurance licensing that keeps parametric cover out of most markets.

GADUIN vs. Parametric Insurance: Key Differences

The same flight delay can be the reference event for either model. Everything around it differs.

DimensionParametric coverage productEvent contract (GADUIN)
What you holdA policy issued to youA share that pays $1.00 if its outcome happens, $0 if it does not
What decides itA parameter threshold read by the issuer’s oracleThe destination airport operator’s published arrival time against its published schedule
Settlement assetUSDC / fiatUSDT
Settlement speedHours to daysAutomatic, once the arrival record is published
Process requiredAutomatic trigger, no adjusterNo claim, no form, no adjuster
Regulatory modelLicensed product, jurisdiction-specificEvent contract market
AudienceRetail policyholdersInstitutional hedgers, active traders
Geographic availabilityJurisdiction-limitedCrypto-native, not available to U.S. persons

Which model fits depends on the use case and the participant. A traveller buying cover for one upcoming flight needs something different from a corporate travel manager with ongoing exposure across thousands of departures a year, or a cargo operator hedging a quarter’s shipping schedule.

The comparison in missed connection insurance vs event contracts applies here too. Event contract markets don’t compete with regulated parametric products for the same customers. They serve institutional, crypto-native and large-volume participants, a segment the licensed parametric model can’t reach.

What This Means for the Future of Flight Delay Coverage

Fizzy’s closure made something clear: the hard part of blockchain-based flight delay cover was never purely technical. Fizzy showed a smart contract could replace an adjuster. What it couldn’t show was that the licensed parametric structure was the right way to do that at scale.

The market’s answer so far depends on who the product is for.

The regulated parametric track will keep developing. Etherisc and similar protocols show that smart contract automation works inside licensed frameworks. As fintech regulation develops, especially in the EU, where passporting and fintech licensing frameworks are maturing, retail parametric products will become available in more markets. The technology works. The regulatory path is slow, but it’s open.

The event contract track runs alongside it. It serves a different group: institutional participants, corporate risk desks and experienced traders who work in crypto and want USDT-settled positions on transport delays. Prediction and event contract markets have grown large: combined monthly volume across major prediction-market venues (Kalshi and Polymarket) reached roughly $24 billion by April 2026, per Pew Research, with thousands of active event markets settling efficiently at scale. Applying the same mechanics to transport delays serves a use case few products cover.

Blockchain-based flight delay cover now runs as two separate market structures for different participants. AXA Fizzy raised the question in 2017, and both tracks are still answering it.


This article is for informational and educational purposes only and does not constitute financial advice. Trading event contracts involves risk of loss. GADUIN markets are not available to U.S. persons. See the User Agreement and Terms of Service for full terms.

Look up flight status by flight number. The methodology explains scheduled, estimated and actual times.