The Klever Blockchain ecosystem just took a massive leap forward. We are thrilled to announce that Smart Contract Source Code Submission and Validation is officially live on Mainnet!
This is a milestone we’ve been eager to deliver, and it changes the game for both developers building on Klever and the users interacting with their applications. KleverScan is no longer just a tool to track transactions, it is now a hub for open-source verification and trust.
Why This Matters: Transparency, Security, and Trust
Until today, interacting with a smart contract meant interacting with compiled bytecode. You knew what the contract did because you trusted the team behind it, but you couldn’t see the exact blueprint.
With source code validation, we are completely removing the guesswork:
-
For Developers: This is your badge of credibility. By validating your source code, you prove to the entire ecosystem exactly what your contract does under the hood. It eliminates the “black box” stigma and showcases your commitment to clean, secure engineering.
-
For Users & Investors: You no longer need to rely on blind trust. Anyone can now audit the exact Rust source code powering a contract directly on KleverScan, verifying that the logic matches the developer’s claims.
-
For the Ecosystem: Open-source verification drastically raises the security floor of the Klever Blockchain. It reduces the risk of malicious exploits, builds a more robust developer community, and aligns KleverScan with the highest standards of Web3 transparency.
Quick Technical Guide: How It Works
The validation process is straightforward, but it requires precision to succeed. Here is the workflow:
-
Deploy: Deploy your contract as usual via the KleverScan “Create Transaction” page, Klever Operator, or the IDE extension.
-
Submit: Navigate to your contract’s address page on KleverScan, head to the validation tab, and upload your source code.
-
Process: The system will compile and verify the code. This typically takes a few minutes, though it might take slightly longer during periods of high network traffic.
Essential Validation Guardrails (Keep These in Mind)
To make sure your validation goes through successfully on the first try, pay close attention to these engineering constraints:
-
Exact Version Matching: The KSC (Klever Smart Contract) version and the Rust version inputted during validation must be the exact same versions used during deployment. You can double-check these details in the
abifile generated during your contract build. (Real talk: We know manual input isn’t ideal, so we are already working on automating this version matching in a future update to make the flow completely frictionless!) -
File Size Limit: The
.ziparchive containing your contract source code must not exceed 1MB. Keep your project structure clean. -
No Local Dependencies: Your project’s
Cargo.tomlfiles cannot contain local file path dependencies. If you used sample contracts fromklever-vm-sdk-rsas a baseline, remember that they often usekscas a local dependency. You must resolve these to registry/remote dependencies, perform a contract upgrade on-chain if necessary, and then proceed with the validation.
The Verified Standard
Once validation is successful, your contract page on KleverScan will display a proud “Verified” badge, along with accessible tab for the Contract Source function. This makes your dApp instantly more professional and secure.
You can see a live example of a verified contract on the Testnet right here:
KleverScan Verified Contract Example (check the Contract Source tab)
Building the Future Together
This release is a direct reflection of our commitment to providing a world-class infrastructure for our developers and a safe, reliable environment for our users. True decentralization cannot exist without absolute transparency, and today we took a giant step toward that ideal.
This is just the beginning of a new era for KleverScan. We have a packed pipeline of features designed to enhance developer experience, tooling, and analytics coming very soon.
Thank you to our incredible community of builders for your continuous support, feedback, and dedication. Let’s keep building! 