The Klever Blockchain ecosystem is about to take a major step forward with the deployment of a new and more robust version of the Klever Virtual Machine (KVM). As part of this process, a scheduled maintenance for the Testnet environment will take place to ensure a smooth transition to the upgraded infrastructure.
Scheduled Maintenance Details
- Start Time: February 6, 2025, at 5 PM UTC
- Duration: 24 hours
- Expected Completion: February 7, 2025, at 5 PM UTC
- Impact: The entire testnet environment, including KleverScan.org, will be unavailable during this period.
- Notification: A maintenance notice will be displayed on the KleverScan homepage throughout the maintenance window.
This update follows crucial adjustments received from the certification body and marks a significant enhancement of the Klever Blockchain ecosystem.
Important Notice: Testnet Reset
As part of this update, the testnet will be fully reseted. This means that all existing projects, including tokens, smart contracts, nodes, addresses and funds will be erased. Developers and users will need to recreate their projects and wallets once the testnet is operational again. This reset is essential to align the environment with the latest improvements and ensure a stable and efficient deployment of the new KVM.
What’s New in the Core Module?
This update brings a comprehensive set of features, enhancements, and fixes to the core module of Klever Blockchain. Below is the full changelog:
New Features:
- Users can now estimate fees using a node API.
- Users can now send split royalties to unregistered addresses in Klever Blockchain.
- Users can now access the
userKDA
endpoint on the node. - Users can now use KLV and KFI as valid token identifiers in the virtual machine.
- Updating an asset owner will now also update the asset KDA pool owner.
- Operators can specify encoded files or WebAssembly (WASM).
- Deployment of multiple indirect smart contracts is now supported.
- Users can add transfer roles when creating or triggering an asset.
- Semi-Fungible Tokens (SFTs) can now be minted with an amount of 0.
- API now displays asset type and indicates if an asset has a KDA pool.
- Administrative functionalities for assets are now available via a designated admin address.
- Operators can now decode VM outputs.
- Users with the deposit role can now perform deposits on the KDA pool.
- A managed method is now available to retrieve SFT metadata in the VM.
Enhancements:
- More consistent behavior when updating contract code during contract calls.
- More accurate gas charging when inserting/removing keys on managed maps.
- Improved gas handling during contract deletions, including a new refund mechanism.
- Smart contract deletions now preserve account state and only remove contract code.
- Enhanced transaction integrity checks and size validation.
- More efficient gas usage; gas is now consumed only for transfers that have not been executed.
- Correct indexing of SFT attributes from smart contracts.
- More consistent return values from
IsOnCurveEC
function. - Enhanced configuration options and better logging for VM query gas limits.
- The total staked on a proposal will decrement when performing a KFI unfreeze.
- Improved validation for
BigFloatPow
function to handle exponent correctly. - Implementation of a maximum gas limit check for improved transaction validation.
- Optimization of transaction selection based on the block gas limit.
- Maximum transaction nonce difference allowance reduced to 100.
- Improved validation for
KDATransfer
transactions.
Bug Fixes:
- Prevents setting a smart contract as the sender in transactions, improving security.
- Handles cases where royalties are not specified without errors.
- Improved validation to prevent input errors in asset names.
- Corrected claim receipt asset IDs.
API & Public Access:
- Improved access restrictions to mitigate potential DoS attacks.
- Size limits introduced for raw transactions.
- More accurate gas calculations in
StorageContext
, particularly for unchanged values.
What’s New in the VM-SDK?
- Redesigned proxy feature for calling other smart contracts.
- Redesigned transaction creation feature.
- Lighter development environment with reduced usage of Rust macros.
- Ability to set asset attributes using built-in functions.
- Functionality to verify if an account has specific permissions.
- Ability to update account permissions.
- New function to retrieve metadata for semi-fungible tokens.
Why This Update Matters
The Klever Virtual Machine (KVM) is a game-changer for the Klever Blockchain ecosystem. It enables faster, more efficient execution of smart contracts and dApps while maintaining security and scalability. Key features include:
- Efficiency: Fast and cost-effective execution of smart contracts.
- Security: A highly secure environment for smart contract execution.
- Scalability: Designed to handle large-scale dApp deployment.
- Energy Efficiency: Utilizes a Secure Proof of Stake (SPoS) consensus for reduced energy consumption.
- Future-Ready Technology: Built with WebAssembly (WASM) for cutting-edge performance.
What’s Next?
Following this testnet update, the peripheral components of Klever Blockchain and KVM will receive updates throughout the next weeks. These updates will further solidify the foundation for the mainnet launch of KVM.
This is a crucial step towards bringing KVM to the mainnet. Now is the time for developers and the community to test, identify potential issues, and fine-tune the system to ensure a seamless launch.
We Need Your Feedback!
Your input is vital to the success of this update. We encourage you to test the new features, report any issues, and share your thoughts with us. Your feedback will help us refine and perfect the KVM before its mainnet debut—a historic milestone for the Klever Blockchain ecosystem.
Stay tuned, test, be part of this revolutionary journey and always Be Klever!