🚀 What's New

Latest App Versions

Check out the latest versions of impacted applications:

Introducing /v2/transactions/submit API Reference

A new API reference, POST /api/v2/transactions/submit, is added to the Liminal Express SDK. Use this endpoint to submit a specific batch of pending transactions for a v2 MPC wallet (hot, deposit, or online cold wallet with a signer accessible via API) by sequenceId, instead of submitting every pending transaction on the wallet. For each transaction, the call assigns the on-chain nonce, refreshes the fee estimate, signs it, and submits it for processing. Not available for multisig v2 wallets or v1 wallets.

A response can report some sequenceIds as processed and others as failed within the same 200 response — a failed entry for one sequenceId does not mean the whole batch was rejected.

Refer to Submit transactions by sequence ID to learn more.

New transactionStatus Object Added to Transaction APIs in Express SDK

Transaction APIs in the Express SDK now return a transactionStatus object showing both the primary transaction status and a secondary sub-status. Previously, data.status returned only a single status type for a transaction.

Impacted API references:

• /api/wallet/transaction-status — Retrieve a transaction status v2
• /api/wallet/pending-transaction — Retrieve pending transactions v2

{
  "transactionStatus": {
    "legacyStatus": 1,
    "primaryStatus": "pending",
    "secondaryStatus": "awaiting_signatures"
  }
}

Refer to the Transactions guide to learn more about transaction status and sub-status.

Added a transactionStatus Object for Failed Webhook Responses in EVM Chains

Webhook responses for Send transactions on EVM chains now include the same transactionStatus object, showing the transaction's status type, primary status, and secondary sub-status.

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

Refer to the Send transaction webhooks guide to learn more.

Default Market Fee for Send-Many and Consolidation APIs (EVM)

Gas fees for EVM chains are now calculated using a centralized market quotation across transaction and consolidation APIs, giving more accurate fee rates. When feeLevel isn't explicitly defined, the API returns maxFeePerGas using the market-rate fee as the default method.

The default maxFeePerGas is calculated as:

maxFeePerGas = (baseFeePerGas × 2) + maxPriorityFeePerGas

maxPriorityFeePerGas is the base network tip fee × a priority fee multiplier of 1.5.

Refer to the Retrieve estimated gas fees and rates API to learn more.

RLUSD (XRP) and USDC (Stellar) Token Support for Send-Many Transactions API

MPC v1 hot wallets now support the RLUSD (Ripple USD) token on XRP and the USDC token on Stellar (XLM), in addition to existing native coin support, for the /wallet/send-many-transaction API.

This introduces the following fields on the wallet object:

• transactionType — transfer (default) or enableToken. Use "enableToken" as a one-time on-chain requirement before sending and receiving transaction requests normally.
• tokenOptions — a sibling field of transactionType, specifying tokenName (RLUSD or USDC) and tokenAddress.

Refer to the Create transaction requests API reference to learn more.

✨ Improvements

Automatic Rewards Claiming Enabled for ETH Staking (MPC)

Users can now automatically claim rewards from an ongoing ETH stake for MPC-based wallets. Earlier, rewards had to be claimed and withdrawn manually — now this happens automatically.

Refer to the Ethereum (ETH) staking guide to learn more.

Bug Fixes

Fixed IP Address Location Details in Email for Blocked API Requests

Earlier, the email sent when an API request was blocked due to an unconfigured EX_OUTBOUND IP address (i.e., an IP not whitelisted in the Express SDK) showed undefined for the geolocation details. Now, the email displays unavailable or N/A when a geolocation field can't be resolved.