◈ Ask this one first
What happens to your proofif this company stops existing.
Careful buyers in this category put the question ahead of every other, and they are right to. Nearly every answer to it is a promise. Ours is a procedure, and further down this page you can watch it run in a future that no longer includes us.
Pretend we are gone.
Flip the switch. Everything of ours fades: the navigation, the buttons, the conveniences. What the check needs stays lit.
Flip it. Nothing is sold on the other side.
Your record is a transaction in Base’s public history. We cannot edit it, delete it, or take it back from you. No policy makes that so; there is simply no mechanism by which we could, and none we could build. The company can stop existing. The record will not notice.
01 What it does depend on
Three things, and none of them is our database.
“Independent” carries a narrow meaning on this page: the checking path stays out of our API and our records. The check still rests on something, though. Everything it rests on is listed here, in full.
The exact file
Byte for byte, unaltered. Re-export the PDF or re-compress the image and the fingerprint changes, so the match fails. When that happens, the mechanism is doing its job.
SHA-256 of that sentence, computed in your browser as you type. Change one character and all 64 digits move.
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.
Base history, served by somebody
Any public explorer or RPC provider holding historical Base data will do, and several exist. Alone among the three, this dependency rests on no single party’s promise. Not even ours.
That is the complete list.
We keep records too. As a convenience, never as a requirement.
Our database powers the comfortable path: a records dashboard, lookup by fingerprint, downloadable proof reports, a one-click verification tool. Use all of it freely while you are our customer. Notice, though, that none of it appears in the list above. The check runs without it, and that absence is the entire argument of this page.
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.
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.
It also carries no legal presumption in any jurisdiction. None of these limits arrived with us, and none of them leaves with us. A record establishes which bytes existed by which date; 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?
The transaction is in Base’s public history and we cannot alter or delete it. You can check a record without us: recompute the digest from the file you kept and read the transaction through any Base explorer or RPC provider. That still depends on things — the exact bytes, the processing rule, the receipt, and someone serving Base history — but none of them is our database.
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 produces a different fingerprint and 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.