KleverChain IDE Extension for Visual Studio Code: Installation Guide

Hey everyone! How’s it going?

No, we haven’t updated anything. In fact, we’re holding off on updates during this hackathon.

I understand what you’re encountering. Rust has a naming convention for modules and packages to be in lowercase, and we built our SDK based on that standard.

So yes, as per the convention for any Rust project, our contracts also need to be in lowercase. I don’t see this as a bug or an issue, but I’ll add it to our list for future releases to ensure everything is automatically converted to lowercase.

@CryptoJaeger
If I understood correctly, you’ve found a solution and aren’t encountering any errors now, right? Do you need any further assistance?

@Bill_Butcher
Were you able to build your contract after CryptoJaeger’s discovery about everything needing to be in lowercase? Could you please recreate your contract using only lowercase and let me know if you encounter any other issues?

3 Likes

On my side all is fine now.

4 Likes

Yes, i managed to deploy it!

4 Likes

Looks like the link that i need is broken. @Duka

Look at “these steps” → link don´t forward to the correct site.

1 Like

Hello bro,

We’re updating the extension to fit with the new KVM update. We’ll take advantage of this to check it as well…

I keep u in the loop

TY

Is there a possibility that you could write the old instructions here?

I haven’t been able to continue all weekend.

Hello @CryptoJaeger!

Are you starting from a clean installation or reusing the last one you installed with us?

  • If you are reusing your previous installation, there’s no need to update yet. You can stay on v1.0.8 for now.
  • If this is a clean installation, you should be good to go by installing it directly from the marketplace. It will automatically prompt you to download the latest versions of KSC and KOperator. If it doesn’t, you can manually trigger the update by opening the Command Palette (View -> Command Palette) and typing “Setup Workspace”.

After installation, don’t forget to run these commands when starting a new project:

rustup override set nightly-2024-06-12
rustup target add wasm32-unknown-unknown

Additionally, make sure to update the wallet address in your extension settings when generating a new wallet. This ensures that the faucet functions properly.


:warning: Important!

Until we release the latest version of the IDE, deploying from the extension will fail.

Suggested workaround:
Manually deploy your generated WASM file using KleverScan:
:link: Create TransactionSmartContractOperation: Deploy

1 Like

Thank you. This was very helpfull. Contract deployed.

1 Like

Is there a newer version of https://sdk.kleverscan.org/kleverchain-sdk-web-umd-1-0-x.js available? With support of smart contracts?

@Duka @Nicollas @Maik

Hello @CryptoJaeger!

All JavaScript libraries have already been updated to support this type of operation.

From the URL you shared, it looks like you are referring to our sdk-web library (designed to interact with the Klever Extension). For this library, support is included in the latest release (v1.4.1).

Let me know if you need any further assistance!

1 Like

Only last question this week. On Kleverscan i miss the option to update the contract, I see only deploy and invoke.

Hello mate, yep the kleverscan has missed the update option. We’ll fix it, tks…

Since a ‘update’ is a invoke with the upgrade command, you can do it by operator as well. BTW we’re very close to release a new version of IDE extension.

1 Like

@CryptoJaeger done, the KleverChain IDE Extension V 1.0.10 has been updated Klever Blockchain IDE - Visual Studio Marketplace

Pls check it out and circle back to us.

3 Likes

For Windows users who get the following message when building their contract:

\target\debug\build\num-bigint-f2380d631b69af53\out/radix_bases.rs:

os error 123

I was able to solve it by creating an environment variable in windows:

Create a folder in your file system

For me as an example: D:\KLVOUT

Open the command line with administrator rights or use the terminal in VS code.

SET OUT_DIR=D:\KLVOUT
cargo clean
cargo build --target wasm32-unknown-unknown

This folder is not used but the error has disappeared, the build goes through.

Maybe someone can check this and possibly include it in the instructions @Duka

A post was split to a new topic: Smart Contract inconsistency


While working on a contract sample, I tried to create the PEM file, but I kept getting this error in the screenshot. The strange thing is that it worked before upgrading my VS Code, but now, it just pops an error. What can I do?

1 Like

Hello @dextonic !

It looks like the extension is not finding the executable that it downloads during installation.

If you were already using the extension before the latest update, there’s a chance that the update process reset your extension settings — this is rare, but it can happen.

:white_check_mark: Please check the following:

  1. Extension Settings

    • Open the Extensions tab in VSCode
    • Search for Klever Blockchain
    • Click on the :gear: Settings icon
    • Make sure the SDK path is correctly defined.
  2. Missing Executable

    • It’s also possible that the executable was lost or not downloaded properly.

    • You can redownload everything by opening the Command Palette (View -> Command Palette) and running:

      KleverChain: Setup Workspace
      

This command will trigger the full setup and re-download any required files.

Let me know if any of these steps fix the issue — I’m here to help! :rocket:

I suspect I was the one getting something wrong. I checked the video linked in the documentation. Yet I got a bit lost. In the screenshot that I am sending now, tell me what to fill in. I have filled in my wallet address, but it doesn’t work. I have also uninstalled and reinstalled it


still encountered the issue. Please send in the guide and let me try again.

The video linked in the documentation was created for Linux users, but it looks like you’re on Windows.
For Windows, we have a dedicated step-by-step guide available here:

:link: How to set up Klever Smart Contracts on Windows (via WSL)

This tutorial is very comprehensive — it covers:

  • How to install and configure WSL (Linux environment on Windows)
  • How to connect VSCode to your WSL environment
  • How to set up the Klever IDE extension
  • How to deploy a basic smart contract to verify that everything works

:camera_with_flash: About the screenshot you shared:

It looks like you are running VSCode directly in the Windows environment, not inside WSL.
This causes two main issues:

  1. Incorrect executable path:
    Your terminal is trying to access WSL, but the extension is still looking for files in a Windows path (C:/Users/...) instead of a Linux path (/home/...).

  2. Outdated executables:
    When running in Windows, the extension downloads a deprecated version of the tools.
    Once you follow the tutorial and run everything inside WSL, the extension will detect the correct environment and fetch the latest supported version.


Let me know once you’ve followed the tutorial, or if you’d like help with any of the steps! I’m happy to assist you :rocket:

1 Like

I was using the wsl terminal in the visual studio code. I would reset it and do it over.

1 Like