How it works
Zyura pays a fixed amount if a named flight is late or cancelled by a stated measure. It does not cover anything else.
Buying protection
Enter your flight, choose a plan, and read the exact terms. You approve one payment in your wallet. In a single transaction the premium moves, the full payout is set aside, and your policy is recorded. If any part fails, nothing happens and nothing is charged.
What decides a payout
The contract compares the reported arrival with the scheduled arrival in your policy. Arriving at least the covered delay late qualifies, and exactly on the threshold counts. So does a cancellation after you bought. A late departure alone does not pay. Nobody reviews a claim.
The plans
Food Cover costs 3.69 USDT and pays a fixed 30 USDT if the flight arrives two hours late or more, or is cancelled. Overnight Cover, for evening arrivals, costs 7.99 USDT and pays a fixed 50 USDT if the flight arrives after midnight at the destination and at least four hours late, or is cancelled. Amounts are test USDT with no monetary value. Every sale needs the pool to reserve the full payout, so a plan can show as unavailable until more liquidity arrives. Read the full terms.
After your flight
You do not file a claim, but the payout is not fully automatic yet. A Zyura-operated key reports the flight result by hand, and it stays open to dispute for a short window. Then anyone can send the settlement, including you from My Protection, and the money can only go to the policyholder wallet. Zyura does not run an always-on monitoring service today.
If there is no flight result
Missing data is never treated as on time. If no result arrives by your policy's deadline, you can take your premium back without needing anyone's permission. That protects your premium but not the payout, so a flight that would have qualified gets only the premium back during a reporting outage.
What you are trusting
- The flight data source to report correctly. Fetching data does not make it true.
- A Zyura-operated key to deliver results. A Chainlink CRE workflow runs in simulation to prepare them, but on this network the contract checks Zyura's key, not a verified Chainlink signature. A guardian can dispute a result for a short window, which leads to refunds.
- The USDT token's owner, who can freeze or destroy any address's balance, including the pool's.
- Whitechain's single sequencer to include transactions. There is a slower route through Ethereum if it refuses.
If this website disappears
Your policy lives on the chain, so any copy of this app, or a direct contract call, can read it and act on it. Settling a final result and taking a timeout refund need no Zyura service. New sales and new flight results do.
What is public
Your wallet address, the flight, the amounts and the result are visible to anyone, permanently. Zyura never asks for your name or passport, and cannot read a real reservation. Demo booking references are synthetic and stay in your browser, and this app has no analytics or trackers. Whoever runs your network connection can see which addresses you look up. You can change it in the page footer.
Real flight data you can inspect
The historical replay runs real US flight records through Zyura's rules, and no policy existed on those flights. Live aircraft shows open ADS-B positions, which are not outcomes and never trigger a payout. Demo flights are fictional, and any result on one is scripted.
What this is not
This is an unaudited testnet product using test tokens with no monetary value. It is not licensed insurance, and prices are illustrative rather than actuarially derived.