CESS is a decentralized cloud storage network and CD²N network based on blockchain, supporting online data storage and real-time sharing, providing a full-stack solution for the storage and retrieval of high-frequency dynamic data in Web3.

The CESS data value network is built on the DePIN concept as a Layer 1 infrastructure, characterized by decentralization, efficiency, security, privacy, and scalability. CESS supports large-scale commercial storage and can accommodate phenomenal decentralized applications (dApps); CESS supports the monetization of data and the free flow/sharing of data value, while achieving user data privacy protection and data sovereignty returning to data owners in a trustless manner, thereby constructing a prosperous, diverse, and sovereign data asset economy new ecosystem.

Important Submissions, Modifications, and Releases

Blockchain Network

The CESS testnet version v0.7.6 consists of consensus nodes and storage nodes. Consensus nodes maintain the world state of the CESS network (by CESS Node) and serve as "data certification stations" (by TEE Worker) within the CESS network. Storage nodes are responsible for providing verifiable storage space and act as the "data storage pool" in the CESS network. Here are the updates for this month:

1. Consensus Node [v0.7.6]

• Fixed the issue where files could still be uploaded after the territory expired in the CESS Node territory module;

• Improved the CESS Node territory module, adding management for territory lifecycle and an expiration time check mechanism;

• Enhanced the readme documentation for the CESS Node territory module, supplementing descriptions of RPC interface functions and usage;

• Completed the writing and testing of benchmarks for the CESS Node territory module;

• Finished generating and adapting transaction weights for various functions of the CESS Node territory module;

• Optimized the CESS Node territory module, improving the condition detection mechanism when purchasing territory;

• Fixed the issue where subsequent territory transactions failed due to users transferring account balances during the lock-up period;

• Improved the CESS Node territory module, fixing some code warnings and removing invalid logs;

• Completed the development and testing of the EVM smart contract for the CDN network cache node work reward protocol;

• Enhanced the order mechanism of the CDN network cache node work reward protocol EVM smart contract, automatically deleting expired and claimed orders;

• Completed testing of TEE Worker DCAP remote authentication and merged the code into the main branch;

• Fixed the issue where TEE Worker could not synchronize and verify blocks after running DACP remote authentication mode;

• Completed the test run and issue fixes for the TEE Worker DCAP remote authentication mode, resolving the issue where nodes could not upgrade hardware configurations;

2. Storage Node [v0.7.10]

• Fixed the issue of being penalized due to the inability to submit storage proofs;

• Completed the adaptation and testing of functions related to the territory module;

• Improved the monitoring program for storage nodes, adding monitoring and alerting features for abnormal node statuses;

Products

CESS is committed to providing practical storage services and CD²N services for Web3, meeting large-scale commercial storage needs, and achieving millisecond-level data retrieval and return. CESS pioneered decentralized object storage services (DeOSS), and the product ecosystem of the CESS network is gradually becoming richer and more prosperous. It has currently incubated innovative applications such as online file sharing tools (DeShare), public chain snapshot storage services, and CESS cloud storage. We welcome you to experience them. Here are the updates for this month:

1. Object Storage Service (DeOSS)

• Fixed the issue where DeOSS could not push user file fragments to storage nodes;

• Fixed the issue where DeOSS could not quickly download files for users due to the failure of the caching module;

• Refactored the CDN component library to make the code structure and reference logic of lightweight cache nodes clearer;

• Improved the credit mechanism of the lightweight cache client, enabling it to establish stable cooperative relationships with nearby cache nodes more conveniently;

• Implemented a general interaction module between lightweight cache nodes and smart contracts, supporting subsequent functional extensions of cache nodes through various contracts;

• Improved the cache order mechanism, adding mutual condition checks between buyers and sellers of cache services;

• Upgraded go-sdk and JS-sdk, completing all adaptations related to the territory module;

• Completed testing of file upload and download functions after integrating DeOSS with the territory module;

• Updated the user operation manual to adapt to the latest version of DeOSS's functions and operation logic;

• Added support for uploading and downloading "canned protocol" (CANS PROTOCOL) file sets in go-sdk;

• Added file slicing and file integrity verification functions in JS-sdk;

• Completed the adaptation of the JS-sdk file breakpoint resume function on the browser side;

2. Online File Sharing Tool (DeShare)

• Fixed the issue where file uploads failed due to abnormal load balancing configuration;

• Fixed the issue of inaccurate prompts when uploading files with illegal filenames;

• Added support for file sharing link preview functionality, allowing users to view basic file information without clicking the link;

• Implemented an off-chain backup mechanism for file metadata, supporting seamless migration of data during testnet iterations;

3. Official Website (cess.cloud)

• Completed the development of the new official website pages;

Technical Documentation Reference

GitHub: https://github.com/CESSProject

GitBook: https://docs.cess.cloud/core/

CIPs: https://github.com/CESSProject/CIPs

White Paper v0.9.1: https://github.com/CESSProject/Whitepaper/blob/main/cess-whitepaper-v0.9.1.pdf