Swap Pending on Avalanche? How Deadlines Limit Late Execution

A destination minimum deposit is the smallest amount a receiving service will credit after a crypto transfer. The key condition is where you send the bridged tokens: an exchange may enforce a minimum, while a wallet you control usually does not.

• Check the exact asset, network, address, and minimum on the receiving service.
• Compare the amount expected to arrive—not the amount you start with—to that minimum.
• Leave room for fees and any destination-network costs before you bridge.

What minimum do you need to meet?

Start on the receiving service’s deposit screen, and select the exact coin and network you plan to use. Record the minimum shown there, along with the deposit address and any memo or tag it requires. A minimum can differ between networks even when the token has the same name.

This minimum is usually a rule for crediting an exchange account, not a universal blockchain rule. For example, an exchange might show a minimum of 10 units of a token on one network and a different amount on another; use the live figure on your own deposit screen, not a number from an old article. Kraken’s deposit guidance also cautions that a deposit below the listed minimum may not be credited.

If you are sending to your own wallet, there may be no exchange-style deposit threshold. You still need the correct token on the correct network, and some networks or token types require a small amount of native currency for account setup or later transactions. That is separate from the exchange’s minimum.

How much will arrive after a bridge?

Compare the receiving service’s minimum with the amount expected at the destination, after any deductions shown in the bridge quote. A bridge transfer moves a supported asset from one blockchain to another; the source transaction fee is generally paid separately in the source network’s native coin. Depending on the route, the displayed output can also reflect a bridge fee, a swap, or a destination execution cost.

For instance, suppose your exchange requires at least 20 tokens, and a bridge quote says you will receive 20.3. That leaves only 0.3 tokens of headroom. If the quote changes before you confirm, or a destination cost is deducted from the token amount, the deposit could fall short. Choose a buffer that suits the quote and route rather than aiming to land exactly on the minimum.

When comparing routes in Portal Bridge, use the quoted destination amount and inspect the fee details before confirming. If you need a fuller breakdown of what affects the cost for your route, see Portal Bridge transfer fees while deciding whether the expected arrival leaves enough margin.

What should you check before sending?

Use this checklist before approving the source transaction:

1. Confirm the receiving service supports both the token and the destination network. A token with the same ticker can be a different asset or token contract on another chain.
2. Copy the deposit address from the receiving service’s deposit screen, and check whether it also requires a memo or tag. A correct address on the wrong network can still result in a failed or unrecoverable deposit.
3. Check that the amount expected after the bridge is above the current minimum, with some margin.
4. Check whether the receiving network needs native currency for a token account or future transactions. A bridged token balance does not automatically provide that gas currency.
5. Review the final route, destination asset, amount, and address in the bridge interface before signing.

Gas is the fee paid to have a transaction processed on a blockchain. Ethereum.org’s explanation of gas is useful here: a token balance and the native currency used to pay transaction fees are different things. A transfer can deliver the token successfully and still leave you unable to move it later if you have no destination gas.

What if the amount is too small?

If the expected arrival is below the displayed minimum, pause and change the plan before signing. You can increase the amount, choose a supported network with a lower minimum if the total route cost makes sense, or send to a self-custody wallet first if you understand the extra steps. A second transfer may mean paying another source fee, and combining small amounts later does not guarantee an exchange will credit the first deposit.

After a transfer, check its status in the bridge interface and use the transaction details or Wormhole Explorer to inspect the on-chain progress. If it is confirmed on the destination but the exchange balance has not updated, compare the received amount, network, token, and any required memo against the deposit instructions, then contact the exchange with the transaction ID. A below-minimum deposit may need the exchange’s support team; do not assume another transfer will automatically recover it.

For a first transfer, the practical finish line is a destination amount above the receiving service’s current threshold, sent to its exact network and address with any required tag. Decide differently if the deposit screen changes the minimum, the route quote leaves too little margin, or the receiving service does not support that bridged version of the token; in those cases, choose another supported route or wait until you can send enough.