JFD DOCUMENT VERIFICATION — JFD-20260814-XAM-00007

Status

SEALED

• 2026-08-14T18:54:49Z — SEALED

The mark, as issued

JFD * XAM * L2 * RETURN * SEALED * JFD-20260814-XAM-00007
SHA256 91fe31e1aa605321 * LEDGER NOT_SEALED:jfd.document.seal-unregistered:tpa-lane * SIG UNSIGNED:signed-at-seal-not-at-assembly * OTS NOT_ANCHORED-AT-ASSEMBLY:see-verify-page
VERIFY jetfyul.com/v/JFD-20260814-XAM-00007

Provenance chain

• doc_sha256 (full): 91fe31e1aa6053211ee57655e5ea806d1e56188ce542f72c0227a98295787e95
• ledger: SEALED — 2205203
• OpenTimestamps: STAMPED_PENDING_ATTESTATION — Bitcoin attestation matures in hours; `ots upgrade` the proof, then it verifies offline forever.
• assembled: 2026-08-14T18:54:49Z

Verify offline, without trusting us

1. In the delivered PDF's raw bytes, locate the two mark strings exactly as printed above (the SHA256 line and the VERIFY line).
2. Replace each with a run of '#' of identical byte length.
3. SHA-256 the result. Its first 16 hex characters must equal the value printed on the document, and the full digest must equal doc_sha256 above.
4. If a .ots proof accompanied the document, run ots verify against the delivered file - the attestation is anchored in Bitcoin and needs no contact with us.

The full procedure is published at /method. A hash a verifier cannot reproduce is decoration.