“The Arweave Yellow Paper” is the 2019 technical paper by Samuel Williams and the Arweave Foundation describing the Arweave storage protocol — a blockchain-based system for permanent, one-time-payment data storage. Where IPFS provides content addressing without storage guarantees and traditional cloud storage requires recurring payments, Arweave’s model is to pay once and store forever — funding permanent storage through an endowment model based on expected declining storage costs over time.

The paper introduces the blockweave data structure (a modified blockchain where blocks reference multiple prior blocks), Proof of Access (PoA) consensus (miners must prove they store historical data to mine), and the permaweb concept (a permanent HTTP-accessible layer built on Arweave).

> Yellow Paper: Available at arweave.org/yellow-paper.pdf.

---

Publication and Context

The “permanent storage” problem: who pays for storage in 50 years when the person who uploaded content may be dead or disinterested? Subscription-based storage always risks cancellation. Cloud providers regularly delete old customer data.

Arweave’s argument: storage cost per GB has declined ~30.5% per year historically (Moore’s Law for storage). A one-time payment equal to current cost × expected future years of storage can be invested as an endowment; as storage costs decline, the endowment’s purchasing power grows faster than the required storage bill, making permanent storage financially sustainable.

---

Blockweave Structure

Rather than a traditional blockchain (where each block references only the previous block), Arweave uses a blockweave — each block references:

1. The immediately preceding block (standard chain link)
2. A recall block — a randomly selected older block from the chain history

Why recall blocks? The recall block is chosen pseudorandomly and must be included in the new block. A miner who doesn’t have the recall block stored locally cannot mine the next block efficiently. This creates an economic incentive to store old chain history — the protocol requires it to participate in mining.

---

Proof of Access (PoA)

Arweave’s consensus mechanism is Proof of Access — a variant of Proof of Work where the hash puzzle incorporates both:

• A fresh nonce (standard PoW)
• The actual data from the randomly selected recall block

target_hash = HASH(nonce || recall_block_data || current_block_header)

A miner without the recall block data cannot compute the target hash — they must have the data stored locally. This ties mining probability to storage participation.

SPoRA (Succinct Proofs of Random Access): The 2020-era upgrade replaced the original PoA with SPoRA, which allows miners to prove they can access a random byte within a large dataset using Merkle proofs, rather than hashing the full recall block — making the system efficient for large packing sizes.

---

The Storage Endowment

Every uploaded file pays a fee in AR tokens. This fee is split:

• A transaction fee to the current block miner
• A storage endowment deposit — AR held permanently in a protocol-level contract

The endowment earns implicit value as the AR token appreciates (assuming growing demand for Arweave storage) and as storage costs decline (meaning the same AR can pay for more GB of storage in future years). Miners draw from the endowment to fund long-term data storage costs.

Risk: The endowment model assumes continuous token value appreciation and declining storage costs. A severe bear market in AR could make the endowment insufficient.

---

The Permaweb

Built on Arweave’s storage layer is the permaweb — a system of permanently accessible HTTP-compatible websites and applications:

• HTML, CSS, JavaScript, and other web assets are stored on Arweave
• Gateways (arweave.net and others) serve content at URLs like https://arweave.net/[TXID]
• Since the TXID content never changes, the URL always resolves to the same content
• JavaScript apps hosted on the permaweb can be fully functional, persistent web applications

SmartWeave contracts: Arweave supports a lazily-evaluated smart contract system (SmartWeave) where contract state is computed client-side by replaying transactions, not on-chain.

---

Sections of the Yellow Paper

Section	Content
1. Introduction	Motivation; cost of permanent storage; endowment model
2. Blockweave	Block structure; recall block selection; fork resolution
3. Proof of Access	Mining algorithm; recall block hashing; security analysis
4. Wildfire System	Peer-to-peer sharing incentives for recall block data
5. Blockshadowing	Batched transaction propagation optimization
6. Library Storage	Commitment scheme for IPFS-compatible content
7. Storage Endowment	Economic model; fee calculation; long-term sustainability

---

Reality Check

Arweave has genuine, demonstrated utility:

• Solana stores block data on Arweave (via the Metaplex/Shadow Drive integration)
• NFT metadata is stored on Arweave by major platforms (Bundlr/Irys, AR.io)
• Mirror.xyz (Web3 blogging platform) stores all posts on Arweave permanently

Caveats:

• The endowment model assumes perpetual AR token demand. If Arweave loses relevance, the endowment funds are worth whatever the bear-market AR price dictates.
• Arweave stores data permanently but cannot delete data — CSAM or legally problematic content uploaded to Arweave creates unresolvable censorship/legal risk for gateway operators. Gateways filter content; the underlying Arweave nodes typically serve everything.
• SPoRA and the blockweave design have not been formally peer-reviewed in academic venues to the same standard as Filecoin’s PoRep/PoSt.

---

Legacy

Arweave pioneered the one-time-payment permanent storage model and the permaweb concept. Bundlr (now Irys) built a scalable batching layer that made submitting millions of small transactions to Arweave practical. The protocol has found genuine product-market fit as a complement to IPFS (IPFS for content addressing; Arweave for persistence).

---

Related Terms

• IPFS Whitepaper
• Filecoin Whitepaper
• Proof of Work
• Data Availability

---

Research

• Williams, S., Jones, W., et al. (2019). The Arweave Yellow Paper. Arweave Foundation.

— Primary paper. Section 3 defines Proof of Access; Section 7 details the storage endowment economics.

• Benet, J. (2014). IPFS — Content Addressed, Versioned, P2P File System. Protocol Labs.

— Complementary storage protocol; Arweave and IPFS are frequently used together (IPFS CID + Arweave permanence).

• Nakamoto, S. (2008). Bitcoin: A Peer-to-Peer Electronic Cash System.

— Arweave’s blockweave is a structural modification of Nakamoto’s blockchain; the SPoRA consensus inherits PoW’s sybil resistance while adding storage obligation.