> 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/master-node.md). # Master Node WeSendit MasterNodes are powerful and specialized nodes within the network that play a crucial role in file transfer. Their primary purpose is to ensure a fast and efficient upload process for users. When a user uploads a file, it is first sent to the WeSendit MasterNodes. Here, the file is compressed to optimize transmission time and storage requirements. The compression is performed using advanced algorithms to achieve the most efficient compression possible without data loss. This step helps to improve transmission speed while simultaneously reducing resource needs. After compression, the information (e.g., transfer/storage size and metadata) is passed on to the Node Balancer, which is responsible for further processing and distributing it to nodes in the network. Thus, the WeSendit MasterNodes serve as a central hub for the upload process and play a significant role in optimizing data transmission. By utilizing specialized MasterNodes, WeSendit ensures that the upload process is fast and reliable, regardless of the number of users and file size. The MasterNodes are designed to be powerful and highly available to guarantee a seamless user experience. Overall, the WeSendit MasterNodes are an essential component of the decentralized network, enabling fast and efficient file transfer while also ensuring the security and integrity of the data. Their performance and specialization significantly contribute to the smooth functioning of the WeSendit network. After encryption, each part of the file is tagged with a hash code. This code is then used by the indexer to track the location of each fragment within the entire WeSendit infrastructure, ensuring that the fragments can always be found and correctly assembled when the user wishes to retrieve the file at a later time. --- # 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/master-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.