# ADDITIONAL NARRATIVES ## Data Availability Swarm stands out as a Data Availability solution for Layer 2 rollup data, featuring a system where committed nodes are slashable through a proof of stake mechanism, and content availability is guaranteed by an on-chain attestation. Its network size underpins strong security, access and decentralization, while data integrity is assured through erasure coding and integrity proofs, providing a reliable, private and cost-efficient data availability solution. ## DePIN Swarm is a decentralized storage and communication system designed to offer a scalable and privacy-preserving platform for the decentralized web. It aims to provide the foundational infrastructure for a new generation of decentralized applications by offering features that align closely with the DePIN narrative: Decentralization & redundancy, Privacy, Scalability, Economic incentives and Interoperability. DePIN main narrative is that token growth does not come from speculation but from utility; there's no clearer utility than storage/hosting. Swarm provides a way to provide zero-cash-entry to different systems (users without ANY crypto could be able to 'earn' some [Book of Swarm, 3.2.4]) ## An Unburnable Digital Library *"The biggest problem with the Library of Alexandria is that it was burned down. We do not know who did it. We do not want the permanent record of Humankind to be taken by the devil, so it is important that the library is fireproof. If you look through the website of Filecoin, you will see that there is no mention of important features like permissionless publishing, information neutrality, plausible deniability (whether it is good or bad) and many other things related to fireproofing are missing."* It will allow blogs, newsrooms, NFTs, websites, to become as uncensorable as Bitcoin. ### Permisionless publishing The ability for anyone to publish or upload content to the network without requiring authorization, approval, or any form of centralized control. To be able to guarantee that uploading data is always available, and that data will be accessible afterwards, is a more sophisticated problem than initially was thought. Two set of economic incentives are needed: bandwidth and storage. https://hackernoon.com/storage-incentives-and-the-evolution-of-decentralization-an-interview-with-viktor-tron ### Plausible deniability The fact that it is the network, through kademlia routing, the responsible for deciding where to send the chunks ('pieces' of the file), represents a system where the nodes do not decide which chunks to store, and consecuently they cannot reconstruct any file they store. Yet, they are rewarded for providing storage. Therefore, nodes can convincingly deny the existence of specific data or information stored within them. This feature is especially relevant in situations where the presence of certain data could lead to legal, ethical, or security implications for the individuals or entities involved. All other solutions have a content policy, somewhere. This is not possible to enforce in Swarm. ### Upload and dissappear In Swarm, the concept of 'pinning' content, as seen in other networks, doesn't exist. Instead, an uploader can contribute content to the network and then disconnect their node from it, with no obligation to maintain a direct link to the content. The longevity of the content on the network can be supported by third parties who can purchase postage stamps for it. These postage stamps act as storage "credits," ensuring the content remains accessible and alive on the network as long as the "community" desires. ### Zero-leak messaging Untraceable messaging and file formats are designed to leak no metadata, ensuring ultra-private communications. This means utilizing private node communication to forge a pseudo-TOR network, enhancing privacy and security across the board. ### Hardware requirements Swarm stands out for having arguably the lowest node requirements in terms of CPU and disk space (20GB per node). This distinct advantage fosters greater decentralization and democratization of nodes, setting it apart in the field. However, this comes with a trade-off, as the network's performance and connectivity demand additional protocol effort. Particulary relevant for IoT devices, where CPU and storage is a constrain. Swarm Bee Client can be run in a Raspberry.