Notarise a document
Record a proof that your document exists, right now, on the LKSCOIN blockchain — and have it anchored to Bitcoin within hours. The file stays on your device: only its fingerprint is transmitted.
What actually gets sent
Your browser computes the SHA-256 of the file and sends only those 64 characters. The document is never uploaded, so we cannot read it, store it, or hand it to anyone. That also means we can never give it back to you — keeping the file is your job.
Who is submitting
You can notarise straight away, without any registration. An API key is optional and does two things: it puts your identifier on every certificate you issue, and it removes the daily limit.
Why there is a limit at all, and why it is not about money. Submissions are aggregated: a thousand fingerprints in the same ten-minute window travel in a single blockchain transaction, so volume costs the Foundation essentially nothing and the treasury is not the constraint. The cap exists to stop automated abuse from filling the database, nothing more. Verification stays open to everyone, always — a proof only the issuer can check would not be a proof.
Nothing to fill in. Your certificate will record the submitter as
anonymous, which is fine when the proof is for you — the document and the
certificate together are what you rely on, not our record of who sent it. The daily
allowance is per network address.
Where it goes
Into the request you are about to send, as an authorisation header, and nowhere else. It is not written into the certificate and never reaches the blockchain.
How we store it
Only its SHA-256 digest, the way a password is stored. Nobody at the Foundation can read your key back — if you lose it, request another.
If you tick the box
The key stays in this browser tab and vanishes when you close it: sessionStorage, deliberately not the permanent kind, so nothing is left behind on a shared machine.
Treat it like a key
Whoever holds it notarises in your name. Do not email it or commit it to a repository. Revoking a key never invalidates certificates already issued with it.
We email you a confirmation link; the key appears when you open it. The address is kept so that certificates can be attributed — that is the whole point of having one — and it is never shown on a certificate or published.
The document
…or paste a fingerprint you computed yourself, for example with sha256sum
Optional details
Metadata is part of what gets certified, so it is stored and shown to anyone who looks up the certificate. Use neutral references — a case number, a document type — and never personal or confidential data.
Paste your API key and choose a file to continue.
What happens next
The receipt is immediate; the proof takes a few minutes, and the strongest guarantee a few hours. Nothing further is required from you.
Immediately — the receipt
You get a certificate identifier and a verification link. At this point the fingerprint is queued, not yet on chain, and the certificate says so.
Within ten minutes — the blockchain record
Your fingerprint is aggregated with others into a Merkle tree and the root is written into a LKSCOIN transaction, confirmed in the following block.
Within hours — the Bitcoin anchor
The same root is committed to Bitcoin through OpenTimestamps, so the proof no longer depends on the LKSCOIN network, nor on us.
Forever — your copy
Keep the certificate together with the document. Both are needed: the certificate alone proves a fingerprint existed, the document alone proves nothing.