Why CertifiK.io remains on AlgoSDK v2.11.0 for the time being

At CertifiK.io, we attach particular importance to the stability, reliability and security of the tools we use in our developments on the Algorand blockchain. With this in mind, we have decided, as of today – March 18, 2025 – to continue to favor branch 2 of the js-algorand-sdk library, and more specifically version 2.11.0, rather than migrating immediately to the recently introduced branch 3.

A thorough evaluation of branch 3

We carried out an internal audit and experimentation on AlgoSDK branch 3, in particular version 3.2.0, to assess its new features and potential for our projects. While this new iteration brings some interesting improvements – such as an overhaul of certain APIs, improved modularity and optimizations for developers – our analysis leads us to remain cautious. Indeed, although promising, branch 3 does not yet seem sufficiently mature to fully meet our requirements in terms of robustness and stability.

The reasons for our choice

Several factors have guided our decision to stay with version 2.11.0 for the time being :

  1. Proven stability : Branch 2, and in particular version 2.11.0, has a proven track record in production environments. It provides a solid, well-documented foundation, essential for guaranteeing continuity of our services and avoiding any unforeseen interruptions.
  2. Compatibility with our existing systems : Migrating to branch 3 would involve significant adjustments to our current codebase. The structural changes introduced in v3, while interesting in the long term, require an adaptation effort that we consider premature until the branch has reached sufficient maturity.
  3. Lack of hindsight on branch 3 : Despite the advances proposed, branch 3 is still new and has not benefited from as much feedback as branch 2. At CertifiK.io, we prefer to wait for the community and real-life use cases to validate its reliability before fully integrating it.
  4. Priority to security : As a player involved in mission-critical blockchain solutions, we can’t afford to take risks on versions that might still contain undetected bugs or unexpected behavior.

A forward-looking strategy

This does not mean that we are definitively rejecting Branch 3. On the contrary, we are closely monitoring its development and remain open to future adoption, once it has reached a level of stability and reliability comparable to that of Branch 2. Our teams are continuing to experiment in parallel, to prepare for a smooth transition when the time comes.

In the meantime, version 2.11.0 remains a safe bet for us, perfectly suited to our current needs and those of our users. It enables us to maintain a high level of quality in our developments, while continuing to explore the opportunities offered by future AlgoSDK updates.

Conclusion

At CertifiK.io, our priority is to provide reliable, high-performance solutions. Staying with AlgoSDK branch 2, and more specifically version 2.11.0, is a well-considered decision that reflects our commitment to stability and user satisfaction. We’ll be keeping a close eye on the progress of Branch 3, and will keep you informed of any developments in our strategy.

If you have any questions or wish to discuss this subject, please don’t hesitate to contact us!