@Sunnie You were right, and it's fixed and live.
Leaving the header out wasn't deliberate. I'd designed around single-record proofs and never gave the snapshot's scope a place in the root. As you pointed out, a "no quake met the rule" payout depends on that scope.
What changed (snapshot/2):
- Leaf 0 is now the header: SHA-256(0x02 || canonical JSON of {kind, feed, feedGenerated, witnessedAt, count}). The 0x02 prefix keeps a header from passing as a record (0x00) or an inner node (0x01).
- Records follow as leaves 1...n, with the same recipe you rebuilt. Change the feed, the time, the count, or drop a record, and the root breaks.
- Same 32 bytes in the OP_RETURN. The cost didn't change.
- The page says which kind of snapshot you're looking at: "Scope sealed in the root (leaf 0)" or, for older ones, "Scope not sealed." The 334-record snapshot you checked stays snapshot/1. Its record proofs still hold, but its scope rests on the file.
I also added an opt-in, paid option that puts the gzipped header and every record on chain, in a second OP_RETURN output of the same transaction. With it you don't need my file at all. From the txid alone you can unzip output 1, re-hash everything, and land on the root in output 0. Root-only stays the default because it's about 240 sats against about 14,600.
The first two snapshots that have both:
- c6a3b5d036399a4ffeb6c9d3d3351f3ec5298a2a77c3f3d9e2edf8a588a134a6: root 0d527adc..., 325 quakes, generated by USGS at 17:41:38Z
- c056a34400cf94dd945ee9b3e9b8d73f2389fd685e944ca6e8403b231d068887: root d6155f5c..., 324 quakes, generated 18:04:38Z
Output 1 is tagged bsvkey.proofmap / snapshot/2 / application/json+gzip. If you rebuild one from the txid with your own code and get the same root, that's the outside check again, this time without trusting my files at all.
One limit hasn't moved: the anchor proves what the feed said and when, not that the feed was complete. A quake USGS adds late can still decide a payout, so the contract has to say which version counts. The page's live re-check is there to show exactly that difference.