A multisignature treasury swap needs approval from several wallet owners before it can move tokens across chains. The key question is whether the wallet transaction has been executed on the source chain, because a proposed transaction alone has not started the swap.
Approvals and execution are separate stages
A multisignature wallet, or multisig, needs a set number of owners to approve a transaction. For example, a 2-of-3 treasury needs two valid signatures from its three owners. Those signatures can collect off-chain, meaning they are recorded without yet sending a transaction to the blockchain.
Once the threshold is met, someone still has to execute the wallet transaction on-chain. That execution spends source-chain gas and sends the swap request. If a proposal is pending with only one of two required approvals, the swap has not started; ask the missing signer to review the same transaction.
Check the transaction’s destination, token, amount, and nonce before signing. A nonce is the wallet’s transaction sequence number. If another transaction uses that number first, a proposal can become invalid or need to be rebuilt.
The source transaction starts a second, cross-chain process
After execution, look up the source-chain transaction hash in that chain’s block explorer. A confirmed transaction means the request reached the chain; it does not prove that the destination tokens have arrived. A cross-chain route may still need to wait for source-chain confirmation, a message relay, or a destination-chain transaction.
For example, imagine a treasury swaps 10,000 USDC on one chain for ETH on another. These are illustrative amounts. The multisig first approves and executes the source request; then the route must complete its destination step. An omnichain cross-chain transfers route puts that movement through one service, while the wallet approval and each chain’s processing remain distinct stages.
That distinction helps diagnose a “pending” status. If there is no source transaction hash, check wallet approvals and execution. If the source transaction succeeded but the destination transfer is still pending, check the route’s transaction status before taking action. Some routes use an intent: a signed request that a relayer, or third-party transaction sender, fulfills on the destination chain. Delays can occur between those steps.
Match the next action to the failure point
For an omnichain swap, start with the last confirmed event, not the wallet’s general activity label. Then use the relevant chain explorer and route status to decide what is safe to retry.
- Not enough signatures: Have the remaining owner check the transaction details and sign that proposal.
- Threshold met, no execution hash: Confirm that an owner executed the approved transaction and that the executor wallet has source-chain gas.
- Source transaction failed: Read the explorer’s failure reason. Check the nonce, gas, token balance, and whether the quote or request expired before building a replacement.
- Source transaction succeeded, destination missing: Keep the source hash and check the route’s status. Don’t submit a second swap unless the route confirms the first cannot complete.
In practice, record the Safe transaction hash, source-chain transaction hash, amount, and destination address for the treasury’s audit trail. For an omnichain transfer, a completed wallet approval is only the beginning; verify the destination receipt before treating the funds as available.