What's new in 2.5.0

In version 2.5.0, we've introduced several enhancements and additions to the SDK functionality:

1. New Functionality: We've added a new function called stopSignTransaction to the SDK interfaces. This function enables users to stop and cancel transactions that were initiated for signing by the SDK.
2. Enhanced error handling for quick transaction signing failures caused by invalid messages from the backend, such as schema changes in the message response from the backend.
3. We've addressed a few edge cases in the mpcKeyGeneration process that could potentially result in key generation failures. These improvements enhance the overall stability and reliability of the SDK.

What's new in 2.4.0

In version 2.4.0, we've expanded the capabilities of the NCW SDK to support Solana and Algorand, now including the EdDSA algorithm alongside our existing ECDSA support. This enhancement enables a single wallet to seamlessly interact with Bitcoin, various EVMs, and Solana.

More information about the supported NCW networks may be found here .

Additionally, we're excited to announce that support for more blockchains, including Stellar, is on the horizon. Stay tuned for further updates!

Upgrade guidelines

To successfully utilize the generateMPCKeys function with MPC_EDDSA_ED25519, it's essential that your workspace supports EdDSA. Learn more about supporting multiple algorithms within a single wallet here.

---

What's new in 2.3.0

In version 2.3.0, we made significant performance improvements in transaction signing.

For additional tips on enhancing overall performance, refer to our documentation here.

---

What's new in 2.2.8

In version 2.2.8, we made significant performance improvements in key generation and transactions.

For additional tips on enhancing overall performance, refer to our documentation here.

---

What's new in 2.2.5

In version 2.2.5, we have added the ability to work with multiple devices in a single wallet.

For more information about multiple devices, refer to our documentation here.

---

What's new in 2.1

In version 2.1, we added a safer backup and recovery mechanism.

Breaking change

Version 2.1 introduces a breaking change since the following two functions in the interface will receive different parameters:

• backupKeys
• recoverKeys

You can find details about the implementation in our android-ncw-demo repo and more information about the backup procedure here.

Upgrade guidelines

When upgrading to version 2.1 and later, you should require the user to run another backup procedure so that the new encrypted backup share on the Fireblocks servers will be associated with a passphraseId.