In October 2024, Everscale developers worked on the major update of the cells database, released new commands for querying blockchain data, and implemented multiple fixes to prevent possible loopholes in the node’s code. Read the details in our digest.
Database Structure
One major upgrade introduced a new, 6th version of the cells database, focusing on performance optimization, especially for Merkle proof generation, along with stability enhancements via minor patches and dependency upgrades. Overall, the new database version will improve the efficiency of blockchain data verification, providing smoother and faster access to blockchain data.
New Commands
In October 2024, the Evernode received two new commands: getblock and getaccountstate_byblock. The first one is intended to be another tool for querying blockchain history, as it allows for retrieving raw block data from the Everscale blockchain. Distinguishing between masterchain and shardchain blocks, this command ensures the correct block data is loaded and returned. The second command allows you to fetch the state of a specific account at the moment of issuing a specific masterblock.
Vulnerability Fixes
Another update was made to enhance the Everscale node’s security, reliability, and performance improvements, ultimately making it more resilient. Here is the full list of mitigated vulnerabilities:
- To ensure correct references to previous blocks, developers patched an issue in block proofs related to shard merges.
- Clippy warnings were resolved, improving code quality.
- Warnings identified during a security audit were fixed.
- For better accuracy and performance, developers fixed serialization caching for SMFT block status.
- To resolve another SMFT issue, the Remp Absent check reaction was disabled.
- Improved error handling and debugging after introducing severity levels for query validation.
- To prevent overloading, the logging frequency for cell database telemetry was reduced.