🚀 What's New

Automatic Expiration for Failed Tron Transactions

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 section to learn more information about this feature.
• Transfer funds from the MPC wallet.
• Transfer funds from a multisig wallet.
• Refer to History to learn about transaction statuses.

Latest Versioning

Check out the latest versions of impacted applications:

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

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

Refer to the following guides:

• Refer to the Failed Tron transactions section to learn more.
• Transactions for primary and secondary statuses.
• History to learn about transaction history.

Added Protocol Field in the Transaction Details Panel

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

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.