human.cvhuman.cv

Architecture

Permanent Storage

Artifacts are written to Arweave — once, and forever. Permanence isn’t a feature here; it’s the entire point of leaving a legacy.

Why Arweave

A legacy that a platform can delete is not a legacy. Arweave stores data permanently with a one-time payment, which makes it the natural home for anything meant to outlive the service that created it. The artifact stops depending on human.cv, on any company, or on any single server staying online.

Paying with ETH on Base, via Irys

Contributors never have to leave the Base experience to write something down forever. Storage is funded with ETH on Base and bridged to Arweave through Irys, so the act of making something permanent feels like any other on-chain action.

Content addressing

What lands on-chain is the artifact’s hash, not its bytes. The hash is what an attestation binds to a key — so the same file, re-hashed later, still matches your derivation tree without re-uploading.

What gets stored

  • The artifact itself — a file, an image, a post body, a commit bundle.
  • Minimal metadata needed to verify integrity and ordering over time.

Sensitive material can be encrypted before it is written, so permanence never forces exposure — the bytes persist, but only the holder of the key can read them.

Permanence and privacy together

Storing forever and revealing selectively are not in tension. The artifact can sit encrypted and permanent on Arweave for years; the proof that it’s yours is disclosed only when you reveal. Time does the preserving; you control the unveiling.