What It Is
Swarm stores data as chunks addressed by cryptographic hashes. A user uploads content through a Bee node, pays with postage batches, and the network distributes chunks to nodes whose overlay addresses are close to the chunk address.
Core concepts:
- Chunks. Fixed-size pieces addressed by hash.
- Manifests. Directory-like structures mapping paths to chunks.
- Postage batches. Prepaid stamps attached to chunks to signal storage payment.
- Bee. Reference Swarm node implementation.
- Neighborhoods. Overlay routing and storage based on proximity order.
Swarm's conceptual home is Ethereum's decentralized web stack: smart contracts on Ethereum, names through ENS, storage through Swarm, and wallets for identity/payment.
How It Works
file / directory
→ chunk into Swarm data chunks
→ build manifest
→ attach postage stamps
→ upload via Bee
→ retrieve by content hash or manifest path
The content hash gives integrity. The postage system gives the network a way to price storage. Retrieval can be done through local Bee nodes or gateways.
Swarm vs IPFS
| Property | Swarm | IPFS |
|---|---|---|
| Origin | Ethereum ecosystem | Protocol Labs |
| Addressing | Content hash | CID / multihash |
| Incentives | Built-in postage/stamps | External pinning or Filecoin |
| Client | Bee | Kubo, Helia, many clients |
| Best fit | Ethereum dapp assets | Broad content-addressed distribution |
| Ecosystem size | Smaller | Larger |
Swarm is more opinionated and Ethereum-native. IPFS has broader ecosystem gravity and more tooling.
Use Cases
- Static dapp frontends paired with ENS.
- Public assets for Ethereum applications.
- Signed manifests for web apps.
- Data blobs that should be content-addressed and paid for at upload time.
For large archival datasets, compare with IPFS and Filecoin and Arweave. For private backups, compare with Sia and Storj.
Trade-offs
Strengths
- Content addressing and manifest model are natural for dapp frontends.
- Ethereum-native payment and naming integrations.
- Postage model ties storage to explicit payment.
- Bee gives a self-hostable node path.
Limitations
- Smaller network and ecosystem than IPFS.
- Public data needs local encryption for privacy.
- Gateway UX can hide the trust model from casual users.
- Dapp developers often choose IPFS/Arweave because tooling is broader.
Attack Surface
| Attack | Mitigation |
|---|---|
| Gateway censorship | Use local Bee node or multiple gateways |
| Chunk loss | Monitor availability and re-upload/stamp as needed |
| Manifest hijack | Sign manifests or anchor roots in ENS / smart contracts |
| Plaintext exposure | Encrypt before upload |
| Economic underpayment | Use adequate postage and monitor retention |
Primary sources
Page history
- Updated
- 2026-10-25
- Origin
- Compiled from the ungovernable.tech research notes.
- Improve this page
- Suggest an edit — issues and pull requests are welcome.