Create Multi-Cloud Storage Allocation
Store your data on the Züs Multi-cloud storage servers.
This flow is triggered at your first login to Blimp, by choosing "Multi-Cloud Storage" or when you click the "Create New Allocation" button from the Multi-Cloud allocation section of the Manage Allocations page.
Step1: Configure the allocation
Tune the configuration of your allocation using the following configuration parameters
| Configuration | Description |
|---|---|
Allocation Name | A custom name you give to an allocation. |
Storage | How much storage space you need for your allocation. |
Duration | How long your allocation will remain valid. It's fixed at 1 year, which is what you pay for. You can extend this from the Allocation Management Page. |
Read Price Range | All reads are Free on Züs! 🚀 |
Write Price Range | This is the range of write price (in ZCN/GB/Month) within which you'd accept for the storage servers (blobbers) to charge your for storage. Each storage server offers a write price and you can use this range filter to narrow down the list of Blobbers that can host your allocation by their write price. |
Data Shards | This is the count of data shards involving in this allocation. Data shards count decides how many blobbers that the allocation data will be split among. |
Parity Shards | This is the count of parity shards involving in this allocation. Parity shards are replicas of the data shards that are used for data protection and fault tolerance. This count also decides how many blobbers will involve in carrying those parity shards. |
Select your desired configuration values and click "Confirm" in the right to move to the next step.
Step2: Choose your preferred blobbers
Here you can select the blobbers you prefer to host your data. Your allocation needs a number of blobbers equal to its: Data Shards + Parity Shards. You don't need to select all of them, just one blobber is enough, and the system will select the best blobbers to fill your allocation requirements.
In this step, you'll see a table with the available blobbers that fulfil your allocation write price requirements:
For each blobber, the table shows the following information:
| Column Name | Description |
|---|---|
Blobber | The Provider ID of the Blobber. You can use the copy icon next to it to copy it to your clipboard. If you clicked the Provider ID, you'll be redirected to the Blobber Details Page of this blobber. |
Host Name | The name assigned to the blobber deployment in Chimney, or the subdomain part of the blobber's host url if the name is not provided. When clicked, it also redirects to the Blobber Details Page of this blobber. You can use the ⇅ icon to sort the results based on this field. |
Allocated Storage | This column shows the allocated storage, along with a range slider showing how much of this allocated storage is used to host users' data. When hovered over, you can see the actual number representing the Used Storage. Allocated Storage, Used Storage as well as other storage-related terms are discussed in the Key Definitions page of the Storage System Feature documentation and in the Storage Explainer Page. |
Unallocated Storage | This column shows the unallocated storage, which is the amount of Staked Storage that is not used for allocations yet i.e. not Allocated. All storage terms are discussed in the Key Definition page of the Storage System Feature documentation and in the Storage Explainer Page. |
Unstaked Capacity | This column shows the unstaked capacity, which is the amount of the Blobbers Total Capacity that's not covered by staking tokens by the delegate clients. All storage terms are discussed in the Key Definition page of the Storage System Feature documentation and in the Storage Explainer Page. |
Passed Challenges | This column shows the count of challenges passed by the blobber. Challenges are means by which the system makes sure the blobbers are actually hosting the users' data correctly. They are generated by the blockchain and received by the blobber, which prepares response and submits them to the blockchain to verify, where it can be either successful i.e. counted as passed, or failed. More about challenges are discussed in the Challenges page. |
Quality Score | This column shows the Quality Score of the blobber, which indicates how the blobber is performing regarding the challenges. Quality Score is the percentage of the Passed Challenges to the total number of challenges generated for the blobber. You can use the ⇅ icon to sort the results based on this field. |
Staked ZCN | This column shows the amount of ZCN Tokens staked by clients to this blobber. More about staking in the Staking page of the Tokenomics System Feature documentation. You can use the ⇅ icon to sort the results based on this field. |
Write Price | This column shows the Write Price of the blobber, which is the ZCN amount the blobber charges the clients to perform write operations on their data. Write Price is expressed in ZCN/TB/Year, that's because it's deducted upfront from the client in the form of locked tokens to their allocations, which corresponds to the size the users request for their allocations. More about Write Price and other storage-related terms in the Key Definition page of the Storage System Feature documentation. |
Service Fee | This is the percentage that the blobber takes as cut of the rewards it receives, before splitting the rest of it among the delegates. More about Service Fee and other storage-related terms in the Key Definition page of the Storage System Feature documentation. |
Total Rewards | This is the total amount of rewards the blobber received from the challenges as well as hosting users data, expressed in ZCN. You can use the ⇅ icon to sort the results based on this field. |
Geo | This is the country and the region where the server hosting the blobber lies, according to the Host URL of the blobber's Chimney Deployment. |
To choose one of the blobbers as a preferred blobber for your allocation, you can click the "Add" button to the left of the blobber's row in the table. You'll then see your selected blobbers separated in another table:
After selecting your preferred blobber, click Confirm to proceed to the next step.
Step3: Lock tokens to the Write Pool
After configuring your allocation and choosing your preferred blobbers, you'll need to lock some tokens to your Write Pool to use them for your uploads. You'll be shown a popup window with the minimum amount of tokens you can lock:
Click Next to proceed to the next step and pay for your allocation.
Step4: Pay for your allocation
You'll need to get tokens to lock them into your Write Pool, as specified in the previous step. You can either get them by using ERC-20 tokens in your metamask wallet, or using your Bank Card (click for mote info about them). If you've ZCN tokens in your Züs wallet, you can use them instead of paying for new ones. You can use your existing balance by choosing "ERC-20 Tokens" then choosing "Pay from existing balance"
That's it 🎉 After you pay for the locked tokens, the allocation will be created for you, automatically activated on Blimp and you'll then be redirected to the File Management pages to manage the files within your allocation. You can manage your allocation on the Allocation Management Page, and also activate other allocations you have on Blimp.
Last updated
