Storacha primary sources — 2026-05-09

Notes

• Storacha presents itself as the next stage of Web3.Storage, focused on hot decentralized storage and retrieval.
• The most analytically useful primary-source angle is not just storage pricing or UX, but the combination of UCAN authorization, Filecoin backing, IPFS compatibility, and differentiated node roles.
• No standalone whitepaper was located during this pass.

Primary sources reviewed

• https://storacha.network/
  • Official landing page framing Storacha as a decentralized hot storage network and scaling layer for IPFS on top of Filecoin.
• https://storacha.network/node-providers
  • Official node-operator page outlining early storage-node participation and future retrieval/indexing roles.
• https://docs.storacha.network/
  • Official docs home describing Storacha as a revitalization of Web3.Storage that uses UCANs, Filecoin, and IPFS together.
• https://docs.storacha.network/concepts/ucan/
  • Official explainer for UCAN-based user-controlled authorization and delegation.
• https://github.com/storacha
  • Official GitHub org showing the protocol surface is split across specs, storage-node, indexing, and upload services.
• https://github.com/storacha/specs
  • Official specs repo for the w3up protocol stack, including account/session/storage/Filecoin-related capability specs.
• https://github.com/storacha/piri
  • Official Provable Information Retention Interface storage-node repository.
• https://filecoin.io/blog/posts/introducing-storacha---the-future-of-hot-decentralized-data/
  • Launch framing for Storacha’s architecture, goals, and node-role model.

Key takeaways captured for corpus

• Storacha is best treated as a hot-storage/retrieval layer with a capability and delegation model, not just as another storage chain.
• UCAN-based authorization is central to the product’s claim of user-owned data and portable delegation.
• Storacha explicitly positions itself between IPFS retrieval and Filecoin durability, making it a useful comparison class for layered storage stacks.
• The architecture’s practical trust/control surface seems to include capability issuance, upload semantics, indexing, retrieval-node topology, and the Filecoin-backed durability pipeline.