When the trigger is disputed, both sides need to recompute.
A parametric catastrophe bond settles on a single data reading: did the wind at the covered location cross the line, or did it not? When a sponsor and the note-holders disagree, the argument is really about what the named source read at the moment that mattered. This page issues a signed, independently re-computable Trigger Receipt for a cyclone-relevant wind threshold at a coastal city, with the methodology and the raw reading each hashed and the concordant sources shown, plus the live named-storm context from NOAA's National Hurricane Center. A receipt both sides can re-verify moves the argument from correspondence to recomputation.
The trigger and the storm context, signed together.
Set the trigger the way the bond documentation states it: a coastal city, a metric, a comparison and a threshold (the default, wind at or above 63 km/h in Miami, is the tropical-storm-force line). Dynamic Feed reads the current value from a named public source, shows every source it read and whether they concord, computes the determination, and returns one Ed25519-signed Trigger Receipt with a methodology hash and a raw-reading hash. Alongside it, the live named-storm context from NOAA NHC is recorded, and if no storm is active that quiet state is shown honestly, never dressed up as a storm. Nothing is mocked and nothing is stored about you.
full signed receipt (JSON)
Parametric capital settles on one reading.
The premise of a catastrophe bond is that settlement is mechanical: the index crossed the attachment point or it did not, and capital moves accordingly. But when the reading sits near the line, the sponsor, the investors and the regulator can each be looking at a different pipeline, and the dispute becomes a contest of screenshots. A re-computation from an independent witness, tied to a named public source, signed at the moment, with the methodology and the raw reading each hashed and every source it read shown side by side, gives all parties the same fixed point to argue from. The receipt works against every party equally: anyone can re-fetch the source, reproduce the hash and re-run the determination, and get the same answer.
Advisory evidence, not the calculation agent.
Dynamic Feed is a neutral advisory witness, not the calculation agent named in any bond's documentation and not an insurer, regulator or adviser. The seat that computes the contractual settlement belongs to the reporting agencies and calculation agents named in the transaction, PCS and PERILS-class bodies among them; we do not make the settlement decision. This receipt is a second, independently re-computable reading of the data only, from a named public source, and it is not the contractual settlement source unless a transaction explicitly names it. Cat bond documentation defines its own indices, stations, reference periods and units, so the interpretation stays with the transaction's parties and their agents. Advisory settlement evidence, tamper-evident not tamper-proof, zero personal data, and not legal advice. Laws, contracts and bond terms vary.
One API call per trigger event.
Risk-capital and settlement platforms can mint a signed, re-computable trigger receipt the moment an index approaches attachment, keyless to try, self-serve to scale.