> For the complete documentation index, see [llms.txt](https://permawebdao-whitepaper.gitbook.io/permawebdao/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://permawebdao-whitepaper.gitbook.io/permawebdao/1.-market-background.md). # 1. Market Background Since its launch in 2017, Arweave has evolved naturally from a protocol focused solely on “permanent storage” into a long-term data infrastructure capable of supporting a full application ecosystem. At the protocol level, Arweave binds miner incentives directly to “historical data retention” through its Blockweave structure and Proof of Access mechanism, enabling uploaded data to remain available across cycles without requiring renewal fees. This pay-once, store-forevermodel differentiates Arweave fundamentally from time-metered decentralized storage networks and positions it uniquely for long-lifecycle use cases such as historical archives, compliance records, on-chain governance, and AI data. Additionally, Arweave’s endowment model injects future storage costs into the economic system upfront. As long as real-world storage costs continue to decline, the network can ensure long-term data availability under extremely low-risk assumptions. Arweave has therefore become the most time-resilient and predictable permanent data layer in the Web3 ecosystem, offering upper-layer applications a stable anchor that can survive multiple technology cycles. #### 1.1 From Tooling Protocol to Sustainable Network Benefiting from its unique economic and technical design, Arweave’s network has expanded continuously over the past two years. By the end of 2024, permanent on-chain data exceeded 10 billion records, with cumulative transactions entering the tens of billions. By late 2025, total network transactions surpassed 23.5 billion, corresponding to more than 334 TiB of permanent data, with on-chain addresses exceeding 300,000. As the Arweave permanent network matures, developers are increasingly migrating application frontends, media assets, indexing structures, and governance records onto Arweave, ensuring consistency and verifiability over longer time horizons. At the token level, AR’s fixed supply and transparent model create a pattern of “accumulative value.” As demand for permanent storage grows, Arweave gradually detaches from short-term storage market cycles and transitions toward long-term infrastructure valuation. With the launch of AO mainnet, Arweave is evolving from a pure data archive into an executable, parallelizable, orchestrable application infrastructure. AO enables on-chain AI models, agent systems, and high-throughput dApps to operate through a message-driven architecture. By the end of 2024, AO had processed over 800 million messages and is widely regarded as one of the most significant breakthroughs in the “AI × Crypto” execution layer. Meanwhile, Arweave’s permanent application toolchain continues to expand: frontend hosting, ArweaveKit, ArNS, AR.IO gateways, and a growing suite of financial and data protocols. These components are collectively transforming Arweave from a “storage protocol” into a “permanent application stack,” allowing developers to build applications designed to operate for 10+ years. On a macro scale, Arweave’s strategic importance continues to strengthen as global data creation accelerates. By the end of 2025, global data volume is expected to surpass 181 ZB. With rapidly expanding storage and verification needs, the broader DePIN sector will also grow substantially. As high-value datasets such as AI training data, financial history, governance records, and compliance archives increasingly demand “long-term availability, verifiability, and traceability,” Arweave is becoming the natural permanent settlement layer for these assets. It is also emerging as the default archival network for L2 rollups, cross-chain protocols, and infrastructure projects. #### 1.2 A Mature Ecosystem with a Missing Middle Layer Despite rapid improvements in Arweave’s storage and computation capabilities, the application layer still has several gaps: * No unified standard for data expression and structure * Limited composability between applications * Governance records, content assets, and indexing structures remain fragmented * Lack of a unified semantic layer to coordinate applications * Absence of a long-term, cross-application application framework Arweave already has the capability to host long-term applications, but it lacks the application-layer infrastructure that integrates storage, compute, access, execution, and composability. As AO matures, the permanent network expands, and developers seek more durable and trustworthy application frameworks, the need for a “permanent application network” has shifted from possibility to inevitability. Given Arweave’s technical maturity, ecosystem momentum, and macro trends, the network is entering a critical transition: from permanent storage layer to permanent application layer.\ The foundational capabilities exist, and the application-layer gap is clear—creating a rare window for building standardized, composable, long-term application infrastructure. This is the context in which PermawebDAO emerges. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://permawebdao-whitepaper.gitbook.io/permawebdao/1.-market-background.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.