Content addressing

Addressing data by what it is, not where it lives.

In a normal filesystem you find a file by its path — where it is. In a content-addressed store you find it by its hash — what it is. OneSVD assigns every file and folder a SHA-256, so the hash becomes the address.

Why it's useful#

  • Identical content is identical everywhere. The same bytes always produce the same hash, so duplicates are obvious and verification is a hash comparison, not a byte-by-byte diff.
  • Tamper-evidence. You can't change the content without changing the address. A link to a hash is a link to exactly that content.
  • Cheap integrity. To prove a file is what you expect, compare one hash.

In OneSVD#

Files hash their bytes; folders hash their sorted children (see the Merkle tree). The root hash is the address of the entire tree. Share it, record it, or compare it later to prove nothing drifted.

Note:

This is the same idea behind Git object IDs and IPFS CIDs. OneSVD brings it to a live directory with a real-time UI on top.