What's new

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.

Improvements

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

Limitations

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

What's new

This release introduces enhancements to the governance of your accounts, allowing you to define extensive transaction rules.

When creating an account you used to be able to define a four-step approval workflow where Operators selected in the first step were able to create and approve transactions, while others were only allowed to review and approve requests.

From now on, you'll be able to define comprehensive conditions starting with rules. A rule is a set of conditions you define for an account. You can create up to four unique rules per account, each customizable with the following conditions:

• Creators: Operators allowed to create transactions in the account. You can manually select 20 Operators or a group.
• Amount range: (optional) Allows you to define how much Operators can spend. This is particularly useful if you want only certain Operators to be allowed to spend high amounts for example. If you don't specify one, no limitations will be applied.
• Whitelist: (optional) Allows you to select previously created whitelists which contain addresses you've grouped in a list. If you select a whitelist, Operators will only be able to send funds to these addresses, depending on the conditions configured for other rules.
• Approval workflow: Allows the selected Operators or group to review and approve the transaction. You can define up to three steps.

Improvements

• To ensure Ethereum addresses are EIP-55 compliant a check will now be performed. In cases where the address is invalid, a converted address will be generated.

• Improved the performance and speed of the Ledger Vault platform.
• Total amounts are no longer rounded up. The exact amount is now always displayed.
• This release also includes a complete redesign of the Ledger Blue Enterprise user interface.
• For ease of use, clicking Export data to CSV on the Transactions page now downloads transaction data depending on the selected filters.
• When creating a transaction, you can now click the circular arrow icon to recalculate fees whenever necessary.

What's new

• You can now export your transaction data in a CSV file directly from the Ledger Vault platform. Using the different filters available on the Transactions page you are able to select the relevant data and transactions to export.

Improvements

• It is now possible for a user who has already approved a transaction to abort it.
• Improved transaction fee computation for ERC-20 tokens.
• The Ledger Vault now supports 1341 ERC-20 tokens, please find the full list here.
• Overall speed and stability enhancements for the Ledger Blue application and the Ledger Vault web portal.

What's new

• Ripple (XRP) is now supported on the Ledger Vault.

A new field has been added to the Create transaction page to allow entering a Destination tag for addresses that require one.



Be aware that:

• The account won't be active before it receives 20 XRP, and you'll be required to hold a minimum of 20 XRP at all times.
• You'll be prevented from creating a transaction if your account's total balance falls below 20 XRP.

• Transactions below 20 XRP sent to inactive Ripple accounts aren't permitted by the network and will fail.

• It's now possible to synchronize your account's dashboard with the latest information from the blockchain network by clicking the synchronize button in the top right corner.



• WebUSB is now supported on the Ledger Vault platform. This allows Windows users, who recently made the update to version 1903, to access the platform seamlessly using their Ledger Blue Enterprise.

This update is the consequence of changes made to the U2F libraries – used to establish a communication channel between the computer and the Ledger Blue Enterprise – that prevented users from connecting to the platform.

WebUSB is optional and can be activated from the Sign-in page by selecting the WebUSB option in the top right corner.



Once done, you'll be required to pair your device with your Chrome browser when you first sign in:

1. Connect your device and enter your PIN code.
2. On the web app, enter your workspace name.
3. Click Sign in.
4. Select the name of your device in the Chrome dialog, and click Connect.
5. On your device, tap Sign in.

You'll be required to pair your device each time you clear your cache or use a different computer.

• Overall speed and UI enhancements.

Improvements

• You can now review the details of an account and edit it directly from the Accounts page by clicking the vertical ellipsis menu.
• The Ledger Blue Enterprise will now directly take you to the Ledger Vault app welcome screen after switching it on. And, it'll no longer prompt you to enter your PIN code before approving requests.

Note that the device automatically locks after a set time of inactivity and therefore requires you to enter your PIN code to unlock it. To increase the auto-lock delay, close the Ledger Vault app and go to the Settings > Device page.

• Improved the performance and speed of the Ledger Vault platform.
• The Dashboard page will now be referred to as the Home page.

Fixed bugs

• Fixed a bug where you could create a transaction in all ERC20 token accounts linked to the same parent Ethereum account at the same time, which resulted in these transactions to fail. To solve this, you'll now only be able to create one transaction at a time in all of these accounts and wait until the transaction is broadcasted before creating new one.
Example
The Coinplace ETH account is linked to 3 children ERC20 token accounts (Account A, Account B, and Account C). If a transaction is pending in Account A, you won't be able to create a transaction in Account C before it's broadcasted to the blockchain network.
• Fixed an issue where the number of transaction approvals couldn't be displayed.
• Fixed an issue where the approval workflow couldn't be displayed.

What's new

• New Operator role:
  • The Operator role has been added. Previously Administrators were able to manage the platform and create transactions. In this release, Operators will now be the only users able to handle transactions. Depending on their permissions, they'll either be able to create and approve transactions or approve them only. This permission is defined when creating the account.
  • Operators will have a dedicated device which will only require a PIN code to be used.
  • Operators can only access and create transactions on accounts where they have been authorized by Administrators.
• Updates to the Administrator role:
  • Administrators will now only take care of the platform's management, they cannot create or approve transactions.
  • Administrators can create, edit or delete groups, create or edit accounts, and invite, revoke or suspend users on the workspace.
  • Your workspace admin rule can now be edited by Administrators at any time after the Onboarding.
• General updates:
  • When creating accounts, the transaction rules option has been enhanced to allow you to define an approval workflow where a transaction can go through up to four different steps before it's broadcasted to the blockchain network.
  • Improved user interfaces on the web application and Ledger Blue Enterprise.

Fixed bugs

• Fixed an issue where the Vault couldn't be used on regular Internet browsers because of an update of device interaction libraries.
• Fixed an issue where only 8 Administrators could be added to a workspace. This limit has been increased to 20 Administrators.
• Fixed an issue where the transaction fee calculation failed.
• Improved the performance and speed of the Vault platform.
• Resumed support for the BCH blockchain.

What's new

• It's now possible to get the xPub of each account created on your Ledger Vault workspace. The xPub allows you to monitor your accounts' activity to meet your reporting needs.

You mustn't derive receiving addresses from the xPUB as incoming funds won't be accessible from the Ledger Vault.

Instructions:

1. Click the Settings icon on the Account page.
2. Click Copy xPub under the Advanced section.



3. Select the I understand option to confirm you won't use the xPub to derive receiving addresses.
4. Click Copy xPub.

• When creating ERC20 token transactions, it's now possible to send the entire balance.

Fixed bugs

• Fixed an issue where transaction requests weren't properly closed on the HSM resulting in the impossibility to create new ones.
• Fixed an issue where Ethereum and ERC 20 token transactions were failing.
• Improved the performance and reliability of the Ethereum explorer.

What's new

• The Settings page, which was accessible from the top navigation, is now available from the account's dashboard by clicking in the top right corner. It displays general information, such as the exchange rate platform used. You can also select the unit in which the balance of the account is displayed.

The Settings page isn't available on ERC20 account dashboards.

• The exchange rate platform, from which the countervalue is indexed, is now dynamic and gets its value from the most accurate website.
• When creating an account, you can now search for ERC20 tokens by ticker and smart contract address.
• It's now possible to create an Ethereum account along with a new ERC20 account. However, the Ethereum account will have the view-only status until you provide its transaction rules. For more information, see Workspace administration.
• Due to a hard fork, it's not currently possible to create Komodo and Bitcoin Cash transactions.

Fixed bugs

• Fixed an issue where clicking outside of the New account request and New transaction request dialogs closed the page and required you to redo the process.

• Fixed an issue where you were able to create accounts with less than 2 members or less than 2 approvals. You'll now be required to select at least 2 members and 2 approvals when creating accounts.

What's new

• The Ledger Vault now supports Ethereum and over 1,000 ERC20 tokens. Click here to download the full list of supported ERC20 tokens.
• The New account and New transaction wizards have been updated to consider ERC20 tokens constraints, such as the need for an Ethereum account to pay gas fees. For more information, see Create a transaction, Create an account, and Workspace administration.
• The Ledger Blue Enterprise firmware has been updated. Follow the Update the Ledger Vault app steps to migrate to the new version.
• General UI improvements, including the following:
  • Account dashboard: Additional information on the account are displayed, such as the cryptocurrency and Index, the list of members, approval scheme etc.

  

  • New transaction wizard: Now displays the total amount to be sent in the bottom left corner.

  

  • Last transactions: Incoming and outgoing transactions are now easily identifiable thanks to icons.

  

What’s new

• The Ledger Vault platform now supports two additional cryptocurrencies: Bitcoin Cash and Bitcoin Gold.
• You can now generate public addresses and QR codes and verify them on your Ledger Blue Enterprise device. This feature provides an additional layer of security by allowing you to ensure the public address displayed on-screen hasn’t been tampered with. For more information, see Generate a receiving address.
• It’s now possible to preview the balance of an account before you approve or reject a pending Account request in the Pending page.



• The search functionality is now available to help you find transactions.

Fixed bugs

• Fixed an issue where the wrong account balance was displayed.
• Fixed an issue where the blockchain confirmation status wasn't retrieved. Transactions that have been confirmed on the blockchain network are now shown as 'Confirmed' in the Last transactions table and the number of confirmations that has been received is shown between brackets.



• Facilitated onboarding in case of disaster recovery following a HSM failure.

• Public addresses of identifiers shown on the Details tab of the Transaction’s details dialog are now capitalized appropriately.
• The same date format is now consistently used across the platform.
• Overall security enhancements.