What Is Content Addressing?
Content addressing identifies data by a hash of the data itself rather than by where it is stored. The address is the fingerprint, so the same content always has the same address, tampering is self-evident, and a file can be fetched from anyone who has it rather than from one named server. IPFS popularised it for distributed storage; the same idea underlies how a verifier re-derives a record’s identity from its bytes instead of trusting a location.
The address that cannot lie
With location addressing, a URL points at a place and trusts whoever controls that place to serve the right bytes. With content addressing, the identifier is derived from the bytes, so asking for an address and getting different content is immediately detectable — the content no longer matches its name.
This is the property the estate’s verifier relies on: a sealed record’s identity is a hash of its canonical bytes, so anyone can re-derive it and confirm they were handed the real thing, from any source.
Related standards
Questions
Does content addressing require a blockchain?
No. It is independent of blockchains; IPFS and Git both use it, and so does any system that names data by its hash.
What happens when content changes?
It gets a new address. Content addressing identifies a specific version of data, not a mutable location.
Keep reading
By Michael Gord · published 2026-10-09 · part of the Agentic Encyclopedia. Dates are the day of publication; events are cited at their own dates.