Store for total protection.
Use Blimp to store on Züs for total protection and business uptime.
Use Blimp to store on Züs for total protection and business uptime.
The process of storing and retrieving a file on Züs involves four steps: creating an allocation, uploading a file by splitting it into fragments, distributing them to multiple servers, and downloading from enough servers to reconstruct the original file.
To get started, you can customize your data protection plan with the number of data and parity bobbers. You can further select your own storage providers (Blobbers), but can also ask the network to select randomly for you based on a preferred price and geolocation.
Once your offer is matched with a group of Blobbers, an allocation of storage is created for you to upload files to Züs.
As the file is uploaded, it is erasure encoded for redundancy and split up into fragments.
Your file fragments are then distributed out to multiple servers (Blobbers).
When you want your file, the fragments are brought back together again, reconstructing the file to its original form.
Design your uptime for higher performance, availability, content distribution, censorship resistance, and security to prevent downtime due to a breach, hack, server or network failure
You can add a storage provider anytime to increase redundancy and replace bad performing blobbers.
In the QoS protocol, the blockchain randomly challenges storage providers (blobbers) for proof of storage and performance. Blobbers earn rewards for passing challenges; failed challenges result in slashed stakes.