Skip to content
SAI Wallet

FAQ

Below are common questions and reasons why an operation may not complete immediately. In most cases, the problem is not with the application, but with the fact that one of the workflow steps has not yet been confirmed by the network, not delivered to the target network, or rejected by execution rules.

For a general scheme of steps, see Cross-chain workflow.

Where to check what exactly happened

Check three things:

  • the step where the operation stopped (by status in UI)
  • txHash in the source network (if the transaction has already been sent)
  • network and asset with which the operation was performed (contract address and decimals are important for tokens)
Why there is not enough network fee

Reason: there is no native token of the network on the address to pay for gas.

What to do:

  • top up the native token of the network (e.g., ETH for Ethereum, TRX for Tron)
  • repeat the operation
  • if the operation is cross-chain, make sure there is gas in the network where the current step is executed
Why Approve is required and what to do with it

Reason: for ERC-20 tokens, the contract needs permission (allowance) to withdraw.

What to do:

  • send the Approve transaction and wait for confirmation
  • after confirmation, repeat the main step
  • if Approve was already done, check that the allowance is sufficient and the correct spender is specified
Why swap was rejected due to slippage

Reason: the price changed more than the slippage allows, or the deadline expired.

What to do:

  • increase slippage within reasonable limits
  • repeat the operation when liquidity is more stable
  • for large amounts, consider splitting into several exchanges
Why there is a transaction in the source network but no result in the target network

Reason: the cross-chain step has not yet been delivered or finalized. This can take time depending on the protocol and network load.

What to do:

  • wait and refresh the status
  • make sure the txHash in the source network is confirmed
  • if there is a messageId, use it to check delivery with the provider (if such a screen is provided)

Context on the messaging layer is described in the section Messaging and Alternatives.

Why balance or position did not update immediately

Reason: RPC or indexer delay, temporary discrepancies between data sources.

What to do:

  • refresh the screen or restart the application
  • check the state via explorer (txHash)
  • if the problem repeats, this is a signal of RPC provider or indexer instability
Why the asset is displayed incorrectly (network, contract, decimals)

Reason: token parameters are incorrectly defined or the wrong contract is selected.

What to do:

  • double-check the network
  • double-check the contract address
  • double-check decimals if the token was added manually
What to send if support is needed

To quickly reproduce the problem, the following is sufficient:

  • network and asset
  • wallet address
  • txHash (and messageId, if available)
  • approximate operation time
  • screenshot of status in UI and description of what was expected