Short answer
The index is measured continuously at the source (sensor, station, satellite), sealed at a 15-minute cadence and anchored on Hedera. The threshold crossing is documented by verifiable proof, independent of insurer and insured.
Did my weather index really cross the declared threshold, and who proves it?
The index is measured continuously at the source (sensor, station, satellite), sealed at a 15-minute cadence and anchored on Hedera. The threshold crossing is documented by verifiable proof, independent of insurer and insured.
Who can verify the index value without relying on my insurer?
Any third party holding the hash: the insured, an expert, an arbitrator. The value is eIDAS-timestamped and anchored, verifiable by recomputing the hash, with no account.
How do I avoid disputes over the trigger data of a parametric insurance?
By anchoring the data at the source at emission time: the trigger rests on a sealed, dated measurement, identical for both parties. The dispute disappears when the reference data is no longer contestable.
Can I automate payment as soon as the index reaches the threshold?
Yes. The sealed proof of threshold crossing can feed an automatic payment oracle. 0DATA provides the technical evidence element; the contractual trigger belongs to the insurance contract.
What reference data do you use for the index (Météo-France, satellite)?
The data is captured at the contractually agreed source (ground sensor, station, satellite). 0DATA seals and anchors it as emitted, without modifying it — the reference source stays the one defined in the contract.
Is the index measurement timestamped and verifiable by an independent third party?
Yes. eIDAS timestamping (RFC 3161) and Hedera anchoring: the anteriority and integrity of the index are verifiable independently of both parties.