TrustAnchor is a document verification service that creates permanent, tamper-proof records of your files. When you verify a document, we compute its unique digital fingerprint and anchor it to a public blockchain — creating an immutable record that proves the file existed in its exact form at that point in time.
Any digital file — documents, photos, videos, contracts, designs, source code, medical records, legal filings, certificates, or any other file type. If it's a file, you can verify it.
Every file has a unique digital fingerprint called a SHA-256 hash. Even changing a single byte produces a completely different hash. TrustAnchor records this hash on the blockchain as an immutable NFT token, and stores the original file on IPFS (a distributed storage network) and CDN. Anyone can later re-upload the same file and verify it matches the original record.
SHA-256 is a cryptographic algorithm that generates a unique 64-character "fingerprint" for any file. It's the same technology used by banks, governments, and security systems worldwide. Two different files will always produce different hashes, and the same file will always produce the same hash.
TrustAnchor uses the Bitcoin Cash (BCH) blockchain with CashTokens technology. We chose BCH because it offers extremely low transaction fees (less than $0.01 per verification), fast confirmations (typically under 10 minutes), and a well-established, decentralized network. CashTokens allow us to mint immutable NFTs that permanently store your file's hash as an on-chain commitment.
IPFS (InterPlanetary File System) is a distributed storage network where files are addressed by their content hash rather than a location. This means your verified files are stored redundantly across multiple nodes and can be retrieved by anyone with the hash — providing censorship-resistant, permanent storage.
CashTokens are a native token system on Bitcoin Cash that allows creating Non-Fungible Tokens (NFTs) directly on the blockchain. Each verification creates an immutable NFT with your file's hash embedded as its "commitment" — a permanent, unforgeable record. The NFT's metadata (BCMR) is published on IPFS and referenced via an on-chain OP_RETURN transaction.
No. TrustAnchor handles all the blockchain operations automatically. A small wallet is created in your browser to mint the verification tokens, and the cost per verification is less than a penny. You don't need any prior crypto experience to use the service.
No. Only the file's SHA-256 hash (fingerprint) is stored on the blockchain. The file itself is stored on IPFS and our CDN. This keeps blockchain costs minimal while still providing cryptographic proof of the file's existence and integrity.
The Free plan includes 3 verifications per month at no cost. Paid plans start at $9.99/month for 50 verifications. The blockchain transaction cost is less than $0.01 per verification. See our pricing page for full details.
Yes. Each verification creates a new, independent blockchain record. This can be useful if you want to prove the file existed at multiple points in time.
Your files are stored on IPFS and CDN, which are accessible via their hash. The blockchain record is public. If you need to verify sensitive documents, the hash alone does not reveal the file's contents — but anyone with access to the original file can verify it matches. See our Privacy Policy for more details.
Your wallet's private keys are stored in your browser's IndexedDB storage and never leave your device. We never have access to your keys. You're shown a seed phrase during wallet creation — write it down to recover your wallet if you clear your browser data or switch devices.
The Anchor Feed lets you follow BCH addresses or @handles to see their public anchored content — photos, documents, and files they've verified on the blockchain. No algorithm, no ads. Just verified content from the people you choose to follow.
Anyone can leave typed comments on an anchor. Each comment has a specific purpose:
Attestations are especially powerful — they turn a single-party claim into multi-party verification. A document anchored by one person and attested by three independent parties carries real weight.
Yes, a small BCH micro-payment is required for every interaction. This serves two purposes: it prevents spam, and it creates a circular economy where content creators earn from engagement on their anchors. The payment is split between the content owner and the platform. Typical costs are around 2,000–5,000 satoshis (a fraction of a cent).
Yes. Every comment, attestation, and like is published to Nostr — a decentralized relay network. TrustAnchor stores a copy in its database for fast display, but the authoritative record lives on Nostr relays, independently verifiable by anyone.
No. All signing happens in your browser using the private key stored in your wallet. When you post a comment or like, two signatures are created client-side: an ECDSA signature for the BCH payment transaction, and a Schnorr signature for the Nostr event. Both use the same private key, but TrustAnchor never sees it. The server only receives pre-signed data and relays it.
Yes — every comment has a fully verifiable cryptographic chain, even if TrustAnchor went offline:
bch-txid tag linking
back to the payment transaction.This bidirectional link means the BCH payment proves who paid, the Nostr event proves what they said, and the shared cryptographic key proves both came from the same person — no trust in TrustAnchor required.
Yes. Each post in your feed has a hide button (×) that removes it from your view. Hidden posts are stored locally in your browser — they remain on the blockchain and Nostr, but you won't see them in your feed anymore.