Put
This section introduces the overall process of data uploading to CESS network.
When you upload data to CESS, it is divided into fixed size segments, and then use the erasure coding technology (based on ReedSolomon) to obtain fixed size fragments. Finally, the fragments are distributed to storage nodes in the network.
Summary
To upload data to CESS network, you must perform the following steps:
Purchase storage space
Authorize the space usage rights to DeOSS
Create a bucket (if it has already been created, then ignore this step, or directly go to step 3 to automatically create a default bucket)
Upload data to DeOSS
Based on the returned Hash value, you can view the data status or download data
Upload process
The following figure shows the detailed data upload process, where metadata includes the client's calculated data size, data hash, segmented list, redundant list, owner's account, data bucket information, etc. The client issues storage orders on the chain, the chain network allocates storage nodes, and the client obtains the results processed by the chain network by listening to events, The result contains the storage nodes corresponding to each fragment, and the client needs to store all fragments in these storage nodes:
When uploading, users can choose whether to encrypt the data. If encryption is required, the user also needs to provide the encryption key. The SDK uses the key entered by the user for encryption, and the SDK does not keep the user key. Users need to keep the key properly, otherwise if the CESS network is lost, the data cannot be decrypted.
When the user receives the data hash, the data may not have yet been stored on the storage node in the CESS network yet. Only when the data status changes to ACTIVE, it means that the data has been successfully stored.
