KRC · BlockDAG · PoW · Immutable

Proof of existence
on Kaspa

Permanently timestamp any file on the Kaspa BlockDAG. No accounts. No uploads. No trust. Pure math and chain.

Stamp a file →
1s
First confirm
3 KAS
Per stamp
Forever
On-chain
Proof of ExistenceSHA-256Kaspa BlockDAGUnforgeableNo UploadsClient-side OnlyPrivacy FirstKPP-1 ProtocolImmutableHash-derived AddressesNo CertificatesTransaction History Proof of ExistenceSHA-256Kaspa BlockDAGUnforgeableNo UploadsClient-side OnlyPrivacy FirstKPP-1 ProtocolImmutableHash-derived AddressesNo CertificatesTransaction History
The mechanism

How it works

Three steps. No middlemen. Your file never leaves your device. Only its mathematical fingerprint touches the blockchain.

01
🔐
Hash
Your file is SHA-256 hashed locally in your browser. The hash is a unique fingerprint. Change one byte and the entire hash changes. Your file is never uploaded anywhere.
02
⛏
Stamp
The hash becomes a Kaspa address through deterministic key derivation. A stamp transaction (3 KAS) is sent: 2 KAS to miners, 1 KAS protocol fee, 0.2 KAS proof dust. The timestamp is set by the Kaspa network, not by you.
03
🔍
Verify
Anyone can drop the same file, derive the same address, and check if it has transactions. If yes, the file was stamped. The date is permanent and unforgeable.
The tool

Stamp & Verify

Drop a file. Get permanent proof on the Kaspa BlockDAG. Or verify any file. No receipt needed, the chain is the proof.

One file. One hash. One address.

Every file produces a unique SHA-256 hash. That hash becomes a unique Kaspa address. Sending any transaction to that address is your timestamp, permanently recorded on the BlockDAG.

Verification works in reverse: hash the file, derive the address, check if it has transaction history. If it does, the file was stamped. The earliest transaction is your proof date.

Your file never leaves your browser. Only the hash touches the chain.

STAMP
VERIFY
📄
Drop any file to stamp
image, document, contract, anything
🔍
Drop any file to verify
no certificate needed. The chain is the proof
What it proves

Trustless proof

Two parties. One file. Both can verify. Neither can tamper. The DAG is the witness.

✓ Immutable proof

  • This exact file existed at this exact date
  • Not a single byte has been modified since stamping
  • The timestamp was set by the Kaspa network. Nobody can backdate it
  • Both parties can independently verify the same document
  • Neither party can alter the file without breaking verification

✓ Real-world use

  • Stamp a signed contract so both sides hold the same unbreakable proof
  • Prove your song, design, or code existed before anyone else claims it
  • Lock in an agreement with someone you don't trust. The DAG holds both accountable
  • Timestamp evidence, legal documents, or any file that must never change
  • Share a document knowing any tampering is instantly detectable
Trust model

Security & privacy

No servers. No uploads. No accounts. Every critical operation happens locally in your browser.

🔐

Client-side hashing

Your file is hashed with SHA-256 in the browser via the Web Crypto API. The file never leaves your device. Not even a byte.

🧮

Deterministic derivation

File hash → private key → Kaspa address. Same file always produces the same address. Different file = different address. Pure math.

📡

Transaction history

Verification checks the permanent transaction history via the Kaspa REST API, not just the current balance. Proof survives even if the dust is spent.

⚡

Adaptive fees

If the network is busy, the priority fee bumps automatically. Stamps don't fail during high traffic, they just cost a fraction more.

👁️

Zero personal data

No accounts. No emails. No tracking. No analytics. The wallet key lives in your browser's localStorage — nowhere else.

🛡️

Audited codebase

XSS-sanitized logs. Timeout-protected API calls. File size guards. Response validation. Open source. Read every line.