docs: clarify full node hardware requirements - #835
Conversation
- have `node-types.md` as the single source of truth of requirements and others refer to that Signed-off-by: Yejin Kelly Joo <yejinkellyjoo@gmail.com>
- Document modest baseline requirements for all node modes - explain the added disk, bandwidth, blockchain, and CPU needs for full nodes and staking. Signed-off-by: Yejin Kelly Joo <yejinkellyjoo@gmail.com>
✅ Deploy Preview for test-twitter-preview-testing-3 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| For both anchor parameters, use the first 4 hex digits from your node's overlay address (which you can find from the `/addresses` endpoint). | ||
| For depth, use the current storage depth of your node from the `/status` endpoint (`storageRadius` value): |
There was a problem hiding this comment.
Would it make sense to recommend swarm-cli utility rchash command here?
| - **Internet**: High-speed and stable connection. | ||
| - **RPC endpoint**: A connection to Gnosis Chain (see [setting the blockchain RPC endpoint](./configuration.md#setting-blockchain-rpc-endpoint)). | ||
| - **xDAI**: Minimum 0.1 xDAI for Gnosis Chain gas fees. | ||
| - **xBZZ**: 1 xBZZ for the initial chequebook deployment. |
There was a problem hiding this comment.
Wrong terminology.
1 xBZZ for the initial chequebook deposit.
Deployment only needs xDAI.
Also, funding the chequebook with xBZZ is optional.
| If you intend to participate in the redistribution game to earn storage incentives, you should test your setup using [the `/rchash` endpoint](./bee-api.md#rchash) in order to ensure that your hardware is sufficient. Participation in the redistribution game requires a process with high computational and memory requirements, along with significant bandwidth usage. | ||
| :::info | ||
| Staking raises the CPU demand but not the memory demand. | ||
| Nodes selected for the redistribution game run the sampler process, which is CPU-bound and bandwidth-hungry; 4 cores are sufficient for it. |
There was a problem hiding this comment.
Is it really bandwidth hungry?
|
One caveat on the |
3 participants
What does this PR resolve? 🚀
Corrects the documented full node hardware requirements and removes framing that made running a full node sound more demanding than it is.
node-types.mdthe single source of truth for full node requirements.getting-started.mdandfaq.mdnow link to#full-node-specificationsinstead of carrying their own drifting copies.Details 📝
The three copies of the full node spec had drifted apart (30 GB SSD vs. 20–30 GB NVMe), and the FAQ copy was the only one listing the on-chain funding requirements. Both lists are now merged into
node-types.mdunder two groups — hardware, and blockchain/funding — so nothing was dropped in consolidation.The
:::warningabove the full node spec list became an:::infoplaced below it. It previously primed readers to expect heavy requirements before showing them numbers that are anything but; it is guidance about staking, not a hazard.Wording changes that followed from the corrected numbers:
staking.md— "resource intensive" → "CPU-intensive", with the 4-core figure and an explicit note that memory is not the constraint.bee-api.md—/rchashbenchmarks "your node's processor is fast enough" rather than "hardware is sufficient", since CPU is what it measures.node-types.md— dropped "requires more system resources" and "without the overhead of running a full node".getting-started.mdalso gains a## Requirementsparent heading, with software/hardware/network demoted beneath it — the FAQ's#requirementsanchor now points there. Some headings infaq.mdwere promoted from#####to###, which had been nested under a question rather than under a section.No pages were added, renamed, or deleted.
Verification
npm run build:checkpasses: 0 broken internal links, 0 broken links in the built HTML (7,731 checked), 0 external 404s. The new#full-node-specifications,#requirementsand#node-types-overviewanchors were confirmed present in the build output, and all inbound links to them resolve.The link checker also reports 16 stale external redirects, 7 unverifiable URLs and 6 llms.txt gaps. All are pre-existing on
masterand unrelated to these lines, so they are deliberately left for a separate link-maintenance PR.Checklist ✅
masterand resolved conflictsnpm run buildsucceedsnpm run check:links) where relevantstatic/llms.txtupdated if pages were added / renamed / deletedSwarmvsswarm, ..)git commit -s)