1. Important submission, modification and release
Blockchain Network
CESS testnet v0.5.3 consists of consensus nodes and storage nodes. Consensus nodes maintain the world state of the CESS network (by CESS Node) and are also "data authentication stations" (by TEE Workers) in the CESS network. Storage nodes are responsible for providing verifiable storage space and are "data storage pools" in the CESS network. The following is the progress of this month:
1. Consensus Node [v0.5.3]
- Unified the data structures, methods and events related to chain nodes and peer_id
- Added the lock cancellation behavior of the off-chain worker of the chain node, which is automatically triggered after the off-chain worker is executed.
- Fixed the bug of lock_time judgment error in chain node
- Fixed a bug found in the idle file authentication process of the chain node
- Fixed the signature logic of the chain node to prevent TEE Worker from colluding with the storage node to cause security issues
- Optimized the storage node selection mechanism and random number generation mechanism during the random challenge of chain nodes
- Completed the testing of chain node transaction query, node registration and other functions
- Refactored the TEE Worker code structure and transferred the network registration function in Kaleido to Rotator
- Fixed a security issue with batch authentication in Kaleido for TEE Workers
- Completed the interface implementation of Kaleido and Rotator of TEE Worker
- Optimized the code logic of the TEE Worker's Rotator initialization process
- Tested the aggregation proof and verification result on-chain function of TEE Worker
- Completed the p2p bootstrap node configuration for TEE Worker
- Fixed the issue where the p2p bootstrap node of TEE Worker could not automatically update the routing table
- Completed the development of the main code modules for node discovery and key exchange functions in TEE Worker
2. Storage Node [v0.5.3]
- Synchronously updated the data structures, methods and events related to peer_id
- Updated the interface between CESS bucket and TEE Worker, mainly to distinguish between idle data and service data when obtaining verification parameters
- Adjusted the subject of the CESS bucket signature, changing the original signature on the peer index to the signature on the peer id
- Implement the function of storage nodes listening to random challenges and actively pushing proof data to TEE Workers
- Fixed the issue where the CESS bucket verification aggregation proof failed
- Updated the CESS bucket startup command to support both foreground startup and background startup modes
- Fixed the issue that the program cannot be terminated and exited when the user enters the private key in CESS bucket
- Fixed the issue that the CESS bucket foreground startup command exits directly when incorrect data is entered, added friendly prompts and supported parameter default values
- Upgraded the CESS bucket command line operation function to improve the user experience
product
CESS aims to provide Web3 with feasible storage services and build a new generation of object storage service (DeOSS). The product ecosystem of the CESS network is becoming increasingly rich and prosperous, and has incubated innovative applications such as online file sharing tools (DeShare), public chain snapshot storage services, and CESS network disk. You are welcome to experience them. The following is the progress of this month:
1. Official website (cess.cloud)
- Completed the development of text hiding and display functions for long text blocks on each page
- Completed the display adaptation of some pages on mobile terminals
2. Object Storage Service (DeOSS)
- Added a series of network data synchronization and monitoring functions to go-sdk
- Cancel the constant configuration of token symbol and precision, and get them directly from the chain instead
- Added test files and test cases for go-sdk
3. Online file sharing tool (DeShare)
- Added RPC node automatic switching function
2. Discussion on technical solutions
The team successfully passed the third milestone of SBP
This marks the steady pace at which the team has completed all SBP milestones over the past 1.5 years. During this period, the project's code underwent significant improvements and optimizations, demonstrating the team's leaps in technical capabilities.
The team completed the discussion on the network idle space authentication speed upgrade plan
This paper discusses how to increase the storage capacity of the network more quickly to provide more storage space for users.
3. Technical Documentation Reference
GitHub: https://github.com/CESSProject
Wiki: https://github.com/CESSProject/cess/wiki
CIPs: https://github.com/CESSProject/CIPs