Arweave primary sources — 2026-05-09

Classification takeaway

Arweave is best cataloged as permanence-oriented storage infrastructure whose key mechanism is the combination of proof-of-access mining and an upfront storage endowment. The important distinction is that Arweave is not mainly a routing layer like IPFS or a storage-market-plus-consensus-weight system like Filecoin. Instead, it tries to make permanent archival storage economically sustainable by prepaying into an endowment and rewarding miners for proving access to uniquely packed historical data over time.

Primary sources reviewed

1. Main site — https://www.arweave.org/

   • Best short framing for Arweave as a permanent decentralized web and community-driven ecosystem rather than a generic storage company.
   • Useful because it states the intended role clearly: permanent data plus an application layer.

2. Protocol overview docs — https://docs.arweave.org/developers/development/overview

   • Most useful current source for SPoRA, the VDF, replica uniqueness, pricing, and the storage endowment.
   • Especially important for understanding that the protocol is trying to optimize storage capacity and replication behavior through incentives, not merely market matching.

3. Denomination docs — https://docs.arweave.org/developers/development/overview/denomination

   • Important because they show a less-obvious control surface: the growth of the endowment can eventually trigger redenomination logic.
   • Useful for seeing how storage economics and monetary-unit practicality are explicitly linked in the live protocol.

4. Official node / protocol repo — https://github.com/ArweaveTeam/arweave

   • Confirms the project maintains a live protocol implementation, protocol papers, and developer toolkit.
   • The repo description is also a concise primary statement of Arweave as a cryptographically verified permanent archive built around the Blockweave data structure.

5. Standards repo — https://github.com/ArweaveTeam/arweave-standards

   • Useful because it shows Arweave is not just a single protocol binary; it also has public standards work for data formats, gateway capabilities, and higher-layer services.
   • This matters when comparing Arweave to IPFS or Filecoin because some of Arweave’s practical control and ecosystem coordination sits in surrounding standards, not only in base consensus.

6. Yellow paper — https://www.arweave.org/yellow-paper.pdf

   • Saved locally as arweave-yellow-paper.pdf.
   • Canonical formal paper for the protocol’s permanence and blockweave design.

7. Lightpaper — https://www.arweave.org/files/arweave-lightpaper.pdf

   • Saved locally as arweave-lightpaper.pdf.
   • Useful shorter companion document for the protocol’s permanence story and economic framing.

Whitepaper / technical-doc status

• The official yellow paper has been saved locally as arweave-yellow-paper.pdf.
• The official lightpaper has been saved locally as arweave-lightpaper.pdf.
• For current mechanism analysis, the live docs are more operationally useful than the older papers alone because they surface SPoRA, VDF-limited mining, address-seeded packing, endowment behavior, and redenomination logic in current language.

Why it stays in the active corpus

• It is the obvious missing comparison for the storage-durability cluster already built around Archivist, Filecoin, and IPFS.
• It helps separate four often-blurred design centers: routing/distribution (IPFS), storage-market consensus (Filecoin), durability engineering (Archivist), and permanence-through-endowment (Arweave).
• Its most reusable insight is that permanent storage claims are not only about cryptographic proofs; they also depend on who controls the economics of long-horizon prepayment, fee routing, replica incentives, and ecosystem standards layered around the archive.