Arweave
A decentralized permanent storage protocol where data is stored once and guaranteed to persist indefinitely, funded by a one-time upfront payment.
Arweave was launched in 2018 by Sam Williams and William Jones, initially as 'Archain'. The mainnet launched in June 2018 with the AR token. The network reached over 100 TB of stored data by 2022 and became a preferred storage layer for NFT metadata (used by Solana NFT projects, Magic Eden, etc.) due to its permanence guarantees compared to IPFS.
The blockweave's random recall block requirement means that as the network grows, miners are incentivized to store not just recent data but the entire history. Pruning old data would reduce a miner's probability of being selected for block production.
The AR token has a fixed maximum supply of 66 million tokens. Mining rewards decrease over time as the endowment mechanism takes over as the primary payment source for miners.
Key risk: the economic model's 0.5% annual storage cost assumption. If Moore's Law-style storage cost declines plateau (e.g., if hard drive capacity improvements slow), the endowment runway shrinks. Arweave mitigates this by requiring miners to 'prove' storage of the entire dataset, making storage commitment economically binding.
graph LR
Center["Arweave"]:::main
Pre_blockchain["blockchain"]:::pre --> Center
click Pre_blockchain "/terms/blockchain"
Pre_cryptography["cryptography"]:::pre --> Center
click Pre_cryptography "/terms/cryptography"
Rel_ipfs["ipfs"]:::related -.-> Center
click Rel_ipfs "/terms/ipfs"
Rel_filecoin["filecoin"]:::related -.-> Center
click Rel_filecoin "/terms/filecoin"
classDef main fill:#7c3aed,stroke:#8b5cf6,stroke-width:2px,color:white,font-weight:bold,rx:5,ry:5;
classDef pre fill:#0f172a,stroke:#3b82f6,color:#94a3b8,rx:5,ry:5;
classDef child fill:#0f172a,stroke:#10b981,color:#94a3b8,rx:5,ry:5;
classDef related fill:#0f172a,stroke:#8b5cf6,stroke-dasharray: 5 5,color:#94a3b8,rx:5,ry:5;
linkStyle default stroke:#4b5563,stroke-width:2px;
🧒 Explain Like I'm 5
Imagine a library that promises to keep your book forever — not just for a few years. Instead of paying rent every month, you pay once when you drop the book off, and the library invests that money to pay its own bills for centuries. The trick is that the library pays librarians (miners) with some of that investment to prove they're actually keeping ALL the old books, not just the new ones.
🤓 Expert Deep Dive
Blockweave Architecture
Unlike a traditional blockchain where each block references only the previous block, Arweave's blockweave requires each new block to reference a randomly selected 'recall block' from the chain's history. Miners must prove they have stored the recall block's data to produce a valid new block. This creates an economic incentive to store historical data: miners who store more of the chain's history have a higher probability of being selected to mine the next block.
Consensus: SPoRA (Succinct Proofs of Random Access)
Arweave v2.6 introduced SPoRA, replacing the earlier Proof of Access (PoA) mechanism. SPoRA requires miners to perform hash computations over specific byte ranges of the stored data, making mining throughput directly proportional to storage capacity. This tightens the coupling between storage provision and block production, discouraging miners from faking storage.
Economic Model: The Storage Endowment
When a user uploads data, they pay an AR fee that is split: a portion goes to the miner who includes the transaction, and the remainder is deposited into a protocol-level 'endowment' pool. This pool is designed to pay out mining rewards indefinitely, calibrated on the assumption that storage hardware costs decline by ~0.5% per year (based on historical trends). If actual cost declines exceed this rate, the endowment surplus grows; if storage costs do not decline as modeled, the endowment may eventually be insufficient — the core economic risk of the permanence guarantee.
SmartWeave (Smart Contracts)
SmartWeave is Arweave's smart contract system, distinguished by 'lazy evaluation': contract state is not computed on-chain at transaction time but is computed client-side on demand by reading and replaying all contract interactions from the blockweave. This eliminates on-chain computational costs but requires clients to execute potentially large interaction histories locally. Warp Contracts (formerly RedStone) is the primary SmartWeave implementation used in production.
Permaweb & Ecosystem
- Permaweb: Web apps and content deployed to Arweave via their transaction IDs are permanently accessible through Arweave gateways (e.g., arweave.net). These apps cannot be taken down by a central authority.
- Bundlr (now Irys): A Layer 2 bundler service that batches thousands of Arweave transactions into a single on-chain transaction, dramatically reducing per-upload costs and enabling sub-second finality for uploads.
- ANS-104: The bundle data format standard used by Irys and other bundlers.
Comparison: Arweave vs. Filecoin vs. IPFS
| Property | Arweave | Filecoin | IPFS |
|---|---|---|---|
| Persistence model | One-time fee, permanent | Periodic renewal contracts | No built-in incentive |
| Deletion possible? | No (by design) | Yes (contract expiry) | Yes (unpinned) |
| Data addressing | Transaction ID / URL | CID | CID |
| Smart contracts | SmartWeave (lazy eval) | FVM (EVM-compatible) | None |
| Token | AR | FIL | None |
❓ Frequently Asked Questions
Is data stored on Arweave truly permanent?
By economic design, yes — the one-time fee funds an endowment based on the assumption that storage costs decline ~0.5%/year. However, this is a probabilistic economic guarantee, not a cryptographic certainty. If the cost decline assumption fails long-term, the endowment could be insufficient.
How does Arweave differ from IPFS?
IPFS is a content-addressed file system with no built-in storage incentive — data disappears if no node pins it. Arweave adds economic incentives (mining rewards tied to proving data storage) and a one-time fee endowment model that funds permanent persistence.
What is the permaweb?
The permaweb is the collection of permanently accessible web applications and content deployed on Arweave. Because transaction IDs are permanent and data cannot be deleted, any app or page deployed to Arweave remains accessible indefinitely through Arweave gateways.