# Builder Vault Upgrade Guide

We will officially end our support for our previous long-term release, Builder Vault v62 LTS, at 2026-02-24. Therefore, we recommend that you upgrade to our most recent LTS version, Builder Vault v70 LTS. Builder Vault v70 LTS will be officially supported with bug fixes and other patches until at least 2027-03-14.

This page guides you through the necessary steps for upgrading Builder Vault from v62 LTS to v70 LTS.

### Note

The Builder Vault SDKv1 has entered maintenance mode. It will still be available in v70 and will receive patch updates until 2027-03-14. However, it will no longer receive feature upgrades and will not be included in Builder Vault versions following v70. If you use SDKv1, we recommend that you [upgrade to SDKv2](https://builder-vault-tsm.docs.blockdaemon.com/docs/upgrading-from-62-lts-70-lts#upgrading-from-the-legacy-sdk).

## New Features

Upgrading Builder Vault from v62 to v70 brings a number of bug fixes, enhancements, and new features. Some highlights are listed here:

- Support for [AWS Secrets Manager](https://builder-vault-tsm.docs.blockdaemon.com/docs/external-values#aws-secrets-manager)
- Support for dynamic [IAM RDS authentication](https://builder-vault-tsm.docs.blockdaemon.com/docs/external-values#iam-database-authentication)
- New curve for ECDSA signatures as used by [Starknet](https://builder-vault-tsm.docs.blockdaemon.com/docs/blockchain-starknet)
- New Schnorr signature schemes supporting [Mina](https://builder-vault-tsm.docs.blockdaemon.com/docs/blockchain-mina), [Zilliqa](https://builder-vault-tsm.docs.blockdaemon.com/docs/blockchain-zilliqa), and [Polkadot](https://builder-vault-tsm.docs.blockdaemon.com/docs/blockchain-polkadot) (sr25519)
- Support for [OCSP validation](https://builder-vault-tsm.docs.blockdaemon.com/docs/access-token#authentication-with-client-certificates-mtls)
- A re-worked [PKCS#11 integration](https://builder-vault-tsm.docs.blockdaemon.com/docs/pkcs11)
- Node-to-node communication via [Redis](https://builder-vault-tsm.docs.blockdaemon.com/docs/message-broker-communication#redis) and enhanced [load-balancing using AMQP and Redis](https://builder-vault-tsm.docs.blockdaemon.com/docs/horizontal-scaling#replicated-mpc-nodes-with-message-broker-communication)
- New flexible [KeyCopy](https://builder-vault-tsm.docs.blockdaemon.com/docs/key-lifecycle-management#key-copy) operation
- Our new SDK is now also available in [Web Assembly (WASM)](doc:doc:web-assembly-sdk)
- The MPC nodes now support the [DKLS23](https://builder-vault-tsm.docs.blockdaemon.com/docs/mpc-protocols#dkls23) MPC protocol for ECDSA signatures.
- Ability to choose [hashing algorithms for API keys](https://builder-vault-tsm.docs.blockdaemon.com/docs/access-token#authentication-with-api-keys): MD5, SHA256, SHA512, bcrypt, Argon2i, Argon2id
- [RSA](https://builder-vault-tsm.docs.blockdaemon.com/docs/rsa), [AES](https://builder-vault-tsm.docs.blockdaemon.com/docs/aes), and [HMAC](https://builder-vault-tsm.docs.blockdaemon.com/docs/hmac) operations are now available in our SDK.
- A new [demo repository](https://gitlab.com/Blockdaemon/tsm-demo) with a collection of Builder Vault configurations and code examples.

## Upgrading Builder Vault

Builder Vault (BV) has several APIs that are versioned separately as described [here](https://builder-vault-tsm.docs.blockdaemon.com/docs/versioning). The table below shows each of these for BV v62 and BV v70, respectively.

| API | Description | BV v62.0 | BV v70.0 |
| --- | --- | --- | --- |
| Client API | The programmatic interface to the SDK. | 51.1 | 60.2 |
| Client Communication | The communication protocol between the SDK and the MPC node that it controls. | 27.0 | 29.2 |
| Database | The interface between an MPC node and its local database | 7.8 | 7.12 |
| Node Communication | Communications protocol between two MPC nodes | 31.0 | 34.0 |
| Node Configuration | The version of the configuration file of an MPC node | 18.1 | 21.4 |

## Upgrading the MPC Nodes

Upgrading brings the node communication protocol from v31 to v34. This includes breaking changes relating to the AES, HMAC, AN10922, and RFC5649 protocols. If you use any of these operations, upgrade all your MPC nodes simultaneously. If not, you can upgrade one MPC node at a time.

### Database

The MPC node database version will go from v7.8 to v7.12. Database upgrades are automatic when the first MPC node v70 is started. Backing up the MPC node database before upgrading is recommended.

### Node Configuration

When upgrading an MPC node, the Node Configuration API changes from v18.1 to v21.4, which includes breaking changes that may require modification of the MPC node configuration file.

### Upgrading the SDK

When upgrading Builder Vault from V62 to v70, the Client Communication API changes from v27 to v29, which includes breaking changes. If you use RSA, AES, HMAC, AN10922, or RFC5649 operations, you need to upgrade the SDK to v70 simultaneously. If you use ECDSA or Schnorr, you can upgrade an MPC node without upgrading the SDK, though upgrading is still recommended.