CESS is a blockchain powered decentralized storage and CD²N (content decentralized delivery network) infrastructure for Web3. Users and creators alike use the platform for on-chain data sharing, whilst builders can develop and deploy DApps.

Offering the most optimal Web3 solution for storing and retrieving high-frequency dynamic data, CESS reshapes the value distribution and circulation of data assets whilst ensuring data sovereignty and user privacy. By utilizing a decentralized physical infrastructure network (DePIN) model, CESS drives mass deployment of network nodes globally through incentives.

CESS network consists of four layers: Blockchain Layer, Distributed Storage Resource Layer, Distributed Content Delivery Layer, and Application Layer. CESS’s R²S consensus mechanism coordinates the network resources and network load, guarantees data security and integrity through proprietary technologies with data ownership protection, technologies such as Proof of Data Reduplication and Recovery (PoDR²), Multi-format Data Rights Confirmation (MDRC), and decentralized proxy re-encryption. CESS aims to be the first decentralized storage network that supports large-scale commercial applications.

CESS is also compatible with EVM and WASM, and the underlying development framework Substrate is also friendly to cross-chain applications. Its technology stack can support most Web3 applications and the development needs of enterprise-level applications.

Current testnet: v0.7.6 consists of consensus and storage nodes. Consensus nodes maintain the world state of the CESS network (by CESS Node) and serve as the “data authentication station” (by TEE Worker). Storage nodes provide verifiable storage space and serve as the “data storage pool” in the CESS network.

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

• Enhanced the territory module with lifecycle management and expiration checks.

• Updated the territory module readme documentation, adding descriptions for the functionalities and usage of RPC interfaces.

• Completed the benchmark writing and testing for the territory module.

• Generated and adapted transaction weights for the territory module functions.

• Optimized the territory module by refining condition checks for territory purchases.

• Resolved issues in the territory module where subsequent territory transactions failed due to users transferring account balances during the lock period.

• Fixed various code warnings and removed redundant logs from the territory module.

• Developed and tested the CD²N network caching node work reward protocol EVM smart contract.

• Improved the order mechanism for the CD²N network caching node work reward protocol, with automatic deletion of expired and claimed orders.

• Completed testing and merged the TEE Worker DCAP remote certification into the main branch.

• Addressed synchronization and verification issues with TEE Worker running in DACP remote certification mode.

• Completed the test run and issue resolution for the TEE Worker DCAP remote certification mode, resolving hardware upgrade limitations.

• Fixed issues where nodes were penalized for failing to submit storage proofs.

• Completed adaptation and testing of territory module-related functions.

• Enhanced the storage node monitoring program, adding monitoring and alert features for abnormal node statuses.

CESS is a blockchain powered decentralized storage and CD²N (content decentralized delivery network) infrastructure for Web3. By utilizing a DePIN (decentralized physical infrastructure network) model, CESS drives mass deployment of network nodes globally through incentives. The first of its kind, DeOSS (decentralized object storage services) by CESS has significantly contributed to the gradual enrichment and flourishing of the product ecosystem within the CESS network, DeShare (online file sharing tool), and public chain snapshot storage services have been incubated. The developments for this month are as follows:

• Resolved issues where DeOSS could not push user file fragments to storage nodes.

• Fixed problems with DeOSS failing to quickly download files due to caching module failures.

• Refactored the CD²N component library, clarifying the structure and logic of lightweight caching nodes for future upgrades and expansions.

• Improved the credit mechanism for lightweight cache clients, enabling easier collaboration with nearby cache nodes.

• Implemented a general interaction module for lightweight cache nodes and smart contracts, supporting future functionality expansions through various contracts.

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

• Upgraded the go-sdk and js-sdk to include all functionalities related to the territory module.

• Completed testing for DeOSS functionalities involving file uploads and downloads with the territory module.

• Updated user manuals to reflect the latest features and operating logic in DeOSS.

• Added support for “CANS PROTOCOL” for batch file uploads and downloads.

• Implemented file fragment and integrity verification functionalities in the js-sdk.

• Finished adapting the js-sdk for file resume upload functionality on the browser end.

• Fixed issues with file uploads failing due to load-balancing configuration errors.

• Corrected inaccurate user prompts when uploading files with illegal filenames.

• Added support for file-sharing link previews, allowing users to view basic file information without clicking the link.

• Implemented an offline backup mechanism for file metadata, enabling seamless data migration during testnet iterations.

• Completed development of new official website pages.

GitHub: https://github.com/CESSProject

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

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

CESS website | Twitter | Telegram | Discord | Github | Medium | LinkedIn | Instagram | YouTube | Facebook

CESS is a blockchain powered decentralized storage and CD²N (content decentralized delivery network) infrastructure for Web3. Users and creators alike use the platform for on-chain data sharing, whilst builders can develop and deploy DApps.

Offering the most optimal Web3 solution for storing and retrieving high-frequency dynamic data, CESS reshapes the value distribution and circulation of data assets whilst ensuring data sovereignty and user privacy. By utilizing a decentralized physical infrastructure network (DePIN) model, CESS drives mass deployment of network nodes globally through incentives.

CESS network consists of four layers: Blockchain Layer, Distributed Storage Resource Layer, Distributed Content Delivery Layer, and Application Layer. CESS’s R²S consensus mechanism coordinates the network resources and network load, guarantees data security and integrity through proprietary technologies with data ownership protection, technologies such as Proof of Data Reduplication and Recovery (PoDR²), Multi-format Data Rights Confirmation (MDRC), and decentralized proxy re-encryption. CESS aims to be the first decentralized storage network that supports large-scale commercial applications.

CESS is also compatible with EVM and WASM, and the underlying development framework Substrate is also friendly to cross-chain applications. Its technology stack can support most Web3 applications and the development needs of enterprise-level applications.

Current testnet: v0.7.6 consists of consensus and storage nodes. Consensus nodes maintain the world state of the CESS network (by CESS Node) and serve as the “data authentication station” (by TEE Worker). Storage nodes provide verifiable storage space and serve as the “data storage pool” in the CESS network.

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

• Enhanced the territory module with lifecycle management and expiration checks.

• Updated the territory module readme documentation, adding descriptions for the functionalities and usage of RPC interfaces.

• Completed the benchmark writing and testing for the territory module.

• Generated and adapted transaction weights for the territory module functions.

• Optimized the territory module by refining condition checks for territory purchases.

• Resolved issues in the territory module where subsequent territory transactions failed due to users transferring account balances during the lock period.

• Fixed various code warnings and removed redundant logs from the territory module.

• Developed and tested the CD²N network caching node work reward protocol EVM smart contract.

• Improved the order mechanism for the CD²N network caching node work reward protocol, with automatic deletion of expired and claimed orders.

• Completed testing and merged the TEE Worker DCAP remote certification into the main branch.

• Addressed synchronization and verification issues with TEE Worker running in DACP remote certification mode.

• Completed the test run and issue resolution for the TEE Worker DCAP remote certification mode, resolving hardware upgrade limitations.

• Fixed issues where nodes were penalized for failing to submit storage proofs.

• Completed adaptation and testing of territory module-related functions.

• Enhanced the storage node monitoring program, adding monitoring and alert features for abnormal node statuses.

CESS is a blockchain powered decentralized storage and CD²N (content decentralized delivery network) infrastructure for Web3. By utilizing a DePIN (decentralized physical infrastructure network) model, CESS drives mass deployment of network nodes globally through incentives. The first of its kind, DeOSS (decentralized object storage services) by CESS has significantly contributed to the gradual enrichment and flourishing of the product ecosystem within the CESS network, DeShare (online file sharing tool), and public chain snapshot storage services have been incubated. The developments for this month are as follows:

• Resolved issues where DeOSS could not push user file fragments to storage nodes.

• Fixed problems with DeOSS failing to quickly download files due to caching module failures.

• Refactored the CD²N component library, clarifying the structure and logic of lightweight caching nodes for future upgrades and expansions.

• Improved the credit mechanism for lightweight cache clients, enabling easier collaboration with nearby cache nodes.

• Implemented a general interaction module for lightweight cache nodes and smart contracts, supporting future functionality expansions through various contracts.

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

• Upgraded the go-sdk and js-sdk to include all functionalities related to the territory module.

• Completed testing for DeOSS functionalities involving file uploads and downloads with the territory module.

• Updated user manuals to reflect the latest features and operating logic in DeOSS.

• Added support for “CANS PROTOCOL” for batch file uploads and downloads.

• Implemented file fragment and integrity verification functionalities in the js-sdk.

• Finished adapting the js-sdk for file resume upload functionality on the browser end.

• Fixed issues with file uploads failing due to load-balancing configuration errors.

• Corrected inaccurate user prompts when uploading files with illegal filenames.

• Added support for file-sharing link previews, allowing users to view basic file information without clicking the link.

• Implemented an offline backup mechanism for file metadata, enabling seamless data migration during testnet iterations.

• Completed development of new official website pages.

GitHub: https://github.com/CESSProject

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

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

CESS website | Twitter | Telegram | Discord | Github | Medium | LinkedIn | Instagram | YouTube | Facebook