When you are still at the checklist
Before signing, nothing has moved, so you can change the route, amount, wallet, or cancel the attempt.
- Confirm the source network, destination network, token, amount, and recipient address.
- Keep native gas on the source chain for the deposit and on the destination chain for later use.
- Compare the displayed fee, exchange rate, minimum received, and estimated completion time.
- Check that the token contract and connected wallet are the ones you intended.
If you need to know what the service actually controls
Rhino Bridge’s cross-chain interface selects a route, but the underlying bridge protocol executes the transfer. Rhino Bridge controls the interface and routing request; the selected bridge organization or protocol controls its contracts, liquidity, messaging, and settlement rules. The source and destination networks’ validators control whether transactions are accepted and finalized. Your wallet controls the private key and signing decision.
A bridge is simply infrastructure for moving assets between networks: Ethereum.org defines it as “used to transfer assets from one blockchain network to another.”
Once the source transaction is signed
I walk through the flow in this order because the first irreversible point is easy to miss.
- Your wallet signs an approval, deposit, or swap transaction.
- Until it is submitted, you can reject it. After submission, you may still be able to speed up or replace a pending transaction, depending on the wallet and network.
- Once the source transaction is confirmed, the asset has been committed to the selected route. You cannot recall it through Rhino Bridge.
- The underlying protocol then completes its destination-side action. A delay is not automatically a failure; it may reflect confirmations, liquidity, messaging, or proof processing.
When “gas” appears in the confirmation
Gas means the blockchain fee for computation. It is paid even when a transaction fails, so rejecting a wallet prompt costs nothing, while a submitted failed transaction may still cost gas.
After the destination leg should be complete
Verify the source and destination transaction hashes in the relevant block explorers. Check the destination wallet, token contract, balance, and network—not merely the application status. If the source is final but the destination is missing, contact the underlying bridge operator with both hashes; do not submit a second transfer unless the route explicitly requires recovery.
When the question is whether it can be undone
A rejected prompt, unsubmitted quote, or pending replaceable transaction may still be undone. A confirmed source transfer, wrong recipient, wrong network, or finalized destination transaction generally cannot. In short: treat every signature as permission to begin, and every confirmation as permanent.