In-depth explanation of the latest major upgrade of KasBlocking: Rusty Kasp

Latest upgrade of KasBlocking: Rusty Kasp explained.

KasBlocking is undergoing a major update, with the entire KasBlocking code being rewritten in Rust. KOL frqncesco has written an analysis of the various aspects of this upgrade, covering the upgrade details as well as the changes and impacts it will cause.

This is not just a technological improvement, but a strategic upgrade aimed at improving functionality, efficiency, and user experience. The alpha version of Rusty-KasBlocking is now available for testing on both the mainnet and testnet. So far, everything has been going smoothly, with development progress proceeding as planned and the network running as expected. The beta version is expected to be released within 2-3 weeks.

KasBlocking developers are working hard on the following aspects: 1) automatic trimming of old block headers (which requires adapting to the complex data structures behind KasBlocking efficiency); 2) block sampling for difficulty adjustment; 3) IBD recovery, which eliminates the need to interrupt and restart the process if the initial synchronization is interrupted. Rusty-KasBlocking will be able to recover interrupted IBD processes, reducing synchronization time and network pressure; 4) improved API, allowing for JSON API requests in addition to GRPC. This includes developing APIs for specific purposes, such as for exchanges, developers, utilities, and more, to interact with the protocol.

How is Rusty-KasBlocking implemented? Rusty-KasBlocking was developed to improve block rates, which requires several changes to the consensus rules and thus requires a hard fork. What would be the process of implementing Rusty-KasBlocking? Alpha > 4BPS testnet (running for months); > 8BPS testnet > Repeatedly searching for the best point of BPS/blocksize and gradually introducing it into the mainnet.

Why Rusty-KasBlocking? The Rust implementation is expected to provide significant performance improvements over the current version of KasBlocking, making transactions faster and more reliable, reducing the likelihood of system crashes, and making the entire platform more secure against network threats. However, it should be noted that the KasBlocking team is committed to gradually introducing these improvements over time to properly test the network’s performance through incremental testing.