human.cvhuman.cv

Architecture

Architecture Overview

Two chains, two jobs. Base handles identity and attestation; Arweave handles permanence. Together they make a claim both cheap to record and impossible to erase.

The division of labor

Every contribution splits cleanly: the artifact goes to permanent storage, and a proof of ownership goes on-chain. Keeping these on the right substrate is what makes the system affordable and durable at the same time.

  • Base — consumer-grade, low-cost attestations and ERC-4337 smart accounts for identity.
  • Arweave — write-once, keep-forever storage for the artifacts themselves.

The flow of a contribution

Trace any upload, post, or commit and it follows the same path:

End to end

artifact → hash → written to Arweave (permanent) → attestation on Base, signed by a derived key → later, a reveal proving the key descends from your root.

Why not store everything on-chain?

On-chain storage is scarce and expensive; permanence and identity have different cost curves. Putting bytes on Arweave and only the binding proof on Base keeps fees consumer-friendly while still anchoring ownership to a public, verifiable ledger.

Dive deeper