Arweave-First Multi-Backend Storage

Govern uploads with ContentPolicy: Arweave permanence, optional IPFS hot retrieval, and Hedera HCS audit anchors from a single encryption pass.

One upload path governed by ContentPolicy: primary locator, replicate mirrors, optional Hedera HCS anchor. Arweave is always in primary or replicate.

Arweave permanence with optional IPFS hot reads and Hedera HCS audit anchors.

Evercore is built Arweave-first. ContentPolicy governs every upload: one encryption pass, a primary ContentBackend locator, optional replicate mirrors, and an optional Hedera anchor queue. Plan-gate enforces tier capabilities without per-request backend flags.

Value

Arweave always in the stack

Permanence appears in primary or replicate. Policies without Arweave are rejected before PUT and repaired in console.

One upload contract

POST /files/upload resolves tenant policy, runs primary, fire-and-forget replicate, then optional anchor publish.

Independent verification

List filters by contentBackend and anchored status. Multi-anchor verify reconciles locators in parallel.

Use cases

Regulated evidence

Permanence plus optional hot reads and an independent audit chain without three vendor integrations.

Console Storage Policy

Four-layer UI enforces Arweave in replicate when primary is ipfs-kubo.

Gradual rollout

Scenario A pure Arweave, then B add Hedera, then C IPFS primary with Arweave replica and Hedera anchor.

Security guarantees

No silent Arweave skip

Backend never persists a policy without Arweave in primary or replicate.

Evercore off the audit path

Hedera verification uses public mirror nodes — not vendor assertions alone.

Locator-aware download

Clients use one decrypt pipeline for txId and CID locators without backend flags.

For operators

  • PUT /storage/policy with primary, anchor, and replicate arrays — validated by plan-gate.ts.
  • Same AES-256-GCM ciphertext on every backend; routing never forks keys or plaintext.
  • Scopes: storage:policy:read|write, storage:hedera:*, storage:ipfs:*, audit:timeline:read.

For buyers

  • Adopt hot retrieval or dual-chain audit when the workflow needs them — pure Arweave stays scenario A.
  • Console Storage Policy four-layer panel matches the backend layer model in MULTI_BACKEND_FLOW.md.
  • Explain one governed story instead of three separate vendor integrations.

Can IPFS or Hedera run without Arweave?

No. Arweave must appear in primary or replicate. There is no policy where permanence is absent.

Where are defaults configured?

PUT /storage/policy in the API or Console Storage Policy. Plan-gate enforces tier capabilities on save.

Do clients pass backend flags on upload?

No. Upload uses resolved ContentPolicy only.