What's new

Learn about the latest features and enhancement.

September 2020 - Version 3.3.0

What's new

Features listed in this release will progressively be rolled out to all customers. Contact your Technical Account Manager for more information.

Stellar is now supported

  • You can now create Stellar (XLM) accounts in your Ledger Vault workspace to send and receive funds. Stellar brings to 14 our list of supported crypto assets and over 1,500 ERC20 tokens.
  • Creating a Stellar transaction is similar to any other transaction. You have the possibility to provide a Memo if you have one. Note that as required by the Stellar network, you must have a minimum balance of XLM 1 at all times in your accounts.


Ledger Blue Enterprise

  • To improve your experience when using the Ledger Blue Enterprise, we have increased the auto-lock delay from 30 seconds to 3 minutes. This ensures you’re not constantly prompted to enter your PIN. If you’d like to increase or decrease this, close the Vault app and go to the Settings page of your device.
  • We’ve simplified the process of changing your PIN to just a couple of steps. To do so, go to the Settings page and follow the steps on-screen.
  • For security purposes, you’ll be prompted to provide your PIN whenever you unplug your device and whether the Ledger Vault app is opened or not.
  • You’ll now find your device’s endorsements details in the Settings page of your device. Our Support team might ask you to provide this information in case of issues.

July 2020 - Version 3.2.0

What's new

Concurrent transaction approvals

  • You can now create multiple concurrent transaction requests per account. Thanks to an architectural redesign, you no longer have to wait for the previous transaction request to be approved to create new ones. Requests are broadcasted once they’ve received the necessary approvals and can be approved in any order.
  • When transaction requests are pending in your account, a new field will show the available balance. The available balance is computed by subtracting the value of pending transactions and max fees from the total balance. This is the amount you can spend on other transactions.
  • The transaction fees displayed when creating transaction requests are now the estimated max fees. The exact fee is calculated when the last approval is collected, but will never exceed the announced max fees. For Ethereum, ERC20 tokens, and XRP you can also define your own max fees. However, if that amount is too low the transaction will take longer to confirm.
  • For more information, see Transactions.

Native SegWit (Bech32) support

  • When creating Bitcoin accounts, you can now select whether you want to create a Legacy or Native SegWit (Bech32) account. The latter is recommended to increase transaction speed and lower transaction fees.
  • You can also now send transactions to any Segwit addresses.

Ledger Blue Enterprise update

  • Before signing in to your workspace, you’ll be prompted to update the Vault app. This new version contains improvements to the security of your device and enables concurrent transaction approvals. See Update the Ledger Blue Enterprise, for step-by-step instructions.


  • The CSV export of your transaction data has been improved to include the creation and broadcast date for each transaction.
  • Before you were able to regenerate an existing address by selecting one from a list. From now on, you’ll have to enter the derivation path of the desired address. This enhancement will avoid having you scroll down a long list when many addresses have already been generated in an account. For more information see, Generate a receiving address.
  • Before you weren’t able to edit the account name after creation, from now on this is possible. You can do this by creating an Edit account request from the dashboard of the account. For more information, Edit an account.
  • When consolidating UTXOs, you’ll now see the total amount in USD and in the crypto asset of the account.


  • Due to display issues on the Ledger Blue Enterprise, whitelists can now contain up to 25 addresses instead of 100 until now.
  • When editing whitelists, you will now be limited to 5 edits per request. If your whitelist requires more changes, you’ll have to create additional requests.

Release notes archive