Sign, then share
Stamping hashes your content locally and signs the hash with the key stored in your own browser. The private key never leaves your device and is never uploaded.
// Content Provenance
TrustStamp
Sign what you create. Let anyone verify who signed it.
Connect a wallet to sign content
TrustStamps are bound to your Trust ID and signed by your wallet.
Connect walletWhat a TrustStamp is
A TrustStamp is a portable proof of authorship: you sign a piece of content with your TrustLayer identity, and anyone can later confirm that this exact content came from this exact human-verified identity.
Anyone can verify
A stamp carries the content hash, the signer identity and the signature. Verification is a pure cryptographic check — no login, no API key, no trust in TrustLayer required.
Anchored for timestamps
Stamps are batched into the daily Merkle anchor on Base, which proves when a stamp existed. Anchor rate on this page shows how many of your stamps are already anchored.
Built for creators
Use stamps to claim authorship of posts, research, artwork or announcements, and to let readers separate your real output from impersonation.
- Impersonation defence for public figures
- Provable publish time for announcements
- Verifiable attribution when content is reposted
Frequently asked questions
- Does a TrustStamp store my content?
- No. Only a hash of the content, your identity reference and the signature are stored. The content itself stays with you.
- What if I lose my device?
- Restore your identity with your 12-word recovery phrase or your bound wallet. Existing stamps stay valid because they are tied to the identity, not the device.
- Can a stamp be faked?
- Not without your private key. Any change to the content changes its hash, and the signature then fails verification.