What an attestation binds
At its core, an attestation links three things: an artifact’s hash, the derived key that signed it, and a timestamp. Together they fix the fact that this content existed, signed by this key, at this time.
Why on-chain
Recording the binding on Base makes it public, ordered, and tamper-evident. Anyone can later verify a claim without trusting human.cv — the ledger, not the platform, is the source of truth. That is what turns a promise of ownership into a proof of it.
The attestation reveals little
On its own, an attestation exposes a hash and a key — not your identity, and not necessarily the artifact’s contents. The link to your root stays private until you reveal it.
From attestation to claim
- Attest — bind hash + key + time on Base when you contribute.
- Claim — prove the attesting key descends from your root.
- Verify — anyone checks the attestation and the descent proof against the chain.
Durability
Because attestations live on-chain and artifacts live on Arweave, both halves of a proof outlast the application. Even if every front-end disappeared, the records that say this is yours would remain independently verifiable.