ALL SYSTEMS LIVE·DRILL & BLAST · ADVISORY EVIDENCE · NEUTRAL WITNESS
DATA WITH RECEIPTS · ED25519 · RFC 3161·--:--:-- UTC
Home  /  Weather evidence  /  Blast conditions
MINING · DRILL & BLAST · WIND, TEMPERATURE & INVERSION-RELEVANT READINGS

What were the conditions when you fired? Signed.

Fume and dust events are decided on evidence. When a blast throws fume over a boundary, the investigation asks what the wind and temperature were doing at fire time, and the ordinary shot-day weather log is an editable file produced by the party under investigation. This page returns a signed, independently re-verifiable receipt of the wind against a stated site limit, plus the temperature and conditions at the site, and every reading Dynamic Feed serves is archived, so what the record said at fire time stays re-checkable. A neutral, timestamped record beside the shotfirer's own procedure. A deferred blast is a defensible six-figure decision, and this is the record that stands behind it.

LIVE

The conditions at your site, right now.

Enter a mining town and your site wind limit. Dynamic Feed reads the current wind against that limit and returns one Ed25519-signed trigger receipt, then records the temperature and conditions as observed evidence from /v1/answer. Where a second independent source agrees within tolerance, the receipt shows that corroboration in-line. Nothing is mocked and nothing is stored about you.

wind limit km/h
the wind determination is a trigger receipt: observed wind_kmh ≤ your stated limit → within limit. temperature and conditions are recorded as observed evidence, with concordance shown when a second source agrees. wind and temperature are numerical-model readings at the site coordinates, not a physical station reading, and not an inversion or dispersion forecast
WHY IT MATTERS

Fume events are decided on records.

When a fume or dust event reaches a regulator, the shotfirer's account is weighed against whatever contemporaneous data survives. The problem is that the shot-day weather log, the wind reading written into the shot record, the spreadsheet the site keeps, are all editable files produced by the party under investigation. They prove little on their own. A contemporaneous record from an independent witness, signed at the moment against a stated limit, carrying its source and observation time, and re-verifiable years later against a published key, is the kind of corroboration a regulator and a site can both check. And when a second independent weather source agrees on the reading within tolerance, the receipt says so, so the record is not one source taken on trust.

Data with Receipts. The receipt proves what the named public sources reported for the site at that time, that a second source agreed or did not, and that the record has not been altered since. It is one independent input beside the shotfirer's procedure, the site's own log and the blast management plan, not a replacement for any of them.
THE BOUNDARY

Evidence, not a clearance decision.

held on purpose

Dynamic Feed is a neutral witness, not a regulator, a shotfirer or a blast adviser. The receipt records the wind against a limit you state, and the temperature and conditions at the site, from public weather sources evaluated at the site coordinates. It is not a physical anemometer reading at the bench, and not an inversion, fume-cloud or dispersion forecast. It does not clear a blast, does not say conditions were safe to fire, and does not interpret your blast management plan or any regulatory limit, which vary by jurisdiction, site and permit. This is a live-now receipt: it records the conditions at the moment you request it. Advisory evidence beside the shotfirer's own procedure, tamper-evident by signature rather than trusted on our word, zero personal data, and not legal advice.

FOR BLAST MANAGEMENT & MINE SOFTWARE

One API call per shot record.

Blast management and mine environmental software can mint a signed conditions receipt the moment a shot is logged, keyless to try, self-serve to scale.