Hello, Klever Community.
We are continuing our bi-weekly commitment to absolute transparency regarding the planning, execution, and evolution of the Klever Blockchain.
As communicated in our previous update, the advancement of our planned 2026 roadmap features remains strictly suspended. We are maintaining a total and unrestricted focus on network security, deep monitoring, and infrastructural robustness. Our highest priority is ensuring the Klever network remains an impenetrable fortress, and we are directing all our actions to prevent any future vulnerabilities. We believe that in the coming sprints, as we solidify these security measures, we will gradually create the space to resume work on our roadmap.
Our collaboration with CertiK continues to be fundamental to this process. They are actively helping us expand our robustness, resolve deep-level findings, and proactively anticipate novel attack vectors in an environment of continuous, AI-coordinated threats. We are sparing no effort to build an ever stronger, more reliable, and robust network.
Here is a transparent breakdown of what we delivered in Sprint 101, and the critical adjustments and aggressive hardening we are executing right now in Sprint 102.
Important Pivot: Release v1.7.20-rc1 Suspended for a Mandatory Hard Fork
One of the primary goals of Sprint 101 was the release of v1.7.20-rc1. However, during the sprint, CertiK provided us with a new audit report containing critical findings that require a hard fork to properly patch.
The Pivot: We have officially decided to suspend the release of v1.7.20-rc1. Instead, we are incorporating the critical fixes from this new CertiK report to launch a final v1.7.20 version during Sprint 102. Because this version includes a hard fork, it will be a mandatory update for all validators, node operators, and exchanges.
Epic 1: Proof of Security Audit (The Core Focus)
-
Sprint 101 (Delivered): This was the primary focus of the sprint, resulting in the successful closure of 14 audit tickets. We successfully resolved the findings. This massive undertaking significantly reduces the risks.
-
Sprint 102 (Planned): This epic remains our heaviest workload, with 15 tickets planned. We are addressing deep-level CertiK findings. To ensure these fixes are ironclad, we are also heavily revising our End-to-End (E2E) testing protocols to specifically validate these new security flows.
Epic 2: Improve Security & Vulnerability Defense
-
Sprint 101 (Delivered): We achieved 100% completion of our planned security epic. Furthermore, we finalized our internal “attack plan” designed to rigorously test the transfer principle on kApps.
-
Sprint 102 (Planned): We are shifting from patching to proactive economic monitoring. This sprint, we are scheduling and executing automated systemic economic checks to detect any potential anomalies or duplications before they can affect supply, balances, or network trust.
Epic 3: Core Infrastructure & Maintenance
-
Sprint 101 (Delivered): We delivered significant operational reliability upgrades. We’ve deployed a new read-only
/network/economicsendpoint. This endpoint provides a live view of the supply and pending rewards, creating a reliable operational source for economic reconciliation. -
Sprint 102 (Planned): We are prioritizing the availability and integrity of the network. We are actively resolving critical bugs.
Epic 4: Ecosystem Tools (KleverScan, Klever Connect & Smart Contracts)
-
Sprint 101 (Delivered): We successfully released our Smart Contract Verification and Audit capabilities. To ensure maximum code traceability and reproducibility for developers, we also integrated
wasm-optversioning into the contract validation process. -
Sprint 102 (Planned): While security is paramount, we are maintaining a focus on user experience by continuing the deployment process for the Klever Connect Interactive Tutorial.
Consolidated Closing: Our Commitment to You
Sprint 101 delivered immense technical value, specifically in fortifying our protocol security and economic observability. However, the pivot to suspend the rc1 release in favor of a mandatory hard fork for v1.7.20 in Sprint 102 demonstrates our absolute commitment to security above all else.
The Klever network must be impenetrable. By dedicating Sprint 102 to finalizing the mandatory hard fork release, resolving the deepest CertiK findings, and revising our E2E testing protocols, we are building a foundation that can withstand the most sophisticated threats.
We will continue to operate with full transparency, keeping you informed of every pivot, every hard fork, and every necessary delay to our roadmap. Thank you for your continued trust and support.