Hello, Klever Community.
We remain steadfast in our commitment to bi-weekly transparency regarding the planning, execution, and strategic direction of the Klever Blockchain.
As we have stated previously, the advancement of our planned 2026 roadmap features remains strictly suspended. Sprint 105 was executed with a total and unrestricted focus on network security, deep monitoring, and infrastructural robustness. This exact same focus is being applied to our current cycle, Sprint 106.
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.
Important Milestone Achieved: We are proud to announce that the most critical corrections identified by CertiK have already been successfully patched and are live in production.
Looking Ahead: We currently anticipate that we will dedicate one more sprint to significantly reduce the remaining effort directed at resolving the final audit findings. Consequently, in the subsequent sprints, we hope to gradually create the space to resume actions directed at realizing our 2026 roadmap. When that time comes, we will carefully analyze and communicate the impacts this extended security pivot has caused to the overall 2026 timeline, which will undoubtedly see changes.
CertiK has just sent us their feedback on our latest return. We are currently analyzing this feedback, and we expect to have updates regarding it in the planning phase of the next sprint. For Sprint 106, our primary objective is to launch the v1.7.21-RC3 release candidate, consolidating all fixes resolved up to this point.
Here is a transparent breakdown of what we delivered in Sprint 105, and the aggressive hardening we are executing right now in Sprint 106.
Epic 1: Core Infrastructure, Observability & Proxy V2
- Sprint 105 (Delivered): We achieved massive success in hardening our external-facing public infrastructure. The team successfully delivered a comprehensive package of stability and observability upgrades for the Proxy V2. We implemented stricter caching rules to prevent data crossing, established vital safeguards to prevent server overload under heavy query volume, and fortified our APIs against potential infrastructure leaks. We also successfully delivered the unified statistics dashboard, exposing real-time transaction counts and KLV volumes. While this was outside the core CertiK audit scope, it provides immense value and stability for users and developers interacting with our public APIs.
- Sprint 106 (Planned): We are taking a strict stance on prioritization. While further Proxy Mainnet updates are prepared, they are officially conditioned upon the successful delivery of our core protocol security tasks first.
Epic 2: Proof of Security Audit (The Core Focus)
- Sprint 105 (Delivered): The team successfully delivered multiple risk reduction patches.
- Sprint 106 (Planned): We are strictly focusing on clearing our in-review protocol queue. We are prioritizing the remaining medium and low-severity findings. Our sprint goal explicitly mandates that these specific fixes must be completed and evidenced before they are authorized for the next release candidate.
Epic 3: Improve Security & Vulnerability Defense
- Sprint 105 (Delivered): We successfully delivered a critical availability patch that ensures nodes remain stable during the bootstrap phase, preventing potential crashes during initial network synchronization.
- Sprint 106 (Planned): We are actively prioritizing a critical availability barrier regarding unauthenticated network requests. This is a mandatory safeguard for ensuring the stability of our node operators.
Epic 4: Ecosystem Tools & Releases
- Sprint 106 (Planned): Our primary integration milestone for this sprint is the
v1.7.21-RC3release candidate. To ensure maximum stability, our sprint goal explicitly mandates that this RC will only be cut if it contains the verified fixes mentioned above. We are placing quality and security gates ahead of arbitrary release dates.
Consolidated Closing: Our Commitment to You
Sprint 105 was highly successful in significantly hardening our public-facing APIs and proxy infrastructure, ensuring a more stable and reliable experience for all users. We also made vital progress on specific CertiK remediations.
For Sprint 106, our goal is exceptionally focused. We are dedicating our capacity to clearing the remaining in-review protocol queue, finalizing the authentication of transaction results, and implementing critical availability barriers. By strictly gating the v1.7.21-RC3 release upon the successful completion of these specific fixes, we are guaranteeing that our next rollout is secure, stable, and verified.
We will continue to prioritize the security and stability of the Klever network above all else.
Thank you for your unwavering trust, your understanding of these necessary security precautions, and for building alongside us.