One reading, one line, no adjuster.
A policy here is a mandate the contract carries out by itself. It buys a storm reading from whichever miner the network ranks best, and pays the claim the moment the reading crosses the red band. Nobody approves it. Nobody can decline it out of turn.
-
0.0calmSea like a mirror. Nothing here is owed.
-
0.1light airWind 6 km/h, gusts 9, rain 3 mm/h or seas 0.4 m.
-
0.2light breezeWind 12 km/h, gusts 18, rain 6 mm/h or seas 0.8 m.
-
0.3gentleWind 19 km/h, gusts 27, rain 9 mm/h or seas 1.2 m.
-
0.4moderateWind 25 km/h, gusts 36, rain 12 mm/h or seas 1.6 m. Whitecaps.
-
0.5freshWind 31 km/h, gusts 45, rain 15 mm/h or seas 2.0 m.
-
0.6strongWind 37 km/h, gusts 54, rain 18 mm/h or seas 2.4 m. A tropical storm within 200 km.
-
0.7near galeWind 43 km/h, gusts 63, rain 21 mm/h or seas 2.8 m. Elevated: worth covering.
-
0.75the cover paysWind 46 km/h, gusts 68, rain 22 mm/h or seas 3 m. At or above this band the contract pays the holder in the same transaction.
-
0.9strong galeWind 56 km/h, gusts 81, rain 27 mm/h or seas 3.6 m.
-
1.0stormWind 62 km/h, gusts 90, rain 30 mm/h, seas 4 m, or a typhoon overhead. Typhoon Rai read 1.000 at Cebu.
Lanes, read now
worst hour on each lane, screened through TelegraphAsk the plate about a place
The same call the contract makes before it spends anything. Name a place, give a coordinate pair, or ask in a sentence. No wallet, no sign-up. The reading comes back signed.
Cargo meets the weather where it is, not where it left.
Each leg is forecast for the hour the shipment reaches it, so the time axis moves with the cargo. The verdict is the worst hour on the way, because that is the one it has to survive.
Would it have paid?
The same thresholds, run over what actually happened. Rai, Odette in the Philippines, crossed the Visayas on 16 December 2021. These are the board's ports on those four days, hour by hour, from the reanalysis archive: the cover pays where the storm went and stays quiet where it did not.
| Port | Peak risk | Peak gust | Peak hour (UTC) | Hours over 0.75 | Outcome |
|---|---|---|---|---|---|
| reading the archive… | |||||
Cebu, hour by hour
15 Dec 00:00 UTC/api/backtest?lat=10.32&lon=123.89&start=2021-12-15&end=2021-12-18
archive: Open-Meteo ERA5
Four steps, and a person appears in none of them.
The contract is the customer of the intelligence, not a screen someone reads it on.
-
contract
Opens a job
It calls
createJobagainstSTORM_ALERT, the intent, not a miner. Which miner answers is the protocol's decision, and it goes to whoever currently ranks best. -
network
Answers and is checked
A miner returns a reading. Validators score it against ground truth and finalise it before anything is paid.
-
protocol
Delivers it back
The result arrives at the contract through
subnetMessage, packed the way that miner declares its fields. The contract reads defensively and declines a payload it cannot interpret rather than guessing at a payout. -
contract
Pays, or does not
Risk at or above 0.75 pays the holder in the same transaction. Below it, the policy closes as declined. If no answer ever comes, the reserve is released after 24 hours; that rail has been run, and the transactions are in the ledger below.
What it has settled
Every row is on chain and none of it is a screenshot. Follow the job id and read it yourself.
| Policy | Point | Cover | Job | Risk read | Outcome |
|---|---|---|---|---|---|
| reading the chain… | |||||
What the network scores
A scoring module decides what a miner's answer is worth, one per intent. These are the ones in force, read from the node: the bar a challenger must clear, the score the board displays for it, and what the best miner on that intent actually scored.
| Intent | Bar | Shown | Best miner | Tries |
|---|---|---|---|---|
| reading the node… | ||||