Provide a concise narrative that clearly states each of (a)–(e) below.
Arweave is a permanent, decentralized data storage network designed to address data impermanence, censorship, and centralized control over information. The protocol's stated founding motivation is the preservation of knowledge in a form that cannot be altered, deleted, or controlled by any single entity.
(Source: Motivation | Arweave Docs, Arweave Lightpaper)
Arweave operates a storage-first architecture in which miners store replicated data, prove access to historical blocks through Succinct Proofs of Random Access, quote upload pricing, and split transaction fees between active miners and a protocol-level storage endowment. Adjacent infrastructure — including gateways, bundlers, and the AO compute layer — handles data distribution, upload scaling, and higher-level compute and application interfaces. Ongoing development is conducted by Minimum Spanning Technologies Ltd., the UK-incorporated company behind the protocol.
(Source: Protocol | Arweave Docs, Arweave Yellow Paper)
Arweave is a global peer-to-peer network that permanently stores multiple replicated copies of uploaded data using a blockweave structure — a variant of blockchain in which each block links to both the previous block and a randomly selected prior block. Consensus is achieved through a mining mechanism combining Succinct Proofs of Random Access and a Verifiable Delay Function. Users pay an upfront storage fee that is deposited into the storage endowment, which then disburses rewards to miners over time to incentivize long-term data preservation.
(Source: Protocol | Arweave Docs, Arweave Yellow Paper)
AR is the network's native token. It functions as the unit of payment for data upload fees, miner compensation, contributions to the storage endowment, and balance transfers between network participants.
(Source: HTTP API | Arweave Docs, Arweave Yellow Paper)
Arweave does not operate a DAO or foundation-administered governance layer for routine parameter changes. Protocol evolution occurs through a fork-based social governance model in which miners and node operators signal adoption of software updates. Node operators exercise local discretion over content policies via their own Shepherd configurations or by loading a published content blacklist maintained by the ArweaveTeam GitHub account. The protocol's published governance principles describe protocol changes as requiring broad stakeholder consent rather than a standing tokenholder vote.
(Source: Fair Forks Paper, Principles of the Arweave Network, Transaction Blacklist | Arweave Docs)
For each existing entity: Labs/DevCo (e.g., Founder, CEO, CTO, COO), Foundation (e.g., President, Executive Director, CFO, COO), and DAO / onchain governance leadership (if applicable) list the: (a) full names, (b) official titles, (c) and prior experience of key team members. For any non-existent entity, explicitly mention it does not exist. External links may be included but they will not factor into the score.
Full Name | Entity | Official Title | Prior Experience |
|---|---|---|---|
Sam Williams | Labs | CEO and Co-Founder, Minimum Spanning Technologies Ltd. | PhD candidate in Computer Science, University of Kent (did not complete); Assistant Lecturer, University of Kent (2014–2017); developed the HydrOS distributed operating system; mentor at Techstars; technical advisor at Minespider; voting member at LAG Foundation |
William Jones | Labs | Co-Founder and CTO, Minimum Spanning Technologies Ltd. (July 2017–August 2018; departed) | PhD candidate in distributed systems and graph theory, University of Kent; AI and Machine Learning Lead at Embecosm from August 2019 |
Jesper Noehr | Labs | CTO | Founder and CEO of Bitbucket (acquired by Atlassian); founder of Upvest |
Sebastian Campos Groth | Labs | COO | Early-stage venture capital, business development, and project management background; co-author of official Arweave lightpaper |
Blockworks note: Arweave / Minimum Spanning Technologies Ltd. does not publish a formal executive directory on arweave.org. The following individuals are identified through official published papers, The Org, Crunchbase, and public reporting. |
Provide a structured description of the DAO's governance, powers, and economic rights. If a DAO does not exist, state so. Address the lettered items below. Even if there is no DAO, there must be an answer to (d).
The IP ownership of Arweave protocol code and the arweave.org brand is not publicly documented. Based on corporate records, Minimum Spanning Technologies Ltd. (company number 10889544, incorporated in England) is the most likely owner of protocol IP, but no public license filing or IP assignment document has been identified.
The project does not have a DAO executor or multisig governance layer with protocol-wide administrative powers. Node operators independently configure trusted peers for bootstrap connectivity, apply local content policies through Shepherd, and may load the ArweaveTeam NSFW blacklist. Protocol upgrade adoption occurs through software deployment and network-level miner consensus, not a standing admin authority. The arweave-standards GitHub repository serves as a public forum for standards discussion without binding governance authority.
(Source: Trusted Peers | Arweave Docs, Transaction Blacklist | Arweave Docs, GitHub — arweave-standards)
Not applicable. No AR locking or staking mechanism granting tokenholders additional governance rights exists at the protocol level.
AR tokenholders hold no formal claim to protocol revenue, treasury assets, or governance distributions. AR functions as the network's payment unit, with transaction fees directed to miners and the storage endowment. No DAO-governed revenue distribution mechanism exists.
(Source: HTTP API | Arweave Docs, Protocol | Arweave Docs)
Not applicable. The project does not operate a DAO legal wrapper with a documented dissolution mechanism.
Blockworks note: The Arweave protocol does not operate a DAO. There is no on-chain governance mechanism through which AR tokenholders vote on protocol parameters, treasury actions, or contract upgrades. The answers below reflect this structure.
For the Primary Foundation do the following independently. If an entity does not exist, state that explicitly. Items (a)–(f) apply only if that entity exists; state explicitly that the entity doesn't exist. Definitions: The primary Foundation and DevCo can be explained as those entities which are directly involved in the issuance of the native token at launch.
The project does not operate a primary foundation entity. No foundation was directly involved in the issuance of AR at launch or in subsequent token administration. Items (a) through (f) do not apply.
(Source: Arweave: Legal Policies, Arweave: Get Funded)
For the Primary DevCo do the following independently. If an entity does not exist, state that explicitly. Items (a)–(f) apply only if that entity exists; state explicitly that the entity doesn't exist. Definitions: The primary Foundation and DevCo can be explained as those entities which are directly involved in the issuance of the native token at launch.
The primary DevCo is Minimum Spanning Technologies Ltd., the UK-incorporated private limited company through which AR was issued and protocol development is conducted.
Minimum Spanning Technologies Ltd. is a private limited company incorporated in England and Wales on 28 July 2017 (company number 10889544). Its registered address is International House, London, EC3V 3NG, United Kingdom. The company operates under the trade name Arweave.
(Source: Companies House record via companyinformation.co.uk, Arweave: Legal Policies)
The specific IP assets owned or licensed by Minimum Spanning Technologies Ltd. — including the arweave.org codebase, brand trademarks, and protocol repositories — are not publicly documented in any filed IP assignment, trademark registration, or open-source license identified in public sources. The ArweaveTeam GitHub organization hosts protocol repositories but does not publish a governing IP ownership or license statement.
No DAO exists. Minimum Spanning Technologies Ltd. does not administer protocol-controlled treasury resources or reward parameters through any disclosed on-chain mechanism. The company issues grants and ecosystem funding directly from its operating resources, as evidenced by the Arweave Grants and Arweave Boost programs.
(Source: Arweave Medium — $8.3M Announcement)
Not applicable. No foundation entity exists.
No public disclosure identifies specific multisig keys, admin wallet addresses, or upgrade authority mechanisms held by Minimum Spanning Technologies Ltd. over the Arweave protocol. The company maintains the ArweaveTeam GitHub organization, through which official node software is published.
No governance-approved, contractual, or programmatic mechanism by which protocol fees or treasury assets are directed to Minimum Spanning Technologies Ltd. or its equityholders has been publicly disclosed. The storage endowment and mining reward distributions are protocol-level and not directed to the DevCo by design — however, any off-chain fee arrangements or equity dividend structures involving the company are not addressed in public sources.
Disclose launch and initial supply details in a single initial allocation schedule covering the token's launch.
55,000,000 AR were created in the genesis block at network launch on 8 June 2018. An additional 11,000,000 AR are introduced gradually as block mining rewards over time, establishing a hard maximum supply of 66,000,000 AR. The public record does not disclose a separate locked-versus-unlocked schedule for the genesis block tokens at launch. (Source: Arweave Yellow Paper, CoinMarketCap — Arweave)
The following allocation breakdown is sourced from CoinMarketCap's summary of publicly disclosed distribution data:
(Source: CoinMarketCap — Arweave, IQ.wiki — Arweave)
The public token sale conducted in June 2018 priced AR at $0.73 USD per token. The sale ran from 1 June 2018 to 6 June 2018, with a hard cap of $8.7 million. The ICO raised approximately $8.7 million. A pre-sale event in August 2017 preceded the public sales; the per-token price for that event is not publicly disclosed in sources reviewed here. (Source: CoinCodex — Arweave ICO, IQ.wiki — Arweave, businessmodelcanvastemplate.com — Arweave History)
AR (Source: Arweave Yellow Paper)
The maximum supply is 66,000,000 AR. The supply is effectively fixed at this ceiling. The 55,000,000 genesis tokens are fully issued. The remaining 11,000,000 AR enter circulation gradually as block mining rewards; as of 4 June 2026, circulating supply stands at approximately 65,652,466 AR. AR is not a deflationary token — no burn mechanism exists — but the storage endowment sequesters a portion of transaction fees from active circulation, releasing them to miners over time. (Source: Arweave Yellow Paper, KuCoin AR Price)
The team allocation (13% of initial supply) is subject to a five-year lock-up with 20% released annually. The future project use allocation (26.5% of initial supply) is subject to the same five-year lock-up structure with 20% released annually. No vesting terms for the pre-sale, private sale, public sale, or advisor allocations are disclosed in public sources reviewed here. (Source: CoinMarketCap — Arweave, IQ.wiki — Arweave)
Address each of the following sub-items based on the project's airdrop status. If a sub-item does not apply to the project's situation, state that explicitly.
No airdrop planned or conducted: Arweave has never conducted a token airdrop for AR and does not plan to execute one. The AR token distribution model consists of the genesis block allocation, pre-sale and public token sales, and gradual mining reward issuance. No airdrop recipient list, allocation methodology, or planned airdrop has been identified in public sources.
(Source: Arweave Yellow Paper, CoinMarketCap — Arweave)
Projects must disclose all material terms of market-making arrangements that affect token liquidity. If the project has no agreements or deals with market makers, state that explicitly; doing so earns full credit. For each market maker, include in a table:
If the project has no agreements or deals with market makers, state that explicitly; doing so earns full credit. If no native tokens were loaned or allocated to market makers, state that explicitly; cash/fiat retainers or fees are not required for this item.
Blockworks note: Minimum Spanning Technologies Ltd. has not publicly disclosed any market-making agreements involving AR token loans, call options, or retainer arrangements. No market maker agreement terms, counterparty names, or token loan amounts are identified in public sources.
Projects must disclose all material terms of centralized or decentralized exchange listings that affect token liquidity. For each listing, include in a table:
If the project has no agreements or deals with CEX or DEX, state that explicitly; doing so earns full credit; cash/fiat fee amounts are not required for this item.
Blockworks note: Minimum Spanning Technologies Ltd. has not publicly disclosed the material terms of any centralized or decentralized exchange listing agreements, including any token allocations for listing, listing fee payments in AR, or associated lockup or incentive programs.
Disclose all prior token sales by the Project — including fundraising rounds, any material OTC sales to investors, and any discounted market-maker sales. For each sale, provide:
If no prior sales occurred, state that explicitly (e.g., "No prior fundraising, OTC, or discounted MM sales have occurred.").
Blockworks note: The following equity and token fundraising events are identified in public sources. The specific legal instruments used (e.g., SAFT, SAFE, token warrant) are not publicly disclosed in sources reviewed here.
Amount raised and investors disclosed in the source table (no matching columns in this schema):
(Source: CoinMarketCap — Arweave, IQ.wiki — Arweave, CoinTelegraph — $5M Round, Arweave Medium — $8.3M, businessmodelcanvastemplate.com — Arweave History)
If any, list prior exploits or incidents that directly affected the token, token supply, tokenholder balances, token contract, minting controls, burn mechanics, or custody of token supply. This question is not asking about general protocol, application, or smart contract exploits unless the incident directly affected the native token itself. If no prior incidents, state this explicitly (e.g., "No exploits affecting tokenholders or protocol funds as of YYYY-MM-DD").
Blockworks note: No exploits affecting AR tokenholders or protocol funds have been identified in public sources as of 2026-06-17. The official Arweave release notes document software and operational incidents — including desync fixes, coordinated-mining failures, double-signing detection race conditions, and chunk-handling regressions — but the official release record states that no funds were at risk in connection with any of these incidents.
(Source: Arweave Release Notes N.2.9.5, Releases — ArweaveTeam/arweave — GitHub)
Describe material risk factors across the three categories below. Each category includes prompts to address at a minimum.
(a) Regulatory, Legal & Tax Risks — Describe how evolving laws and regulations could affect the project by answering, at a minimum, questions like:
Impact of Regulatory Change on TGE and Listings: (If applicable) How could evolving or conflicting laws and regulations affect your ability to complete the TGE, deliver tokens to purchasers, and list or maintain the token on trading venues in key jurisdictions?
Entity-Level Regulatory Impact: (If applicable) How could regulatory or legal changes impact your core entities (Foundation, DevCo, DAO, affiliated service providers), including enforcement actions, licensing requirements, or forced changes to structure or operations?
Tokenholder Tax Treatment: (If applicable) What uncertainties exist around how tokenholders may be taxed, and make clear that tokenholders are responsible for understanding their own tax obligations?
Jurisdictional & User Access Restrictions: (If applicable) If the project restricts access for certain jurisdictions or user types (e.g., U.S. persons, sanctioned countries, retail vs. professional), what are those restrictions and what risks do they create for users and for the project?
(b) Protocol, Technology & Security Risks — Describe risks to network and contract reliability, correctness, and safety by answering, at a minimum, questions like:
Bugs and Design Flaws: (If applicable) What bugs, design flaws, or implementation errors could exist in your core protocol code, smart contracts, and any bridges, rollups, or oracles that you depend on, and how could these lead to loss of funds or disruption of the protocol?
Security Measures & Their Limitations: (If applicable) What security measures have you taken (audits, formal verification, bug bounties), and what types of failures might these measures still fail to detect or prevent?
(c) Token Economics, Unlocks & Incentive Risks — Describe how the token's economic design and supply schedule could affect holders by answering, at a minimum, questions like:
Critical Economic Assumptions: (If applicable) Which economic assumptions (e.g., staking yields, fee revenue, liquidity incentives, MEV capture, demand for blockspace) are critical for protocol security, utility, and governance, and what happens if those assumptions fail?
Governance Control over Monetary Policy & Rewards: (If applicable) To what extent can governance change monetary policy, fee parameters, or reward allocations (e.g., inflation rate, treasury flows, incentive programs), and how could such changes adversely affect tokenholders?
(a) Impact of regulatory change on TGE and listings
Arweave completed its token generation event in July 2018. Future regulatory changes in key jurisdictions — including the United States, EU member states, and jurisdictions where AR is actively traded — could affect the ability of exchanges to continue listing AR or require Minimum Spanning Technologies Ltd. to alter how it describes or administers the protocol. The company has not publicly disclosed a jurisdiction-specific listing compliance strategy.
(Source: Arweave: Legal Policies)
(b) Entity-level regulatory impact
Minimum Spanning Technologies Ltd. operates arweave.org and processes user data under GDPR-oriented privacy policies. Evolving privacy regulation, consumer protection enforcement, or virtual asset service provider licensing requirements in the UK, EU, or other jurisdictions could affect the company's website operations, grant programs, and protocol development activities. The company has not publicly disclosed its approach to VASP compliance or any regulatory licensing it holds.
(Source: Arweave: Legal Policies, Privacy Policy | Arweave Docs)
(c) Tokenholder tax treatment
Arweave has not published guidance on the tax treatment of AR for tokenholders. Tax classification of AR — as property, a commodity, a security, or otherwise — varies by jurisdiction and is subject to change. Tokenholders are responsible for understanding and complying with their own applicable tax obligations.
(Source: Arweave: Legal Policies)
(d) Jurisdictional and user access restrictions
Arweave's legal materials require users to comply with applicable laws in their own jurisdictions when storing personal or confidential data on the network. No tokenholder jurisdiction-blocking matrix for AR purchases or transfers is disclosed in public sources. Users in jurisdictions where AR may be classified as a regulated financial instrument are responsible for determining whether their use of the protocol or token is permissible.
(Source: Arweave: Legal Policies)
(a) Bugs and design flaws
Arweave's technology risk surface encompasses mining-logic bugs, coordinated-mining failures, syncing stalls, VDF client issues, validation defects, desync conditions, and storage-replica handling regressions, all of which are documented in the official GitHub release notes. The protocol relies on trusted peer configurations, external or self-run VDF infrastructure, and optional local content blacklisting tools, meaning defects or misconfiguration across any of these layers can degrade service quality independently of any centralized admin function.
(Source: Releases — ArweaveTeam/arweave — GitHub, Trusted Peers | Arweave Docs, VDF | Arweave Docs)
(b) Security measures and their limitations
The Arweave protocol uses storage-oriented cryptography and RandomX-based data packing as core security mechanisms. The RandomX project has completed four independent security audits without identifying critical vulnerabilities. Despite these measures, official Arweave release notes document post-design implementation bugs and operational failures that required patches, confirming that audit coverage does not eliminate ongoing implementation risk.
(Source: Arweave Lightpaper, GitHub — tevador/RandomX, Releases — ArweaveTeam/arweave — GitHub)
(a) Critical economic assumptions
Arweave's token economics depend on sustained storage demand, continued miner participation under the fee-and-endowment incentive model, and the storage endowment retaining sufficient purchasing power as storage hardware costs evolve over time. The protocol's economic model explicitly relies on Kryder+-style declining storage cost assumptions to ensure the endowment can fund future miner payouts. If storage demand declines, miners exit the network, or storage cost trajectories diverge materially from model assumptions, the long-term economics supporting permanent data preservation could weaken.
(Source: Protocol | Arweave Docs, Arweave Yellow Paper)
(b) Governance control over monetary policy and rewards
No tokenholder voting mechanism exists for routine AR monetary policy changes. Protocol evolution — including any changes to block reward schedules, fee structures, or mining parameters — occurs through software forks and network-level adoption by miners and node operators. Material changes to the reward structure can arise from software evolution without a formal tokenholder approval process, and no supermajority threshold or veto mechanism constrains such changes.
(Source: Fair Forks Paper, Principles of the Arweave Network, Protocol | Arweave Docs)
This Token Transparency Filing is provided for general informational purposes only and does not verify or warrant the accuracy of individual answers.
