Arweave yellow paper

The five-minute read

One action, walked through

1. A user pays the fee and inserts data. The transaction's identifier is determined by the content.
2. The data is woven into the block structure so later recall challenges can point at it.
3. A miner who wants to produce a block fetches the recall block the protocol names and proves access.
4. The reward for that block comes from the protocol's issuance and from the endowment's rules, not from a renewal invoice to the original user.
5. A later reader who has the identifier can fetch the bytes from any node that still stores them, and check the hash.

The argument, unpacked

What has to be true

• The endowment's assumptions about storage-cost decline and interest are roughly right, or users accept the residual risk.
• Miners store enough of the weave that a random recall is available to honest producers.
• Readers can find a replica. Content addressing checks integrity once a replica is found. It does not search the earth.
• The data people pay to include is data they are willing to see persist.

What happened after the paper

Arweave launched from this design and became a common place for applications to pin data they wanted addressable for a long time. The endowment's performance against its own assumptions is an empirical question that should be reported as such. The yellow paper is the recall-and-endowment construction, not a guarantee letter.

What to check before you use the idea

• What does the endowment assume about the future price of storage?
• How is a miner required to show they still hold history?
• Who will serve a replica to a reader, and how is that different from the mining proof?
• Is 'permanent' being used as a marketing word or as a claim under these assumptions?

Terms

Recall block

A historical block a miner must access in order to produce a new block.

Endowment

The prepaid pool that is supposed to fund storage after the user has paid once.

Content address

An identifier computed from the bytes, so a different file cannot wear the same name.

Weave

The paper's structure of blocks and data, which recall challenges range over.

The problem the paper names

Ordinary storage deals expire. A link rots when whoever paid the invoice stops paying. Arweave's design asks a user to pay once, into an endowment, and asks miners to prove they are holding a randomly recalled piece of the global dataset.

What the design proposes

• A block includes a reference to a recall block. Mining requires access to that historical data.
• Content addressing means the identifier is a function of the bytes.
• The endowment is an economic object. Its adequacy is an assumption about future storage cost, and the paper has to be read that way.

How the mechanism is specified

• Wildfire, in the protocol's terms, is how nodes prefer peers who serve data. Replication is a social and economic outcome of that preference, not a certificate that every byte sits everywhere.
• A successful proof shows the miner could fetch the recall block. It does not show that every node holds every file.
• Permaweb applications sit on top of this dataset. They are not specified by the storage proof alone.

What this page does not treat as proven

• Pay-once storage is only as permanent as the endowment and the miner set. The paper does not repeal the cost of disks.
• The yellow paper version matters. Later updates change mechanics.
• This page does not describe token price.

Why a venture studio still reads it

When a venture says 'permanent record', Arweave is the design that at least names an endowment and a recall proof. Ask what happens if storage cost does not fall the way the endowment assumes. That question is the design review.