Hello, Klever Community.
We are maintaining our commitment to bi-weekly transparency regarding the planning, execution, and strategic pivots of the Klever Blockchain.
As we communicated previously, the advancement of our planned 2026 roadmap features remains strictly suspended. Sprint 102 was executed with a total and unrestricted focus on network security, deep monitoring, and infrastructural robustness. This same unwavering focus is being applied to our current cycle, Sprint 103.
We are giving absolute priority to completing the remediation of the CertiK audit findings and protecting the stability of the blockchain before we expand any product fronts. All our actions are directed toward expanding the robustness and security of the network to prevent any future vulnerabilities. We believe that in approximately two more sprints, we will gradually create the space to resume the actions directed at realizing our 2026 roadmap. At that time, we will carefully analyze and communicate any impacts this security pivot has caused to the overall 2026 timeline.
Important Milestone Achieved: We are proud to announce that one of the primary goals of Sprint 102 was successfully met. The final version, v1.7.20, containing all the critical remediations developed to date, was successfully launched on July 20th.
Looking ahead to Sprint 103, we are planning the release of a new Release Candidate (RC). This RC will prioritize the most critical fixes first, paving the way for a subsequent final version that we believe will cover all CertiK findings identified to date.
CertiK continues to be fundamental in assisting us with this security work, helping us expand our robustness, and anticipating potential attack scenarios. We are sparing no effort to build an increasingly stronger, more reliable, and robust network in this era of continuous, AI-coordinated attacks.
Here is a transparent breakdown of what we delivered in Sprint 102, and the aggressive hardening we are executing right now in Sprint 103.
Epic 1: Proof of Security Audit (The Core Focus)
-
Sprint 102 (Delivered): This epic was the highest value driver of the sprint, successfully closing 18 security tickets. We delivered fixes that closed seven out of the eight high-priority tickets for the sprint, reducing risks that could have affected network availability, consensus determinism, and node integrity. Crucially, we implemented validations against future epoch block proposals, corrected execution timeouts, and resolved unmeasured memory consumption loops. Furthermore, the delivery of revised E2E testing ensures we can now systematically prove these corrections rather than just implement them.
-
Sprint 103 (Planned): This epic remains our dominant focus, representing 85.7% of the planned sprint volume. We are targeting on the remaining vulnerabilities. We are also working to reduce exposure regarding some misconfigurations. To ensure these code fixes translate to operational security, we are actively developing a comprehensive hardening guide specifically for node operators.
Epic 2: Improve Security & Vulnerability Defense
-
Sprint 102 (Delivered): While the bulk of the security work was within the audit epic, we successfully moved critical network connection safeguards into the final code review phase to mitigate potential resource exhaustion.
-
Sprint 103 (Planned): We are pushing those inbound network connection limits across the finish line. We are imposing strict parameters on direct communications and connection caps for our nodes.
Epic 3: Core Infrastructure & Maintenance
-
Sprint 102 (Delivered): We resolved a high-priority, high-impact operational issue regarding historical replay imports.
-
Sprint 103 (Planned): Alongside our release candidate preparations, we are executing necessary operational adjustments. This includes the planned removal of a specific wallet block related to previous hack remediations, which is pending final internal approvals and evidence of safeguard completions
Epic 4: Ecosystem Tools & Releases
-
Sprint 102 (Delivered): We successfully delivered the deployment of the Klever Connect interactive tutorial, aiming to reduce adoption barriers for developers. Most importantly, we successfully delivered and launched the
v1.7.20release. -
Sprint 103 (Planned): Our primary integration milestone for this sprint is the
v1.7.21Release Candidate. This RC will consolidate our prioritized remediations and undergo rigorous testing before a final mainnet release is authorized.
Consolidated Closing: Our Commitment to You
Sprint 102 was highly effective in mitigating rapid, relevant risks, culminating in the successful launch of v1.7.20.
However, our work is not done. Sprint 103 is designed to finalize the remaining CertiK remediations, focusing heavily on consensus integrity and node availability. By prioritizing the v1.7.21 RC, we are ensuring that these critical fixes are thoroughly tested and verified before final deployment.
We will continue to prioritize the security and stability of the Klever network above all else. We anticipate that as we close these remaining security loops over the next two sprints, we will be in a position to re-evaluate and communicate our path forward for the 2026 roadmap.
Thank you for your unwavering trust and for building alongside us.