When you upload your files to the swarm, they are split into 4kb chunks and then distributed to nodes in the network that are responsible for storing and serving these parts of your content. Each chunk has a postage stamp stuck to it which attaches a value in xBZZ to that chunk which you agree to burn when buying the batch of stamps. This signifies to storage nodes that this data is important, and supposed to be retained in the Distributable Immutable Store of Chunks (DISC).
To upload data to the swarm, you must perform the following steps:
- Fund your node's wallet with xBZZ.
- Purchase a batch of stamps with your xBZZ.
- Wait for the batch to propogate into the network.
- Upload your content, specifying the batch id so that Bee can attach stamps to your chunks.
- Download your content using your content's hash.
Purchasing Your Batch of Stamps
In order to upload your data to swarm, you must agree to burn (spend) some of your xBZZ to signify to storer and fowarder nodes that this content is valued. Before you proceed to the next step, you must buy stamps! See this guide on how to purchase an appropriate batch of stamps.
Once your Bee node is running, a HTTP API is enabled for you to interact with. The command line utility curl is a great way to interact with a Bee node's API.
First, let's check to see if the API is running as expected...
Ethereum Swarm Bee
Once running, a file can be uploaded by making an HTTP POST request to the
files endpoint of the Bee API.
Here, you must specify your Batch ID in the
Swarm-Postage-Batch-Id header as follows.
curl --data-binary "@bee.jpg" -H "Swarm-Postage-Batch-Id: 78a26be9b42317fe6f0cbea3e47cbd0cf34f533db4e9c91cf92be40eb2968264" http://localhost:1633/bzz
We may also pass the appropriate mime type in the
Content-Type header, and a file name to the
name query parameter so that the file will be correctly handled by web browsers and other applications.
curl --data-binary "@bee.jpg" -H "Swarm-Postage-Batch-Id: 78a26be9b42317fe6f0cbea3e47cbd0cf34f533db4e9c91cf92be40eb2968264" -H "Content-Type: image/jpg" http://localhost:1633/bzz
Data uploaded to the swarm is always public. In Swarm, sensitive files must be encrypted before uploading to ensure their contents always remains private.
When succesful, a JSON formatted response will be returned, containing a swarm reference or hash which is the address of the uploaded file, for example:
Keep this address safe, as we'll use it to retrieve our content later on.
In Swarm, every piece of data has a unique address which is a unique and reproducible cryptographic hash digest. If you upload the same file twice, you will always receive the same hash. This makes working with data in Swarm super secure!
If you are uploading a large file it is useful to track the status of your upload as it is processed into the network. To improve the user experience, learn how to follow the status of your upload.
Once your file has been completely synced with the network, you will be able to turn off your computer and other nodes will take over to serve the data for you!
Once your file is uploaded into the swarm, it can be retrieved with a simple HTTP GET request.
Substitute the hash in the last part of the URL with the reference to your own data.
curl -OJL http://localhost:1633/bzz/042d4fe94b946e2cb51196a8c136b8cc335156525bf1ad7e86356c2402291dd4/
You may even simply navigate to the URL in your browser:
To share files with someone who isn't running a Bee node yet, simply change the host in the link to be one of our public gateways. Send the link to your friends, and they will be able to download the file too!