How verification works
Why "tamper-proof" is a technical guarantee, not a marketing word.
Across the rest of these docs we say your venture's records are "tamper-proof" and "independently verifiable." This page explains the technology that makes those words literally true. (This is the one place in the docs where we get technical — you don't need any of this to use Entity.ID.)
Records are anchored on Ethereum
When your venture is formed — and every time something meaningful changes: an approval, an ownership change, an amendment — the record is anchored on the Ethereum blockchain via RegistryChain, the public registry protocol Entity.ID is built on.
Ethereum is a global network of thousands of independent computers that all maintain the same ledger. Once a record is written to it, changing that record would require rewriting history across the whole network simultaneously — which is, for practical purposes, impossible. That is the precise sense in which your records are tamper-proof:
- Nobody can quietly edit them — not a partner, not Entity.ID, not a government. Amendments create new records; they never overwrite old ones.
- Nobody has to take anyone's word — a bank or investor can check the record against the public network themselves, without trusting Entity.ID as an intermediary.
- They can't be lost — the record doesn't live on one company's server. If Entity.ID disappeared tomorrow, your venture's history would still exist and still verify.
Addresses resolve like DNS
Your venture's address works the way domain names do — a human-readable name that resolves to the underlying record:
tarka-labs.venture.public.entity.idReading right to left: the Entity.ID public registry → the entity type
(venture) → your chosen slug. Anyone can resolve the address and get the
venture's verified record — the same motion as typing a URL, applied to
organizational identity.
Interoperability
Because RegistryChain builds on open Ethereum naming standards rather than a proprietary format, your venture's identity already works with the existing ecosystem: it's resolvable by 5,000+ software libraries and recognized in 750+ apps and wallets today. Your venture's address can receive funds, sign agreements, and be looked up in tooling that has never heard of Entity.ID.
That's the practical meaning of building on an open standard: your identity isn't locked into one product.
What's public and what isn't
Anchoring doesn't mean everything is exposed. What's publicly verifiable is what needs to be: that the venture exists, its address, its formation, and the integrity of its records (via cryptographic fingerprints). Personal details — KYC documents, IDs, selfies — are not published to the public network. See the FAQ for the breakdown.
Why this matters in practice
Traditional registries are single points of trust: a database row in one government office, verified by calling that office. Your venture's records verify in seconds, from anywhere, by anyone — which is what makes the compliance story fast and the incorporation path smooth.