Learn about the latest features and enhancement.
March 2021 - New ERC20 supported
The Ledger Vault now supports additional ERC20 tokens, including:
|UnFederalReserveToken (eRSDL)||THORChain ETH.RUNE (RUNE)|
|GIGCoin (GIGCOIN)||Offshift (XFT)|
|Rari Governance Token (RGT)||Apollo (APO)|
February 2021 - API v1.2
- This release notes details the changes introduced with API v1.2 and LAM v.1.2
- API v1.2 remains backward compatible with LAM v1.0 and v1.1
- The documentation now lists all notification events and a short description. For more details, see Notifications.
- You can retrieve the oldest version of LAM compatible with the current API version using the _version endpoint.
- The API usage is now limited to the supported versions of LAM. If you interact with the API using a deprecated version of LAM, an error will prompt you to upgrade.
- The API user’s type and role section of the documentation has been clarified to better describe each role. For more information, see API users.
- Fixed an issue where the number of calls calculated by the rate limiter wasn't accurate. From now on, when generating N receiving addresses, N calls will be recorded.
- Fixed an issue where an error appeared on first run when user_store is missing.
February 2021 - New ERC20 supported
The Ledger Vault now supports additional ERC20 tokens, including:
|AlphaToken (ALPHA)||NFTX (NFTX)|
|Index (INDEX)||RAMP DEFI (RAMP)|
|Yield (YLD)||DeFiScale (DFC)|
January 2021 - API v1.1
- API v1.1 remains backward compatible with LAM v1.0
LAM and Vault versions are now exposed on a new endpoint /_version.
Additional information has been added to the GET /api_users endpoint documentation.
The account id is now optional when creating and approving a transaction. Note that providing the account id will be deprecated in the next version of LAM.
The https://api.vault.ledger.com endpoint has been set as the default target.
The creation of API users is now done through a POST endpoint with a JSON body.
coin_fields allow separating blockchain-specific parameters to keep the API simple and easy to use as we add more coins to the Vault. Coin-specific fields, like destination_tag for XRP, are read from the coin_fields node.
The max threshold of the amount range max is now optional. You can now retrieve accounts for which no upper limit has been defined.
The Signed status is now supported when querying the request’s history.
API tokens are now verified using the constant-time comparison method to prevent using timing attacks to guess tokens.
When approving a transaction the account id is now validated.
When creating a transaction we now ensure the gas price is always greater than 1.
'Method not allowed' HTTP errors are now properly handled on API Users' routes.
A 400 error is now raised when the same API Operator approves a transaction for the second time.
When creating or approving transactions, amounts are now validated using regex.
Additional information has been added when documenting amount objects as string.
The unsupported custom fees option has been removed when creating new transactions.
A 500 error is no longer raised when approving someone else’s transactions.
API usernames are now properly validated. A 400 error is raised in case of violation.
The broadcast_on field has been added to transactions.
Release notes archive
You can now interact with the Ledger Vault’s API to query account balances, search for information on transactions, and create and approve transactions.
If you wish to use the Ledger Vault API, please get in touch with your Technical Account Manager.
A new warning has been added to inform you of the Bitcoin Cash (BCH) suspension. For more information, see Operational announcements.
The number of transactions you can export in one go to a CSV file has been limited to 2,000. If you need more data, either create multiple exports or use the Vault API.
Fixed an issue where the recipient address was displayed in both the sender and recipient columns in the exported CSV file.
Additional ERC20 tokens are now supported (download).
Fixed an issue where it was possible to create two Administrators with the same name if the first request wasn’t approved before the second one.
Wording improvements when creating and completing requests.
Amounts which are too long and can’t be displayed properly will now be rounded up. Hover over the amount to display the full number.
General interface improvements and fixes.
After the fork on November 15th, Bitcoin Cash (BCH) has split into two new blockchains: Bitcoin Cash Node (BCHN) and Bitcoin Cash ABC (BCHA). For the time being, only Bitcoin Cash Node (BCHN) will be supported on the Ledger Vault.
The Bitcoin Cash Node crypto asset will be called Bitcoin Cash on our platform and will use the BCH ticker
Discover the new interface
Version 3.4.0 allows you to try out our redesigned web interface. This complete revamp improves the usability of the platform and makes your work easier.
The navigation remains identical with all tasks accessible from the left panel, while dashboards, tables, and requests creation flows have been redesigned and improved. You can now clearly follow the interaction between your device and the web app thanks to new visuals.
You can try the new interface now, and roll back to the previous one at any time!
Let us know what you think <here> or contact your Account Manager.
From now on, you’ll automatically be alerted whenever new requests are created or processed within your workspace. The notifications will appear in the top right corner, and clicking them will take you to the appropriate request – whether it’s in progress or completed. This new feature ensures you’re always aware of what is going on in your workspace when you’re connected.
For now, notifications only appear when requests are created or processed. In a future release, they’ll all be listed in a Notifications Center.
Following the recent fees increase on the Ethereum network, we’ve raised the gas limit for ERC20 tokens and smart contract transactions. This will avoid your transactions to fail by ensuring enough funds are available to pay the fees.
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.
- Fixed an issue where you could make an Ethereum or it's children ERC20 account unusable by creating multiple edit requests at the same time.
From now on, you'll have to process the pending request – either on Ethereum and its ERC20 children accounts – before creating a new one. See the table for more details.
|I want to...||Edit an Ethereum account when...||One of its linked ERC20 accounts is pending to be edited...||
You'll be prevented from editing the Ethereum account until the edit request is processed.
|Edit an ERC20 account when...||Its parent Ethereum account is pending to be edited...||You'll be prevented from editing the ERC20 account until the edit request is processed.|
|Edit an ERC20 account when...||Another ERC20 account linked to the same parent Ethereum account is pending to be edited...|
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.
Unspent Transaction Outputs (UTXOs)
- The Ledger Vault now allows you to view and manage UTXOs for Bitcoin and Bitcoin-like blockchains. You can review the UTXO distribution from the account’s dashboard and consolidate UTXOs which have the lowest amounts into a single one. The consolidation can be performed on up to 100 UTXOs at a time. For more information, see Unspent Transaction Outputs (UTXOs).
- When creating a transaction, you can now select which UTXOs should be used among these three options:
- Merge outputs, to select UTXOs which have the lowest amounts. This is the method used by default.
- Deep outputs first, to select UTXOs which have the highest amount of confirmations on the blockchain.
- Optimize size, to select UTXOs which have the highest amounts.
For more information, see Create a transaction.
Update your device seamlessly
- We have improved the user experience of the firmware and app update process to guide you through each step of the process. For more information, see Update the Ledger Blue Enterprise.
Connect to your workspace in one click
- Until today, you needed a client certificate and a workspace name to connect to the Ledger Vault. This is no longer needed. From now on, you can safely connect using your device only. You’ll be automatically signed in to your workspace. If you have access to multiple workspaces, you can also select it here. For more information, see Sign in and out of your workspace.
Recreate rejected or failed requests
- You can now easily recreate requests which have been rejected by another user or which have failed. This can be done from the request dialog. For more information, see Recreate a rejected or failed request.
- You can now generate again and verify an address previously generated on the Ledger Vault instead of requesting a new one. For more information, see Generate a receiving address.
- The Help Center is now available at https://help.ledger.vault.com for both Administrators and Operators.
- When generating a receiving address for an account, you must now verify the address on your device before it’s shown on-screen.
- Implemented a new database management system that improves the stability and performance of services reading the blockchain.
- Fixed an issue where a balance of 0 was shown on the account dashboard during service downtime. From now on, the last known balance will be displayed while transactions are refreshed in the background.
- Administrators can now generate receive addresses from the account's dashboard. For more information see, Generate a receiving address.
- You can find out which versions of the Ledger Vault you are using by clicking the version number at the bottom of the left panel.
- Fixed an issue where you weren't able to use the name of a whitelist or group that has previously been rejected.
- Fixed an issue where the currency's unit displayed on the Ledger Blue Enterprise was incorrect.
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.
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.
- 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.
- 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.
- Ripple (XRP) is now supported on the Ledger Vault.
- 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.
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:
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:
- Connect your device and enter your PIN code.
- On the web app, enter your workspace name.
- Click Sign in.
- Select the name of your device in the Chrome dialog, and click Connect.
- On your device, tap Sign in.
- Overall speed and UI enhancements.
You'll be required to pair your device each time you clear your cache or use a different computer.
- 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.
- Improved the performance and speed of the Ledger Vault platform.
- The Dashboard page will now be referred to as the Home page.
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.
- 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.
- Fixed an issue where the number of transaction approvals couldn't be displayed.
- Fixed an issue where the approval workflow couldn't be displayed.
- 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 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.
- 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.
- Click the Settings icon on the Account page.
- Click Copy xPub under the Advanced section.
- Select the I understand option to confirm you won't use the xPub to derive receiving addresses.
- Click Copy xPub.
- When creating ERC20 token transactions, it's now possible to send the entire balance.
- 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.
- 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 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.
The Settings page isn't available on ERC20 account dashboards.
- 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.
- 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.
- 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 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.