If you are new to the blockchain technology, taking our Introduction to Blockchain Technology self-paced course is highly recommended. Also, for a comprehensive coverage of blockchain development in Ethereum or mastering Solidity programming, taking our below self paced courses is highly recommended:
In our previous article (How to Run Ethereum IPFS Storage), we discussed how to run Ethereum IPFS storage.
In this article, we learn how to work with Ethereum Swarm storage.
We discussed Swarm in our previous article series,Deep Research on Ethereum, in the Decentralized data and content storagearticle. We learned that Swarm is a distributed storage platform and content distribution service, and the native base layer service of the Ethereum Web3 stack. We showed the use case for Swarm and the typical Ethereum DApp application architecture diagram for it. In this article, we will show you how to install Swarm and get started using Swarm for decentralized content storage.
Swarm is very similar to IPFS; it is made up of Ethereum as the storage layer based on the Ethereum web3 stack and supports the Ethereum Geth client. It connects to Ethereum blockchain and requires an Ethereum account. Nodes in the Swarm network use the bzz wire protocol, which is based on devp2p/rlpx as a transport protocol for communication among Ethereum nodes. devp2p/rlpx is a TCP-based transport protocol that's used for P2P communication among Ethereum nodes. RLPx carries encrypted messages belonging to one or more capabilities to send and receive packets. One of the primary objectives of Swarm is to allow DApps to efficiently store and share their data with the end user. Swarm is still under development and not fully operational.
The following diagram shows the Swarm distributed storage architecture:
Swarm has a distributed chunk store, which has the basic unit of storage with a fixed maximum size (currently,this is 4 KB). The chunk store is deterministically derived from its addressed content. When any kind of readable source, such as images, texts, or video records, is uploaded to Swarm, the Swarm API layer will chop this data into fixed-sized chunks. A unique cryptographic hash is generated for each chunk. The hashes of these chunks will be used to generate another unique hash of a new chunk. Currently, 128 hashes make up a new chunk. The content gets mapped to a chunk tree. This builds up a Merkle tree, and the root hash of the tree is the address that you use to retrieve the uploaded file.
This hierarchical Swarm hash construct allows chunk data within a unique hash, providing data integrity and allowing protected random access. When the chunk is damaged or has been tampered with, the tree can tell by just hashing it.
On top of the chunk Merkle trees, Swarm provides a crucial third layer: manifest files. The manifest defines a document collection for organizing content and defines a mapping between arbitrary paths and files. The metadata in the Swarm manifests are associated with the collection, files, and media mime type. Here is an example:
"hash": "4b3a73e43............. 048d",
"contentType": "text/html; charset=utf-8", "path": "index.html"
"hash": "69b0a42a9382........... 98Ta",
"contentType": "application/pdf", "path": "a.pdf"
The preceding manifest file specifies a document collection; each document defines its path, unique cryptographic hash, and content type. You can think of a manifest as a dictionary that provides a service for the user and tells them what the content is and where to find it. Swarm exposes the manifest API via the bzz URL scheme.
The Swarm node directly connects to the Ethereum network and has the cryptographic hash associated with their bzz-account address. The nodes pool provides a distributed storage and content distribution service.
The actual storage layer of Swarm supports both localstore and netstore, and they have the following properties:
In the concept of a distributed preimage archive adopted in Swarm, nodes that close to a chunk's address actually host the data, alongside providing information about its content. The access frequency of the chunks determines what the nodes are storing. When nodes reach a certain storage limit, the oldest unaccessed chunks will be purged.
In our next article (How to Install Ethereum Swarm Storage), we discuss how to install Ethereum Swarm storage.
This article is written in collaboration with Brian Wu who is a leading author of “Learn Ethereum: Build your own decentralized applications with Ethereum and smart contracts” book. He has written 7 books on blockchain development.
Here is the list of our free webinars that are highly recommended:
Here is the list of our 10 free self-paced courses that are highly recommended:
If you like to learn more about Hyperledger Fabric, Hyperledger Sawtooth, Ethereum or Corda, taking the following self-paced classes is highly recommended:
If you want to master Hyperledger Fabric, Ethereum or Corda, taking the following live classes is highly recommended:
If you like to learn more about blockchain technology and how it works, reading the following articles is highly recommended:
If you like to learn more about blockchain development in Ethereum with Solidity, reading the following articles and tutorials is highly recommended:
If you like to learn more about blockchain development with Hyperledger, reading the following articles and tutorials is highly recommended:
If you like to learn more about blockchain development on Corda , reading the following articles and tutorials is highly recommended:
If you like to learn more about blockchain development in other platforms, reading the following articles and tutorials is highly recommended:
We offer private custom tutoring classes both online and in DC, MD and VA for almost all of our courses or bootcamps. Give us a call or email us to discuss your needs.
$50 Limited OfferREGISTER NOW