Swarm primary sources
Reviewed: 2026-05-15 UTC
Core product framing
- https://www.ethswarm.org/
- Best concise official framing for Swarm as a decentralized storage-and-communication substrate for serverless, censorship-resistant applications.
- https://docs.ethswarm.org/
- Official docs landing page. Useful as the main index into Bee, incentives, developer tooling, and publishing features.
- https://raw.githubusercontent.com/ethersphere/bee/master/README.md
- Best short source for Bee’s role as the main node/client surface and for confirming that Bee is the practical building block of the network.
Upload-rights market and storage admission
- https://raw.githubusercontent.com/ethersphere/docs.github.io/master/docs/concepts/incentives/postage-stamps.md
- Most important source for the postage-stamp mechanism. Explains prepaid batches, time-decaying batch balances, immutable vs mutable batches, batch-depth utilization, and why upload rights are not just a flat storage fee.
- https://raw.githubusercontent.com/ethersphere/docs.github.io/master/docs/develop/upload-and-download.md
- Useful implementation-facing source showing that uploads always require a postage-stamp batch and that Bee / bee-js / swarm-cli are the normal operational entry points.
Storage incentives and price steering
- https://raw.githubusercontent.com/ethersphere/docs.github.io/master/docs/concepts/incentives/redistribution-game.md
- Best concise explanation of the neighborhood-based commit / reveal / claim reward game, stake-density weighting, and freeze penalties for dishonest participation.
- https://raw.githubusercontent.com/ethersphere/docs.github.io/master/docs/concepts/incentives/price-oracle.md
- Best concise explanation of the utilization signal and the explicit fourfold redundancy target that pushes Swarm away from static storage pricing.
- https://raw.githubusercontent.com/ethersphere/storage-incentives/master/README.md
- Best source for the deeper control-plane split across postage batches, staking, neighborhood eligibility, reserve commitments, truth-teller selection, reward payout, and onchain contract roles.
Mutable publishing and application-layer structure
- https://raw.githubusercontent.com/ethersphere/docs.github.io/master/docs/develop/tools-and-features/feeds.md
- Best source for Swarm feeds as the mutable-pointer layer above immutable chunks, including the Ethereum-address-plus-topic control surface and ENS-related publishing implications.
- https://raw.githubusercontent.com/ethersphere/docs.github.io/master/docs/develop/tools-and-features/manifests.md
- Best source for trie-based manifests, path routing, metadata, and why Swarm can act like a filesystem/website layer rather than only a raw chunk store.
Canonical long-form references
- https://www.ethswarm.org/swarm-whitepaper.pdf
- Official whitepaper PDF. Best canonical protocol paper to keep with the project entry.
- https://www.ethswarm.org/The-Book-of-Swarm.pdf
- Longer-form official reference. Especially useful for deeper details on feeds, chunk types, and incentive design beyond the lighter docs pages.
Main takeaways from this pass
- Swarm is worth keeping separate from IPFS, Filecoin, and Storacha because it combines content-addressed distribution with a distinct upload-rights market, a neighborhood-scoped reward game, and a mutable publishing layer.
- The key control-plane split is between Bee as the operational node/client surface, postage-stamp batches as upload admission, the redistribution game as storage-honesty verification and payout, and the price oracle as redundancy-targeting economic governance.
- The postage-stamp system is one of the strongest reasons to keep Swarm explicit in the corpus: batch depth, bucket utilization, TTL, immutable vs mutable batch behavior, and dynamic price updates make storage capacity and upload rights unusually legible.
- The redistribution-game materials matter because they show that storage incentives are not a generic mining reward. Neighborhood selection, commit/reveal timing, stake-density weighting, and freeze penalties define who can realistically earn storage income.
- Feeds and manifests matter because they show Swarm is not just a storage market. It also exposes a publishing and routing layer for updateable websites and application bundles.
- Good comparison targets after this pass: IPFS, Filecoin, Arweave, Storacha, Bubble Protocol, WNFS, and other systems where naming, persistence, upload admission, and mutable publishing are split across different layers.