Arke
Build

Attestation

Permanent attestation of entity versions to Arweave for independent verification.

Overview

Arke permanently attests entity versions to Arweave, a decentralized permanent storage network. This ensures that:

  • Full manifests (not just hashes) are stored permanently
  • The network can be reconstructed from Arweave alone
  • Third parties can independently verify content integrity

How It Works

  1. Entity version is created or updated
  2. The full manifest is queued for attestation via D1's attestation_queue table
  3. An async process uploads the manifest to Arweave
  4. The Arweave transaction ID is indexed in KV (attest:{pi}:{ver})
  5. The prev_cid chain provides ordering guarantees across versions

Verification

Anyone can verify an entity's history by:

  1. Querying Arweave for the entity's attestation records
  2. Verifying the content hash matches the CID
  3. Following the prev chain to reconstruct the full version history

Attestation Status

Check the attestation status of an entity:

GET /attestations/:entityId
Authorization: Bearer <token>

Returns the list of attested versions with their Arweave transaction IDs.

On this page