New Features & Improvements

• [Wallet v1 & v2] Added mobile support for complete transaction initiation with warm MPC wallets.
• [Wallet v2] Added mobile support for Travel Rule compliance.
• [Wallet v2] Improved address screening in Travel Rule compliance for safer transfers.
• [Wallet v2] Improved transparency with complete destination address visibility during approvals in Travel Rule compliance.

API Reference

• [Wallet v2] Improved maxNumInputsToUse variable limit (max batch size) from 50 to 200 for consolidated wallet transaction requests for UTXO chains.

Docs

• Added release note for Liminal Vaults web and mobile [Sep 16, 2025].
• [Wallet v2] Added send a transaction with Travel Rule on the mobile guide.
• [Wallet v1 & v2] Added initiating a transaction on the mobile section ( v1, v2 ) to the Transfer funds from a warm MPC wallet ( v1, v2 ) guides.
• [Wallet v1 & v2] Updated decimal precision description for fields (effectiveChange, effectiveChangeUsd, fee, inputs[].amount, and outputs[].amount) in Receive ( v1, v2 ) and Send ( v1, v2 ) transaction webhook guides.
• [Wallet v1 & v2] Updated webhook payload parameters table parameters for Receive transactions ( v1, v2 ) and added a note for clarity.
• [Wallet v1 & v2] Updated webhook payload parameters table variables for Send transactions ( v1, v2 ) and added a note for clarity.
• [Wallet v2] Fixed incorrect API base URL and endpoint path for wallet consolidation transaction requests.

A new guide on Archiving and Unarchiving Wallets is added under the Vaults UI guides tab.

You may want to archive certain wallets in your organisation for the following reasons

1. To migrate funds from a V1 wallet to V2 wallet. Post migration of funds these V1 wallets would be of no use.
2. The wallet is no longer being used.
3. The wallet was created by mistake.

Archiving a wallet removes it from the Wallets section of the Liminal Vaults dashboard and disables all future send transactions. Archived wallets are moved to a separate section and can be unarchived at any time.

Changed environment variable values from those ofPre-dev to Dev environment

• V1 Wallet Postman Collection
• V2 Wallet Postman Collection

The following note is added in Receive transaction webhooks and Send transaction webhooks.

Currently, webhooks contain both x-platform-signature and x-liminal-signature headers. However, Liminal will deprecate x-liminal-signature in future. As an organisation, you are advised to configure only x-platform-signature going forward.

A new Submit a transactionAPI reference document is added under API References. This API is used to submit transactions for broadcasting to the blockchain network from a specific v2 hot wallet.

The Create transaction requests v2 API reference is updated by improving the API description and response body.

Liminal has released new production environment version v1.2.0 of Liminal Express. To learn about the changes in this version, see Version v1.2.0 (Prod).

The default value of minimum consolidation balance threshold for tokens is changed from 10 USD to 4 USD in the Default address balance thresholds table. The value is updated due to a dip in the network gas fee for Ethereum.

A new Retrieve all transaction by status API reference document is added under API References. This API is used to fetch all transactions across all wallets based on their current status.

The following API reference docs are recently updated:

• Consolidation API error responses - Added the Skipped address errors section in the document. The table consists of the error messages that you receive in the API response, error explanation, and solution.
• Retrieve hot wallet transactions - Updated the API title and added the filter object in the request body.