Glossary › Entity stamp

Entity stamp — a tamper-evident version history of a fact sheet

An entity stamp is a hash of a signed-off fact profile, published with every superseded version, giving a tamper-evident history of what a business published and when — and, once that hash is anchored in a public ledger, a notarized and timestamped one.

The profile is hashed. The hash is anchored publicly. The page we host lists every version, its hash, the date, and a link to the anchoring record, and publishes the exact bytes that were hashed so anyone can check the hash themselves. That is the whole mechanism, and it is small on purpose.

What it is for: a business that changes a published commitment can show what the commitment was, and a superseded version stays in the history instead of being quietly overwritten. What it is not for: proving who you are. We are specific about this because the category is full of language that implies more.

Where our own record stands today, since a definition is cheap and a worked example is not: every version of our fact sheet is frozen and hashed, the exact bytes of each one are published, and none of them has been anchored yet — there is no funded anchoring wallet. So our history page says timestamp pending on every row and our badge says tamper-evident rather than notarized. It said notarized until an audit of this site caught it, which is exactly the defect we charge to remove: a claim that had outrun its evidence. The wording is generated from the record now, so it cannot say more than the record supports.