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.2

In version 2.3.2, we have resolved a bug that occurred during transaction signing, leading to intermittent failures after a few transactions. The root cause was identified within the MPC process, where the SDK did not handle a specific use case that emerged during performance improvement efforts.

It's important to note that although a transaction may have failed initially, it was possible to retry the transaction signing with success on subsequent attempts.

What's new in 2.3.1

In version 2.3.1, we have addressed and resolved a potential race condition that could occur during the generateMPCKeys process. This fix ensures that the operation no longer fails due to the identified race condition.

What's new in 2.3.0

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

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

What's new in 2.2.0

In version 2.2.0, we 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 ios-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.