December 2021 - Version 3.6.6

HSM Cluster

• Enabling the second part of the feature concerning the migration of objects from the single HSM to the cluster HSM.

December 2021 - Version 3.6.5

Improvements

• Several improvements to account synchronization for Bitcoin and Litecoin.

November 2021 - Version 3.6.4

Improvements

HSM Cluster

• Preparing the different components and updating the code ahead of the migration of all workspaces towards the HSM Cluster environment.

User Interface

• Several miscellaneous wording improvements were made.

November 2021 - New ERC20 supported

Additional ERC20 tokens supported

The Ledger Vault now supports additional ERC20 tokens, including:

</p>

October 2021 - Version 3.6.3

Improvements

• Several structural changes to already existing features in order to make them more robust.

October 2021 - Version 3.6.2

Additional ERC20 tokens supported

The Ledger Vault now supports additional ERC20 tokens, including:

Review the full list of Supported crypto assets (or download it here).

Goodbye U2F, hello WebUSB!

• WebUSB has now been supported on the Ledger Vault platform for two years. It allows web users to access the platform seamlessly using their Ledger device.
• As such, this means that U2F will no longer be supported on the Ledger Vault platform as it's being decommissioned for use.

WebUSB is automatically selected on the Sign in page. You'll be required to pair your device with your Chrome browser when you first sign in:

1. Connect your device and tap your PIN code.
2. Click Sign in on the web app.
3. Select "Blue" on the Chrome certificate which pops up, then click Connect .
4. 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.

Improvements

User interface

• Several improvements to filters and search were made, in addition to various miscellaneous visual improvements.

September 2021 - Version 3.6.0

Improvements

Whitelists enhancement

• Until today, whitelists could only contain 25 addresses and you were limited to 5 edits when creating an edit request. We’ve now improved this feature to allow you to add up to 300 addresses per whitelist and removed the limitation of 5 edits to support 90 edits of changes.

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 whitelist improvements . See Update the Ledger Blue Enterprise , for step-by-step instructions.
• Following the version upgrade, when creating or editing an account, you'll see a new field named "Entity" on your device. Until the rollout of the "Entity" feature is complete across the whole platform, this field will be set as "N/A" and has no impact on your standard account creation or edit operations.

August 2021 - API v1.3 and Version 3.5.4

API

What's new

- This release note details the changes introduced with API v1.3 and LAM v.1.3

- API v1.3 remains backward compatible with LAM v1.1 and v1.2

• You can assign the View-all permission to API Operators. This allows the user to view all data in the workspace, whether it’s an account and its approval workflow or the list of all registered users. Administrators can enable this permission in Users > Username > Permissions tab and enable the View-all toggle.
• By default, API Operators won't be able to access any information unless they're added to the rules of an account or granted View-all permission.
• You can now integrate HashiCorp Vault to LAM to securely store the users' seeds used and benefit from customizable authentication policies to access encrypted-at-rest seeds.
• Hashicorp Vault is an open-source secrets management tool specifically designed to control access to sensitive credentials, such as the seeds and certificates stored on LAM.
• Using HashiCorp Vault allows you to encrypt your seeds at rest, segregate their access, and enforce a layer of authentication to access them.
• For detailed instructions on how to integrate HashiCorp Vault to LAM see, Help Center . For more information on HashiCorp, see the HashiCorp Vault documentation .

Fixed

• Fixed an issue where the field validation caused the GET /transactions endpoint to fail when querying certain transactions. The broadcast _ on field is now optional to handle non broadcasted transactions.

Enhancements

• Smart contract addresses of ERC20 token accounts are now visible on the Settings page of the account dashboard.
• It’s no longer possible to select a unit in the settings of an account. Cryptocurrency amounts will be shown in their native currency, such as BTC, ETH, or XRP.
• Other minor UI and wording improvements.

July 2021 - New ERC20 supported

The Ledger Vault now supports additional ERC20 tokens, including:

Review the full list of Supported crypto assets (or download it here).

June 2021 - New ERC20 supported

The Ledger Vault now supports additional ERC20 tokens, including:

Review the full list of Supported crypto assets (or download it here).

## May 2021 - New ERC20 supported (part 2) ---------------------------------------

The Ledger Vault now supports additional ERC20 tokens, including:

Review the full list of Supported crypto assets (or download it here).

May 2021 - New ERC20 supported (part 1)

The Ledger Vault now supports additional ERC20 tokens, including:

Review the full list of Supported crypto assets (or download it here).

April 2021 - New ERC20 supported (part 2)

The Ledger Vault now supports additional ERC20 tokens, including:

Review the full list of Supported crypto assets (or download it here).

April 2021 - Version 3.5.0

What's new

API

• API users can now create a third type of user: the API Operator. This user has the same role and responsibilities as a regular Operator, but can only be created for API users.
• The CIT environment will be updated shortly after this release. A short downtime is to be expected (API users only).

User interface

• The Ledger Vault's new user interface is now officially used by default. If you used the old interface, this will no longer be possible.
• The Ledger Vault will now prevent you from creating BCH transactions to cash addresses as they aren't supported.

Improvements

• A warning has been added to inform you that the gas limit on Ethereum transactions shouldn’t be lower than 21,000. If you choose to send the transaction anyway it may fail.
• Fixed an issue where a transaction was shown as pending in XRP accounts when there was none.
• Fixed an issue where XLM transaction fees were set to Low by default instead of Medium .
• Fixed an issue where the XLM Memo field wasn't entirely visible. You can now see the full memo and copy it.
• Fixed an issue where all approvers in the approval workflow could review a request that should have only been visible to one set of approvers.
• Other minor UI and wording improvements.

April 2021 - New ERC20 supported (part 1)

The Ledger Vault now supports additional ERC20 tokens, including:

Review the full list of Supported crypto assets (or download it here).

March 2021 - New ERC20 supported (part 3)

The Ledger Vault now supports additional ERC20 tokens, including:

Review the full list of Supported crypto assets (or download it here).

March 2021 - New ERC20 supported (part 2)

The Ledger Vault now supports additional ERC20 tokens, including:

Review the full list of Supported crypto assets (or download it here).

March 2021 - New ERC20 supported (part 1)

The Ledger Vault now supports additional ERC20 tokens, including:

</p>

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

Added

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

Fixed

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

</p>

January 2021 - API v1.1

- This release notes details the changes introduced with API v1.1 and LAM v.1.1

- API v1.1 remains backward compatible with LAM v1.0

Added

• LAM and Vault versions are now exposed on a new endpoint / _ version.
• Additional information has been added to the GET /api _ users endpoint documentation.

Changed

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

Fixed

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