Select Page
The Price of Permanence: Comparing Swarm and Arweave

The Price of Permanence: Comparing Swarm and Arweave

Storing data securely is essential for the decentralized internet. To meet this need, Arweave and Swarm both aim to provide a storage layer free from censorship, gatekeepers, and centralized control. Each system incentivizes node operators to store data reliably while keeping costs low enough to remain accessible, and high enough to keep the system self-sustaining. It’s a careful balancing act with different approaches. This article compares the basic economics, incentives, and long-term risks of both systems.

Let’s begin with a general comparison:

ArweaveSwarm
Payment modelOne-time, fixedTop-up balances via postage stamps
BlockchainArweave (native)Built on Ethereum (Gnosis Chain)
TokenARBZZ 
Token Atomic UnitWinstonPLUR
Risks/ AssumptionsKryder’s Law, AR token valueEthereum ecosystem, active nodes
Economics Proof-of-Work, Storage EndowmentRedistribution Game
Live Network HealthViewBlockSwarm Scan
Live Fees Arweave feesSwarm fees

Arweave offers a simple promise to users: “pay once, store forever.” The price paid when uploading a new piece of data guarantees storage for at least 200 years. There is only one transaction, and the time horizon is fixed for all users.

Swarm’s system is more flexible and adaptable. It allows users to choose how long their data stays available, based on how much they fund their storage. Uploaders purchase batches of postage stamps. A batch represents a quota (e.g. 20GB), which entitles the owner to issue and assign a postage stamp to a number of chunks needed to store that data. The batch also acts as a wallet from which the storage rent is automatically deducted. The balance decreases over time, and the data remains available until the funds run out.

Arweave’s Storage Endowment

“Arweave draws inspiration from Bitcoin’s proof-of-work structure for achieving consensus and adapts its implementation to incentivize the permanent storage of information within its network.” – Arweave lightpaper

Like Bitcoin, Arweave runs its own blockchain. Miners store and retrieve data for users as well as process transactions on the network. They are rewarded in native AR tokens, which are minted by network node operators and serve as block rewards. Also like Bitcoin, Arweave was designed with a hard cap on the total supply (66 million AR tokens).

When users upload data, they pay AR tokens into the storage endowment, a reserve that keeps miners incentivized even if block rewards fall short. To sustain this mechanism of permanent storage in exchange for a one-time transaction, Arweave relies on two key assumptions:

  1. Storage gets cheaper over time (Kryder’s Law)
  2. AR token value remains steady or increases
https://permaweb-journal.arweave.net/article/storage-endowment-explained.html

Assumption 1 is backed by an observation from the storage industry called Kryder’s Law. According to Kryder’s law, storage density tends to double —and cost per unit tends to halve—roughly every 18 months. Historically, this has translated to an average annual storage cost decline of around 38%. Uploading data locks AR into the endowment, effectively removing it from circulation, which puts pressure on the price of AR tokens to increase.
So far, thanks to both assumptions holding, Arweave’s tokenomics has worked out, and as a result “not a single token has left the endowment since launch nearly 7 years ago.” However, if AR’s value fell significantly or storage costs stopped declining, the endowment could struggle to maintain incentives, jeopardizing Arweave’s long-term promise.

Swarm’s Redistribution Game

“Swarm is a peer-to-peer network of nodes that collectively provide a decentralised storage and communication service. This system is economically self-sustaining due to a built-in incentive system which is enforced through smart contracts on the Ethereum blockchain and powered by the BZZ token.” –Swarm whitepaper

In Swarm, the batch balance functions similarly to Arweave’s storage reserve, while the redistribution game can be likened to Arweave’s block rewards, keeping storage providers incentivized. 

Users purchase postage stamps in bulk using BZZ (specifically, xBZZ on the Gnosis Chain). Individual stamps are attached to each data chunk uploaded to the DISC (Distributed Immutable Store of Chunks), Swarm’s underlying storage layer. 
The BZZ tokens collected from postage stamp sales are redistributed to groups of nodes called neighborhoods. In each round of the game, a random neighborhood is selected to receive the reward, incentivizing cooperation and agreement on stored content.

Interaction of smart contracts for swarm storage incentives. The figure shows with the dotted line the information flow between the four contracts comprising the storage incentive smart contract suite, as well as the public transaction types they accept (Source: The Book of Swarm)

The game is orchestrated by smart contracts. The batch also acts as a wallet, with storage rent deducted automatically based on the quota and the dynamic unit price set by the price oracle. The oracle adjusts the price of postage stamps based on supply and demand, specifically, how many nodes in the selected neighborhood are replicating chunks. If there are fewer than the target replication rate (of 4), the unit price increases; if more, it decreases. When exactly four attested replicas are present, the price remains stable. 

As rent increases, stamps expire faster and associated data is deleted; when rent decreases, data persists longer. For this storage incentive model to work, Swarm relies on key assumptions:

  1. The number of nodes in a neighbourhood that participate in the game correctly indicates the supply of storage (for the size of reserve, a particular fixed volume of chunks each node is supposed to store).
  2. Liquid supply of storage: node operators will respond to price signals in the sense that higher prices will attract more node operators to dedicate their disk space to the network, while decreasing price will discourage some operators to continue their service.

If storage prices fall over time (as assumed in Arweave’s model) or if BZZ value increases, a well-funded batch can effectively achieve “pay once, store forever”. However, Swarm doesn’t make this a formal guarantee—rather, it allows flexible configurations based on user preferences and market conditions.

Comparing Risks and Assumptions

Let’s review the risks and assumptions side by side:

  • Arweave depends on:
    • Kryder’s law continuing to drive down storage costs
    • A stable or rising AR token value

If both hold, the endowment can incentivize storage indefinitely.

  • Swarm relies on:
    • Accurate pricing via the price oracle and game participation
    • Elastic node supply reacting to incentives

The unit price of rent (denominated in BZZ per chunk per block) is determined by a price oracle at the time the rent is due, so users can’t pre-determine how long storage will last. 

But if the rent declines fast enough and the batch balance exceeds the finite sum of future rent, the balance will never deplete—effectively mimicking Arweave’s “store forever” outcome. Crucially, Swarm’s design allows users to set or adjust storage duration at any time. In this sense, Swarm’s economic model can subsume Arweave’s.

Conclusion

In essence, Arweave promises permanence via simplicity, locking in fixed assumptions at the protocol level. Swarm achieves resilience through adaptability, allowing price discovery and dynamic adjustments through market participation. For users, the choice boils down to:

  • Arweave: Set-it-and-forget-it storage, assuming macroeconomic stability. 
  • Swarm: Adjustable permanence through market-driven economics. 

Each has its strengths, and understanding their assumptions is key to deciding which is right for your data.

Understanding Decentralised Data Storage Costs on Ethereum Swarm

Understanding Decentralised Data Storage Costs on Ethereum Swarm

In the dynamic world of blockchain technology, Ethereum Swarm stands out as a cornerstone for decentralized data storage and communication. It’s crucial for users and developers in the Ethereum ecosystem to understand the intricacies of storage costs on this platform. This article delves deeper into the various factors affecting these costs, including network size, data size, and the critical role of BZZ tokens in pricing.

What is Ethereum Swarm

Ethereum Swarm is not just a decentralized storage system; it’s an extension of Ethereum‘s vision to build a comprehensive, decentralized internet. It enables data to be stored and distributed across a network of nodes, reducing reliance on centralized servers and mitigating risks like data loss or censorship. Swarm is designed to seamlessly store Ethereum’s dApp data, smart contracts, and user data, ensuring high availability and resistance to outages.

Factors Influencing Storage Costs

Network Size: The cost of data storage on Swarm is significantly influenced by the network’s size. A larger network means more nodes are available to store data, leading to increased redundancy and potentially lower costs due to economies of scale. In contrast, a smaller network might have higher costs due to increased demand for the limited storage space available.

Data Size: The volume of data being stored directly impacts the cost. Larger files require more space and network resources, naturally incurring higher costs. Smaller data sets, however, are less resource-intensive, making them more economical to store.

The Role of BZZ Tokens

BZZ tokens, Swarm’s native cryptocurrency, are fundamental to its operational model. These tokens facilitate transactions within the Swarm network, serving as a form of payment for storage services. Users pay for storage in BZZ, while node operators earn BZZ by providing storage space. This creates a decentralized market for storage, where prices are governed by supply and demand.

The Pricing Mechanism

Swarm’s pricing model is dynamic, adjusting to real-time conditions in the network. Storage costs are calculated based on several factors, including the amount of data, network congestion, and the availability of nodes. This ensures that the pricing is fair, competitive, and reflective of the network’s current state.

Swarm’s Postage Stamps Mechanism

An integral part of understanding data storage in Swarm is its unique “postage stamp” system. This mechanism is crucial for the functioning of the Swarm network and influences storage costs:

    • Concept of Postage Stamps: In Swarm, users must purchase “postage stamps” to upload and store data. These stamps are essentially proof of payment attached to the data being stored, ensuring that the data remains in the network for a predetermined amount of time.

    • Functioning: When a user wants to store data, they buy a postage stamp using BZZ tokens. The price of the stamp depends on the size of the data and the desired storage duration. The data with a valid postage stamp is then accepted and stored by the nodes in the network.

    • Impact on Storage Costs: The cost of postage stamps adds an additional layer to the overall storage costs on Swarm. It’s a pay-as-you-go model where the more data you store and the longer you want it stored, the more postage stamps you need to purchase.

Understanding Swarm’s Cost Per Gigabyte Per Year

Calculating the cost of storing data, such as a gigabyte for a year on Ethereum Swarm, requires an understanding of several dynamic factors:

    • Market Value of BZZ: Since storage costs are paid in BZZ tokens, the market value of BZZ significantly impacts the cost. As the value fluctuates, so does the cost of storage.

    • Network Demand and Supply: Costs vary depending on the balance between available storage space and the demand for storage. Higher demand or limited supply can drive up costs.

    • Data Redundancy and Replication: Swarm ensures data redundancy for reliability, which might affect the cost as more copies of the data are stored across different nodes.

Given these variables, providing an exact figure for the cost per gigabyte per year can be challenging. However, for illustrative purposes, let’s assume a scenario:

Assume that 1 BZZ equals X USD, – you can check the up to date prices here – and the current rate for storing 1 GB of data for a month is Y BZZ – check the up to date Swarm storage price here. Therefore, the cost to store 1 GB of data for a year would be (Y * 12) * X USD. At the time of writing, based on this calculation you’d pay $1.561 for storing one GB of data for a year on Swarm. It’s important to regularly check the latest rates and BZZ value for the most accurate cost estimation.

Comparisons with Other Storage Solutions

When compared to other decentralized storage systems like IPFS (InterPlanetary File System) and Filecoin, Swarm offers a distinct approach. While IPFS focuses on peer-to-peer file sharing and content addressing, Swarm provides more integrated storage solutions specifically designed for the Ethereum ecosystem. Filecoin, with its unique proof-of-storage model, represents another alternative, highlighting the diversity in decentralized storage solutions.

Future Outlook and Scalability

The future of Swarm is closely tied to the broader development of the Ethereum ecosystem. As Ethereum evolves, so too will Swarm, potentially leading to more efficient storage solutions and cost reductions. Key to this evolution will be improvements in scalability and network efficiency, which are expected to impact storage costs positively.

Conclusion

Grasping the nuances of storage costs on Ethereum Swarm is vital for anyone engaged in the Ethereum ecosystem. The cost is influenced by factors like network size, data volume, and the economic model governing BZZ tokens. As Swarm continues to grow and evolve, staying informed about these developments is crucial for developers and users alike.