A parametric insurance policy pays out automatically when flight AA42 is delayed more than two hours. The question is purely factual — there is no interpretation, only data.
Pose a question. Pick a mode. Watch five validators deliberate. See the Equivalence Principle deliver a verdict. Disagreement triggers appeal.
"AA42 was scheduled to land at 14:00. The flight tracker shows it landed at 16:47. Did it land more than 2 hours late?"
Awaiting summons.
Awaiting summons.
Awaiting summons.
Awaiting summons.
Awaiting summons.
A parametric insurance policy pays out automatically when flight AA42 is delayed more than two hours. The question is purely factual — there is no interpretation, only data.
Strict because the answer is a number. Every validator should fetch the same public flight tracker and return the same delay in minutes. Any output difference is a data error, not a legitimate interpretation gap.
Ethereum cannot reach out to flight tracker APIs. A Chainlink oracle could fetch the data, but it introduces a single point of trust. GenLayer validators each query the live web independently — unanimity among them is the proof.