Acceptance and inclusion are different evidence
A signed acceptance receipt records that Quantum Notary accepted a request. Its signature does not establish Base transaction inclusion. A later proof includes transaction and block references plus the digest slot needed to inspect Base evidence. Read the stamp and date lesson for a demonstration.
Application timestamps such as includedAt and finalizedAt are service observation times
unless a field explicitly identifies a Base block timestamp. Confirmed evidence is a
successful Base L2 receipt observation, not proof of Ethereum L1 settlement.
Find the available downloads
A PDF proof report is free for an eligible confirmed record and uses no credits. Download it from your notarization in Records.
After notarization, the receipt offers Download proof for archivable JSON and Download report for a PDF when the relevant evidence is available. Verify, Share and View transaction on block explorer ↗ help inspect or share the result.
In Records, open a record and use Summary, Technical details and Acceptance receipt. Available actions include Download PDF Report, Verify it now, Share verify link and Block explorer ↗. The Acceptance receipt panel offers copy jws, verify offline and verify online. These signature checks do not establish Base inclusion.
Proof/report actions can be unavailable while processing, during evidence review, or when the service cannot prepare a report. Follow Record statuses and retry the download when available; a download error is not a new notarization request. The sample report is an illustrative layout, not a real record.
Preserve a complete evidence package
Keep these together in storage you control:
- The exact original file bytes, with an independently maintained backup.
- Available receipt/proof JSON, signed acceptance receipt and PDF report.
- The SHA-256 digest, transaction hash, block hash and number, chain identifier and
batchIndex/batchSizewhen present. - The input-processing description and any exact canonical-byte artifact needed to reproduce the fingerprint for structured inputs.
The report summarizes evidence; it cannot recreate the source file.
Save the independent verifier
Download the Python verifier package (.zip) and its SHA-256 checksum. Extract the ZIP and keep the complete folder with your receipt or proof JSON and exact original file.
The package includes the required code and a README. It needs Python 3.12+ and a Base RPC endpoint, with no source-repository access or third-party Python packages. Follow Direct Base verification for setup, commands and results. These downloads and instructions are also available without an account, so a recipient can use the package with evidence you choose to share.
Share intentionally
A verification link may reveal a digest or public transaction reference. A proof export can also contain off-chain metadata. Review what you share with its intended recipient.