Upgrade to the Latest Affinidi SDK Version for Improved Performance

Today, we are announcing the deprecation of support for Bloom Vault in the latest version of our Affinidi SDK.

This blog outlines the updates in the new versions of Affinidi stack and the required steps developers should take to avoid any disruptions in our SDK’s functionality.

What’s new in Affinidi SDK v6.0.4 and above?

At a glance, here’s what changes from Affinidi SDK v6.0.4 and above.

• Migrating from Bloom Vault to Affinidi Vault for improved performance
• Server-side search by credential Id
• Server-side search by credential types

Read on to know why we are migrating to Affinidi Vault, what’s in it for you, and what steps you must take.

What are we changing?

The earlier versions of Affinidi SDK (below v6) use Bloom Vault as the end-to-end provider-agnostic storage. Undoubtedly, this has helped our customers to securely store verifiable credentials when using Affinidi’s open-source SDK. But starting from Affinidi SDK v6.0.4, we are migrating from Bloom Vault to our in-house built Affinidi Vault.

Why are we changing it?

It is our goal at Affinidi to provide an easy-to-use, secure, reliable, and high-performing set of functionalities within our Affinidi SDK. As a part of our continuous performance improvement activities, the engineering team has identified a need to replace the Bloom Vault with something that provides better performance and more advanced functionality. Thus, we have implemented Affinidi Vault as a replacement for Bloom within our SDK.

If you’re wondering why, here’s a comparison chart of the performance of Bloom vault vs Affinidi vault.

Comparison of vault performance

As you can see, there is a huge time-saving by switching to the Affinidi Vault, and this is why we made the change.

Why should you upgrade?

If you are using the earlier Affinidi SDK versions (lower than v6), your application won’t support the Affinidi Vault, and hence we can’t migrate you out of the Bloom Vault.

From Affinidi SDK v6.0.4 onwards, we have introduced an automatic migration trigger to the Affinidi Vault and that is why we ask you to upgrade to that version or above. Otherwise, your credentials will never be migrated and will eventually be wiped from the Bloom vault.

Please note that this migration will NOT impact the SDK performance negatively. On the contrary, if you have more than 100 credentials in Bloom Vault, you’re sure to see a big jump in performance after the migration.

Action points for you

• Update your services to use Affinidi SDK v6.0.4 or above.
• Please pay attention to the changelog while upgrading the SDK version as some methods may be changed or deprecated.

How to upgrade to the latest version of Affinidi SDK?

Go to GitHub and upgrade to version v6.0.4 or above.

When you send your first API request to get all the credentials using the new SDK, our system will start the asynchronous migration of your data from Bloom to the Affinidi Vault. No more action is required from you.

Once the migration is complete, your services will automatically start using only Affinidi Vault for both the write and read operations.

What is the timeline for this upgrade?

Starting from 8th July 2022, we will block writes to the Bloom Vault. All users must update their services to use the Affinidi SDK v6.0.4 or above by then. From 25th July 2022, we will block both reads and writes to Bloom Vault and depreciate support for the same.

For further questions/doubts, reach out to us at developers@affinidi.com, or drop us a note on Discord.

Visit GitHub to download Affinidi SDK v6.0.4.