---
updatedAt: 2026-01-09T07:51:25.000Z
agentTools:
  projectIndex: https://docs.lmnl.app/llms.txt
---

# January 09, 2026

This release enhances transaction lifecycle management, boosts reliability, and introduces platform upgrades for a more robust experience.

# 🚀 What's New

## Automatic Expiration for Failed Tron Transactions

<Image align="center" border={true} src="https://files.readme.io/741d9afc9cf95846d3d9e07625c905af20aaa41750bf59ffce093dc891bd38d6-CleanShot_2026-01-08_at_16.51.52.png" className="border" />

With this release, we have added support for **Send** transactions using the Tron chain with a 24-hour automatic expiration feature. It is available in the **Vaults web** for **MPC** and **Multisig** transactions. The auto-expiration feature encourages seamless transaction initiation and signing approvals, facilitating faster completions. It also enhances the visibility of transaction status and the management of expired transactions.

### Key Capabilities

1. Reminder message during a **Send** transaction initiation.
2. Introduces a countdown **Timer** for pending transactions and in the transaction’s **Side-Panel.**
3. Automatically expires an incomplete transaction, moving to **Transactions History** and primary status to **Rejected**.

Refer to the following resources:

* The [Auto-Expiration for Tron Transaction](https://docs.lmnl.app/docs/transfer-funds#auto-expiration-for-tron-transaction) section to learn more information about this feature.
* [Transfer funds from the MPC wallet](https://docs.lmnl.app/docs/transfer-funds-from-a-warm-mpc-wallet).
* [Transfer funds from a multisig wallet](https://docs.lmnl.app/docs/initiate-multi-sig-transaction).
* Refer to [History](https://docs.lmnl.app/docs/history) to learn about transaction statuses.

## Latest Versioning

Check out the latest versions of impacted applications:

<Table align={["left","left","left","left"]}>
  <thead>
    <tr>
      <th>
        Component
      </th>

      <th>
        Version
      </th>

      <th>
        Description
      </th>

      <th>
        App / SDK Location
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        Liminal Express SDK (Production)
      </td>

      <td>
        `v1.3.7`
      </td>

      <td>
        Refer to the  Update Liminal Express guide [Wallet [v1](https://docs.lmnl.app/reference/update-liminal-express#/) & [v2](https://docs.lmnl.app/v2/reference/update-liminal-express#/)].
      </td>

      <td>
        [Production Web](https://vaults.lmnl.app/)
      </td>
    </tr>

    <tr>
      <td>
        → MPC Docker Image
      </td>

      <td>
        `/liminal-sdk-api:1.3.1`
      </td>

      <td>
        Pull the latest MPC Docker image to the latest production version [Wallet [v1](https://docs.lmnl.app/reference/update-liminal-express#/3-pull-the-latest-image) & [v2](https://docs.lmnl.app/v2/reference/update-liminal-express#/3-pull-the-latest-image)].
      </td>

      <td>
        Client side
      </td>
    </tr>

    <tr>
      <td>
        → Express API Postman Collection
      </td>

      <td>
        [Liminal Express Developer_1.3.1 (v1).postman_collection.json](https://github.com/LiminalVaults/Liminal-Express/blob/main/Liminal%20Express%20Developer_1.3.7%20\(v1\).postman_collection)

        [Liminal Express Developer_1.3.1 (v2).postman_collection.json](https://github.com/LiminalVaults/Liminal-Express/blob/main/Liminal%20Express%20Developer_1.3.7%20\(v2\).postman_collection)
      </td>

      <td>
        Use the updated Liminal Express API Postman collection.
      </td>

      <td>
        [Postman Collection Repo](https://github.com/LiminalVaults/Liminal-Express/tree/main)
      </td>
    </tr>
  </tbody>
</Table>

# ✨  Improvements

## Failed On-Chain Transaction Reliability for Tron

**Send** transactions, using the **Tron** chain, that fail on-chain are now accurately reflected across the platform and communicated through webhook alerts. This enhancement brings clear visibility into failed Tron transactions, enabling faster and more reliable alert handling through webhooks.

* **Transaction Status**
  * Failed **Tron** transactions are now marked as **Rejected** status with a **Failed On-Chain** secondary status.
  * **Rejected** transactions are recorded in the **Transactions History** for complete traceability.
* **Webhook Alerts**: The **Send** Transaction webhook is triggered, allowing you to detect and handle failures programmatically.

Webhook status payload for Sent on-chain failure:

```json
"transactionStatus": {
    "legacyStatus": 5,
    "primaryStatus": "failed",
    "secondaryStatus": "failed_on_chain"
  },
```

Refer to the following guides:

* Refer to the [Failed Tron transactions](https://docs.lmnl.app/reference/send-webhook-requests#failed-tron-transactions) section to learn more.
* [Transactions](https://docs.lmnl.app/docs/transactions#transaction-status-and-substatus)  for primary and secondary statuses.
* [History](https://docs.lmnl.app/docs/history) to learn about transaction history.

## Added Protocol Field in the Transaction Details Panel

<Image align="left" border={true} width="500px" src="https://files.readme.io/d47e3955d443977fe6fd7ff692345d02282c2b9a7b45b806b571277581e206f3-CleanShot_2026-01-08_at_17.33.15.png" className="border" />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

The **Transaction Details** panel now includes the **Protocol** name of the native coin or token transferred in a transaction in its metadata, improving user experience.\
Refer to [History](https://docs.lmnl.app/docs/history) to learn about the transaction details.

## Consistency in Reporting On-Chain Transaction Time

The `timestamp` field in the transaction **Webhooks** and **History** now reflects the on-chain timestamp of a transaction, accurately improving transaction reporting.
Refer to [History](https://docs.lmnl.app/docs/history) and [Transaction Webhooks](https://docs.lmnl.app/reference/transaction-webhooks) to learn more.

## Gas Station Required for Multisig Wallet Creation

With this release, **Multisig** wallet creation has the following enhancements:

* **Sprayer** wallets are used to fund **Tron Multisig** wallets during their creation. Ensure your **Tron** sprayer wallet has at least 120 TRX balance.
* **Gas Station** wallets are now used to fund **EVM-based Multisig** wallet creation. Ensure your Gas Station has a sufficient balance.

Refer to [this](https://docs.lmnl.app/docs/setup-multisig-cold-wallet) guide to create a multisig wallet.

# 🛠️ Resolved Issues

## Safe Link Accuracy Fix for Polygon Tokens

Fixed an issue where the **Safe** link during **Multisig** transaction initiation showed an inaccurate link for **Polygon** tokens. Now, the **Safe** link is accurately demonstrated.

## Account Statement Consistency Fix

Fixed inconsistent behavior where the **Account** statement was missing the destination and origin addresses columns. With this release, the fix is applied, helping with validation in [Reports](https://docs.lmnl.app/docs/reports).

## Stuck BCH Transaction Fix

Fixed an issue where **BCH (Bitcoin Cash)** wallet transactions were getting stuck by default due to global **Firewall** configurations. With this release, all **BCH** transactions now process the spendable balance seamlessly.

# ⊖︎ Deprecated

## Removed the `resData` object from Webhook Payload Request

With this release, the `resData` object has been removed from all supported webhook payload request bodies in **Vaults** as it was redundant.