Every anchored document creates an unbreakable chain of proof on the Bitcoin Cash blockchain. No central authority. No trust required. Just math and cryptography.
BCMR + a SHA-256 hash of the metadata document + its IPFS address. This follows the Bitcoin Cash Metadata Registry standard, allowing any CashToken-aware wallet to discover the token's metadata.The file's SHA-256 hash appears in three independent places:
If any single link in this chain is tampered with, the hashes won't match and the tampering is immediately detectable. No one — not even TrustAnchor — can alter the on-chain record.
CashTokens are a native token protocol built directly into Bitcoin Cash (activated May 2023). Unlike tokens on other blockchains that rely on smart contracts, CashTokens are validated by every node on the network as part of the consensus rules.
TrustAnchor mints an immutable NFT — a non-fungible token with capability: none, meaning it can never be modified after creation. The token's commitment field holds up to 40 bytes of arbitrary data, which we use to store the file's SHA-256 hash (32 bytes).
The token category (a unique identifier) is derived from the genesis transaction, making every verification token globally unique and traceable back to its moment of creation.
BCMR (Bitcoin Cash Metadata Registry) is an open standard for associating metadata with CashTokens. It works by publishing an OP_RETURN output in the token's authchain — a linked sequence of transactions starting from the token's genesis.
The OP_RETURN contains three pieces of data:
BCMR — the protocol identifier (4 bytes)Any wallet or application can follow the authchain, find the OP_RETURN, fetch the metadata from IPFS, verify its hash matches, and display rich information about the token. No central server required.
IPFS (InterPlanetary File System) is a decentralized storage network where files are addressed by their content hash, not by a location. This means:
TrustAnchor pins both the BCMR metadata and the original document (for public anchors) to IPFS, ensuring they remain available independently of the TrustAnchor website.
Public anchors upload the file to IPFS and create a full BCMR metadata record. Anyone can download the original file and independently verify everything.
Private anchors never upload your file. The SHA-256 hash is computed in your browser, and only the hash leaves your device. An immutable CashToken is still minted with the hash in the commitment, proving the document existed at that point in time — but the file itself remains entirely in your possession.
To verify a private anchor later, the original file must be provided. Its hash is computed and compared against the on-chain commitment.
TrustAnchor connects directly to Bitcoin Cash network nodes via the Electrum protocol to fetch raw transaction data and decode it. The On-Chain Proof section on every verification page shows:
This data is not read from a database — it is fetched and decoded from the actual blockchain in real time. You are seeing the same data that every Bitcoin Cash node on the planet has validated.
Once a document is anchored, the proof exists entirely on public infrastructure. If TrustAnchor ceased to exist tomorrow, your verification would still be intact:
Anyone with a Bitcoin Cash node and access to IPFS can independently verify an anchored document without ever contacting TrustAnchor. The blockchain doesn't need our permission, our servers, or our cooperation. That's the point.