> For the complete documentation index, see [llms.txt](https://docs.wesendit.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wesendit.io/en/wesendit-node-network/the-participants/storage-node.md). # Storage Node The nodes form the crucial foundation of the decentralized WeSendit network and provide storage space for uploaded files. They function as data storage, allowing users to securely and reliably store and access their files within the network. Each node provides 64 MB storage packets to meet the needs of various file sizes and types. The nodes are operated by node operators and meet the **minimum requirements**, including a stable round-the-clock internet connection and a minimum data transfer rate. Nodes actively participate in the network, offering their storage capacity for file transfer. They receive upload requests from the Node Balancer and securely store the uploaded files. The files are organized in special storage blocks and tagged with hashes to ensure data integrity. As network participants, nodes are subject to various evaluation criteria such as availability, response time/ping, and data transfer speed. These criteria are monitored and assessed by the Node Balancer to ensure that the nodes operate reliably and meet the network's requirements. Nodes in the WeSendit network are classified into various networks: **Checknet**, **Testnet** and **Mainnet**. In the Checknet, all nodes are registered, while the Testnet and Mainnet must meet stricter criteria to be classified as trustworthy and high-quality nodes. The nodes are responsible for securely storing uploaded files and responding to download requests. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.wesendit.io/en/wesendit-node-network/the-participants/storage-node.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.