Aibai is a good fit for sending crypto only when it supports both networks and delivers the token you need. A cross-chain bridge moves value between separate blockchain networks. Before sending, compare the amount arriving, the full cost, the wait, and who can release the funds.
The route must reach the right network
A usable route starts on the network holding your crypto and ends on the network your recipient accepts. Your wallet may show a token name without making its network obvious. Open the token details and check the network before choosing a route.
Say you hold USDC on one network and need USDC for an app on Solana. For example, the Aibai cross-chain bridge qualifies for that transfer only if its quoted route supports your starting network and Solana. Check Aibai’s listed token pair as well; support for both networks alone does not mean that pair is available.
Enter the receiving wallet address for the destination network. Check its first and last characters against the address shown in your wallet, then check them again before signing. A valid address on the wrong network can leave funds somewhere the recipient cannot use them.
The token received matters as much as its name
The receiving token must be the version your wallet, app, or recipient expects. Two tokens can share the name USDC yet have different issuers or token addresses. A token address is the identifier that tells a network exactly which token it is.
A bridge may lock your original tokens in a smart contract, which is code that holds and moves funds. It then issues a wrapped token, a bridge-backed copy, on the destination network. Another route may pay you from a pool of tokens already there, or remove tokens on one network and issue them on another.
That difference decides what you can do next. If an app accepts issuer-backed USDC but the route delivers a wrapped version, the balance may appear in your wallet and still be unusable there. Check the receiving token’s address against the address published by the app or token issuer. Check an Aibai route’s stated output token before treating its quote as a match.
Also check whether the route changes tokens. Moving USDT on one network and receiving USDC on Solana includes an exchange as well as a bridge transfer. The exchange rate can change the amount received, even when the transfer itself works as expected.
The amount received shows the practical cost
Compare valid routes by the token amount you will receive, then add any fees paid outside that quote. A displayed bridge fee is only one possible charge. The full cost can include:
-
Source network gas: the fee paid to record the outgoing transaction.
-
A bridge fee: a fixed charge or a share of the amount sent.
-
An exchange cost: the price difference when the route changes tokens.
-
Destination gas: a fee you may pay to claim or later use the tokens.
For example, say a quote turns 1,000 USDC sent into 997 USDC received, while your wallet shows $2 in source gas. That is about $5 in total cost, or 0.5% of the amount sent. Compare Aibai bridge fees using the same sending amount and receiving token; otherwise, the quotes measure different jobs.
Time also belongs in the comparison. The source transaction must be confirmed before the bridge can act on it. Some routes then wait for finality, meaning the source network has settled enough that the transaction should not be reversed. Available tokens in a destination pool and network traffic can add further delays.
Use the route’s current time estimate as an estimate, not a deadline. If you need the funds for a payment soon, allow time for both the bridge and your next transaction. Solana documentation lists a base fee of 0.000005 SOL per signature, with possible extra priority fees. That small network fee does not tell you the full bridge cost.
The security model decides who you trust
Before signing, find out who or what confirms the transfer and releases the destination tokens. Ethereum.org describes bridges that rely on outside verifiers and bridges that rely more directly on the connected networks. Each design has different failure points. Look for a clear explanation of the route’s contracts, operators, and any controls that can pause transfers.
Check the transaction your wallet asks you to sign. An approval gives a smart contract permission to spend a token; some approvals have no spending limit. Set a limit close to the amount you are sending when your wallet allows it. A transfer signature is a separate step, so an approval alone does not mean the bridge has sent anything.
For a first Aibai transfer, send a small test amount that still meets the route’s minimum. Wait until the expected token appears on the destination network, then send the rest. Save the transaction ID, the unique record of the outgoing payment, and use it to follow the transfer’s status. Make sure you have the destination network’s fee token before planning to move the funds again.
FAQ
Can I cancel a bridge transfer after signing?
Once the outgoing transaction is confirmed, you usually cannot undo that blockchain payment. A route may offer a refund if its later step fails, but the conditions and wait vary. Check the route’s status using your transaction ID before sending anything again. A second payment can create a second transfer.
Why are the tokens missing from my wallet?
First check that your wallet is showing the destination network and the exact receiving token. Some wallets do not display a new token until you add its verified token address. Then check the bridge status and destination transaction record. If the source payment succeeded but the destination step is pending, follow the route’s claim or support process.