## 3 MuReQua Decentralized Storage and Security Engine (MuReQua DeSSE)
### Main Features of Downloading Component
Specifically, all file fragments are retrieved and subjected to specific procedures to accurately reconstruct their contents. Each fragment is decomposed, and all its parts are decoded using the AES-256 algorithm to ensure maximum data security. One of the fragment parts undergoes an additional phase of decoding the proprietary encryption, as detailed in point 4 of the uploading scheme. In this phase, the modified character is replaced with the original character at the position where it was altered during the upload. Subsequently, the resulting content is decoded again using AES-256 to ensure data integrity and security. Finally, the content is converted from the previously applied base to base 10, as described in point 3 of the uploading scheme, thus completing the process of data reconstruction and decoding. With reference to point 6 of the downloading scheme, once all base conversions for each fragment are completed, server 3 sends the contents of the original fragments directly to the client via server 1, concatenated in the correct sequence to reconstruct the original file. This process ensures that each fragment is positioned exactly in its original location, allowing the client to receive the file in its entirety and integrity. Consequently, the client can save the reconstructed file on their device, having access to the complete and accurate content of the original file. The network architecture extends itself beyond the central server, integrating an array of geographically dispersed local servers and storage servers. Local server 1, which is positioned remotely from the central server, is connected via a secure VPN channel utilizing OpenVPN technology. This setup not only secures data transmission but also preserves its integrity. Local server 1 serves as the communication hub, directly linking to local server 2 and the storage servers, all of which are situated within the same network to minimize the latency inherent to physical infrastructure constraints. This configuration ensures that only local server 1 requires an internet connection to communicate with the central server through the VPN, while local server 2 and the storage servers remain isolated from the global network. This strategic design reaffirms our commitment to the paramountcy of security and operational efficiency within the system. Now, let us present functional mapping in relation to the physical deployment. Additionally, we consider the logical architecture for uploading processes. Below, we present the logical architecture in Figure 5 for downloading. Figure 5 shows the logical architecture of the file download process. The process begins with the user clicking to download a file via a client. The client sends a download request and the file ID to the central server. The central server gathers the user's information and sends it to local server 1, which verifies the identity of the user making the request. If the verification is positive, local server 1 forwards the file information to local server 2. Local server 2 reads the first fragment of the file, decrypts it using a proprietary decryption system and additional decryptions, and then merges the contents of the fragments. After performing a base conversion of the data, the file is sent to the client for download by the user. This scheme illustrates a security system that employs multiple servers and steps of verification and decryption to ensure that only authorized users can download the files. From the elements presented in this section and its four subsections, we have been able to introduce our data storage and protection solution in its entirety. While focusing only on its most distinctive and innovative aspects, the solution presented here aspires to become a new benchmark for high-security data storage, being capable of withstanding future quantum attacks. The most noteworthy features of the solution can be identified primarily in its ability to:  
1. [label=()]
2. Fragment content randomly;
3.