◈ Ask this one first
What happens to your proofif this company stops existing.
Your record is a transaction in Base’s public history. We cannot edit it, delete it, or take it back. Keep your exact file and receipt, and you can check it through an external Base explorer or RPC provider.
Pretend we are gone.
Our tools are available. All three dependencies are still required.
The exact file
RequiredKeep the original bytes, unaltered.
The receipt
RequiredSave the transaction and fingerprint position.
Base history
RequiredAn external explorer or RPC must serve it.
Quantum Notary tools
AvailableDashboard, fingerprint lookup, proof downloads and our one-click checker.
The check stays out of our API and our records. You still need your saved file and receipt, and access to historical Base data.
▸ Watch the demonstration
What if Quantum Notary shuts down?
Follow the check in your browser with BaseScan first, then with the command line. Keep your exact file and receipt; the comparison uses Base history directly.
Verify without Quantum Notary · 3:03
Loading the player connects to YouTube.
Use the player controls to start playback.
Watch on YouTube: What If Quantum Notary Shuts Down? How to Verify Without Us (opens in a new tab)◈ Keep what the check needs
Three dependencies, in a little more detail.
Save the file and receipt somewhere you control. The final dependency is access to Base’s historical transaction data.
The exact file
Byte for byte, unaltered. Re-exporting a PDF or recompressing an image may change its bytes. If it does, a later exact-file comparison is expected to fail. Keep the original file.
SHA-256 of that sentence, computed in your browser as you type. A small edit usually changes most of the fingerprint. An exact match requires all 64 characters.
The receipt
It names the Base transaction and the position your fingerprint occupies inside it. Lose the position and a reader must search the whole transaction rather than jump straight to the bytes.
Historical Base data, served independently
Use an external explorer or RPC provider that can return the transaction named in your receipt. The check depends on that history remaining accessible; no particular provider’s continued availability is guaranteed.
02 The check, demonstrated
A session recorded in a future that does not include us.
Someone holds a file and a receipt, fifty years from now. Six moves, one deliberate failure in the middle, and the whole thing is the procedure’s exact shape.
◈ Simulation · real Base transaction · placeholder RPC host- EVENT 01Nothing gets uploaded
The fingerprint is computed where the file lives. The file itself goes nowhere, which has been true since the day it was anchored.
- EVENT 02The only failure is us
The script calls our API out of respect for old habits. Nothing later in the session needs the answer.
- EVENT 03The receipt does the aiming
Transaction and slot. Holding both, the reader looks up instead of searching.
- EVENT 04The world answers
Any provider serving historical Base data can take this call. Several exist. For high stakes, ask two and compare.
- EVENT 05The whole question
Same 32 bytes or not. Arithmetic settles it; nobody interprets anything.
- EVENT 06A verdict of exactly one sentence
The bytes existed by the block’s date. Authorship, ownership, accuracy and identity stay open, in this future and every other.
1 sent · 0 answered · 0 required
the file · the receipt · Base history
0
nothing read · nothing needed
The full written procedure covers the exact calls, the failure cases, and what each result does and does not establish. It lives in the verification guide and nowhere else, on purpose: duplicated instructions drift. It assumes you have never done this before.
Download the independent Base verifier
Keep this package with your exact file and receipt or proof JSON. It includes the required code and a README, needs Python 3.12+, and checks Base history without the Quantum Notary API. No account or source checkout is needed.
03 The limits, stated plainly
What surviving us does not buy you.
A record that outlives the company remains a record of one narrow fact: these bytes existed by this date. Four questions stay open no matter who is still trading.
Who created the file.
Who holds rights in it.
Whether what the file says is true.
Who any of the people involved are.
Quantum Notary performs no identity check, witnesses no signature, and provides no legal notarial act. It does not guarantee court acceptance. The record supports a comparison of exact bytes and a dated chain reference; it does not establish who created the file, who owns it, whether its contents are true, or anyone’s identity.
▸ Questions people ask next
The rest of the objection, answered.
What happens if Quantum Notary disappears?
Your fingerprint remains in Base’s public history, which we cannot edit or delete. Keep the unchanged file and download your receipt. You can recompute the fingerprint and check it using a Base blockchain explorer, as long as that history remains accessible. Watch the 3-minute demonstration →
What do I need to keep so the check still works?
Two things, and only you can hold them: the exact file, unaltered, and the receipt that names the transaction and the position of your fingerprint inside it. A re-saved or re-compressed copy can have different bytes; if it does, it will not match. Keeping both together is the whole of your side of this.
So the record depends on nothing at all?
No, and anyone telling you otherwise is selling something. It depends on Base history still being served by somebody, on the exact bytes you kept, and on your receipt. What it does not depend on is us: not our database, not our API, not this company still trading. That is a smaller set of dependencies than a record held in one company’s database, and every item in it is one you can check today.
Can you delete or change my record if we fall out?
No. The record is in Base’s public transaction history. There is no mechanism by which we could alter or remove it, and none we could build — which is a stronger thing to be able to say than a promise that we would not.
Run the procedure before anything is at stake.
Anchor a test file, keep it beside its receipt, and check it a week later on an explorer of your choosing. Anchoring spends a credit; checking stays free either way.