Code Docs

WarmWeb Product Design

Architecture Overview

Filecoin Onchain Cloud Modules & How We Use Them

3.1 Synapse SDK

• Why: Single developer SDK to interact with Filecoin Services (upload, retrieval, deal mgmt).
• Usage in WarmWeb:
  • synapse.storage.put(files, {replication, warm:true}) to upload site bundle.
  • synapse.storage.status(cid) to monitor migrations/deals.
  • synapse.pay.meter() to fetch estimated costs; power usage-based billing UI.
• Depth: Core path for all writes/reads.

3.2 Filecoin WarmStorage Services

• Why: Low‑latency storage tuned for hot/warm retrieval of static assets.
• Usage:
  • Primary store for all deployed site bundles (tar/zip of /dist).
  • Retention and replication policies configurable per site.
• Depth: All sites reside here; no centralized mirror.

3.3 FilCDN

• Why: Global caching & edge acceleration for CIDs.
• Usage:
  • Map domain → CID; CDN routes visitors to nearest edge.
  • Automatic cache invalidation on new publish (CID/version bump).
• Depth: Mandatory path for public traffic.

3.4 Filecoin Pay (Contracts)

• Why: On‑chain payments for storage/retrieval usage and creator monetization.
• Usage:
  • Creator wallet linking: receive tips/payments/subscriptions.
  • Pay‑gated sections: token‑gated or NFT‑gated download/sections via Pay receipts.
  • Usage billing: end‑user pay‑per‑GB (optional) and creator‑pays storage.
• Depth: Integrated at account layer and per‑site policy.

3.5 PDP (Provable Data Publication)

• Why: Verifiable evidence that a specific CID was published at a given time; integrity attestations.
• Usage:
  • Publish receipts recorded with PDP proof hash in Index.
  • Version history: chain of CIDs with proofs to show content lineage.
• Depth: Default on for public sites.

Overview: Previous

Next: Detailed System Design

Table of Contents