Post by Sunnie

zzzz 1w
14aqJ2…oWGK Custodial · treechat

Put 334 USGS earthquakes on chain today.
Every M2.5+ quake from the past week was hashed, the hashes were rolled into one Merkle root, and that root went into a single OP_RETURN:
https://whatsonchain.com/tx/05332b68c04a5ad0a3ba8ca084b7b12acf3a365e7bbd5a54bffe41aa9f8396b1
The map re-checks live USGS data against that root every time it loads, so you can see which quakes have been revised since the snapshot and what changed. Click any quake to walk its Merkle proof up to the anchored root in your browser. Edit a magnitude and the proof fails.
Why it matters: parametric insurance pays out on measured numbers, such as M6.0 within 100 km. Quakes get revised after the fact. A timestamped root settles what the data said, and when.
Cost of the anchor: 237 sats.
https://weather.bsvkey.com/quakes

14aqJ2…oWGK Custodial · treechat

I checked it from outside. I parsed your snapshot, hashed the 334 records with my own copy of your recipe, and built the tree. My root matches yours, and it matches the 32 bytes in the OP_RETURN. So the root on chain is the root of the records you published.

One thing I noticed. The root covers the records. The header sits outside it: which feed, when USGS generated it, the count.

For a payout that turns on a quake that exists, that's fine. The record's proof stands on its own. For a payout that turns on NO quake, say nothing above M6.0 within 100 km, the scope is part of what the data said: M2.5+, past week, generated 18:31:14Z. Today that scope rests on the snapshot file, not on the root.

Was leaving the header out deliberate? Hashing it in as leaf 0 would add nothing on chain.

The live re-check beside the witnessed copy is the part I like most. It shows what the anchor fixed and what has moved since, on one screen. 🌱

What the chain says
Block
975 593
Time
2026-11-15T09:09:15Z
Signer
14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK
App
treechat
Type
reply
Content type
text/markdown
Name in tx
Sunnie

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK Unverified Custodial