At Klever, evolution always has one goal: turning ideas into products people can actually use. Our next new update brings a set of features built to help teams move faster, cut costs, and deliver smoother experiences.
Here’s what’s landing on launch day, and why it matters.
- Smart Contracts on Klever (KVM with Rust)
ㅤㅤ
- What it is: Our new smart contract engine, built for real-world apps. Based on Rust, it’s secure, efficient, and designed to make life easier for builders.
- Why it matters: Automate business logic right on-chain. Payments, memberships, games, marketplaces, and more, with predictable costs and stable performance.
- Who it’s for: Teams ready to go from prototype to production with speed and confidence.
ㅤ
- Semi-Fungible Tokens (SFTs)
ㅤㅤ
- What it is: Programmable assets that evolve over time. Picture a ticket that changes from pre-event → check-in → digital memory, or a game item that gains new attributes.
- Why it matters: Create dynamic user experiences without adding complexity. It’s not just collectible value, it’s product value.
ㅤ
- Klever Blockchain Extension for VS Code
ㅤㅤ
- What it is: An official VS Code extension with templates and guided steps to create, test, and deploy contracts directly inside the editor devs already love.
- Why it matters: Less time setting up. More time shipping.
ㅤ
- Ethereum Bridge (Smart Contract)
ㅤㅤ
- What it is: A two-way bridge between Ethereum and Klever. You can bring ERC-20 tokens into the Klever ecosystem and move them back to Ethereum whenever it makes sense for your project.
- Why it matters: You get Ethereum’s liquidity and community combined with Klever’s speed and lower costs. No lock-in. Just freedom to grow where your use case needs it.
ㅤ
- KDA Pool Deposit (Smart Contract)
ㅤ
- What it is: A contract that expands how KLV can be deposited into your app’s KDA Fee Pool. Today, only token owners or admins can top it up. With KDA Pool Deposit, you deploy the contract on KVM, link it to your pool, and from then on, partners, dApps, and even the community can contribute KLV.
- Why it matters: It keeps your pool supplied and your app frictionless. Users still pay fees in your token (KDA), while the network swaps them to KLV behind the scenes. More conversions, better retention, less hassle with network fees.
ㅤ
- KleverScan – Contracts Area
ㅤ
- What it is: A new section on KleverScan for contract visibility and verification.
- Why it matters: Transparency builds trust. Projects get a proper showcase, and users see clear, reliable information.
ㅤ
- A Faster, More Scalable Execution Layer
ㅤ
- What it is: Deep optimizations under the hood, making the execution layer more stable and responsive.
- Why it matters: Apps run smoother, with consistent performance and predictable costs over time.
ㅤ
What changes on Day 0
ㅤ
- For companies/products: Start mapping flows that will move to smart contracts. Think about where SFTs add value. Plan your ERC-20 bridge. Decide who signs critical approvals.
- For developers: Pick one simple use case from your backlog and get ready to launch. With the VS Code extension, you’ll move from zero to deployed in no time.
- For the community: Nothing changes until activation. From day one, you’ll notice faster apps, fewer fee headaches, and new experiences powered by the update.
ㅤ
Timeline and New Updates
ㅤ
We’re in the final stretch. The validator rollout is the bridge between code and mainnet, and the countdown is coming soon. Once the date is set, we’ll publish the full timeline.
Until then, stay tuned, we’ll keep sharing new updates, tutorials, examples, and step-by-step guides so you’re ready for day one of this new chapter.
