🚀 What's New

Transaction History for Vaults Mobile

With this release, the Liminal Mobile app introduces a new History page that provides a comprehensive view of all transactions within your organisation, along with their associated metadata.

Access:

Sign in to the Mobile app.
Click the History tab from the homepage.

Key capabilities:

Quickly review and verify transaction activities at any time to maintain a clear audit trail of all financial movements on the go.
Search for a transaction using the search bar.
Filter the transaction history via transaction status and date picker.
View the transaction history details, including transaction metadata.

Refer to the History section in the Liminal Mobile app to view and manage transaction history on your mobile device. Refer to the Liminal Mobile App guide to learn about the mobile app.

✨ Improvements

Address Screening for Transaction Initiation Flow

With this release, Initiators can verify transactions for Address Screening when initiating (sending) a transaction on the Vaults web app. The enhancement strengthens security by enabling Initiators to review and validate destination addresses before submitting a transaction.

Key capabilities:

Supported wallet: MPC Mobile and Multisig wallets.
MPC Transaction initiation (Send): When initiating a transaction as an Initiator via the Vaults web app.
Access: You can initiate transactions from:
- Home > Send, or
- Wallets > Send on the Vaults web app.

Refer to the following guides:

Address Screening validation for MPC Wallet Transactions.
Address Screening validation for Multisig Wallet Transaction.
Initiate and Sign an MPC wallet transaction.
Initiate and Sign a Multisig wallet transaction.

Transaction History Timeline

With this release, the Transactions History side-panel is enhanced with a Timeline tab to provide a chronological order of all user-initiated transaction events. The Timeline record is only available for Send transactions.

Key capabilities:

Enhanced user experience: Quickly track and follow every step in a transaction journey as each user-initiated event and its description are recorded chronologically.
Comprehensive visibility into transaction lifecycle: Displays the user name, their IP address, and event timestamp for improved transparency and audit readiness.
Recorded Events: Gain visibility with transaction events recorded during their lifecycle.

Refer to the Timeline section in the History guide to learn more.

Disabled Resend button

The Resend button is disabled for Periodic webhooks in Receive transactions to improve clarity, as this webhook type is intermediary and cannot be resent.

Enhanced Whitelisted Address Sorting in Vaults Mobile

Improved the sorting order of whitelisted addresses when the user initiates a transaction from Vaults Mobile. The latest whitelisted address now appears at the top.

Liminal Express SDK v1.3.1

Updated the latest version of Liminal Express SDK to v1.3.1 and the respective Docker container image to /liminal-sdk-api:1.3.1.

Refer to the Update Liminal Express guide to update to the latest version

🛠️ Resolved Issues

sequenceId Consistency in Wenhook Fixed an issue where sequenceId was missing from some webhook request bodies. The sequenceId is now fetched directly from the raw transaction data and populated in webhook request bodies, ensuring consistency.
Webhook Performance Optimisation Fixed webhooks optimisation and performance in Vaults UI and Liminal Express SDK for Success and Periodic webhooks for Send and Receive transactions.
x-forwarded-for Header Validation Fix Resolved an issue where the x-forwarded-for header parameter could not handle additional values of whitelisted IP addresses for an API key. It now correctly supports additional values.
Rescan API TransactionHash Fix Fixed an issue where the Rescan API returned a success response for an invalid transactionHash for BTC, ALGO, CELO, DOGE, BCH, and LTC chains. The API now correctly returns a 404 Not Found error for an invalid transactionHash.
Accurate externaladdress in Batch Webhooks Fixed an issue where the Receive and Send webhooks for batch transactions returned an inaccurate externaladdress in the request body. Now, the externaladdress parameter is retrieved accurately.