Rhino Bridge exposes two related operations that can look similar in a wallet but produce different outcomes. A bridge-only transaction moves the same supported token between networks. A bridge-and-swap transaction changes both the network and the token, using external swap aggregation as part of the route.
The Rhino Bridge route options let a reader verify which of these two operations is currently available for a specific pair.
Understanding that split helps users read quotes correctly and gives developers a clearer model of the transaction lifecycle.
Bridge-only: preserve the asset
In a bridge-only route, the input token and output token are the same supported asset. Rhino.fi’s supported-chain documentation uses USDT from Tron to Polygon as an example because USDT is supported on both networks.
The simplified sequence is:
- Verify that the same token is supported on both chains.
- Request and review a route quote.
- Commit the quote.
- Submit the source-chain deposit transaction.
- Track processing and destination settlement.
“Same token” should still be interpreted carefully. The destination token is a specific contract or native asset representation, not an abstract ticker. Applications may distinguish native and bridged versions even when wallets display similar symbols.
Bridge-and-swap: change the asset and chain
Rhino.fi’s SDK guide says cross-chain swaps use external swap aggregators. The user supplies a tokenIn and tokenOut, and Rhino.fi handles the coordinated swap and bridge flow before sending the resulting asset to the destination recipient.
This route introduces additional quote fields:
- the amount of the input token paid;
- the USD value of the input;
- the minimum destination amount;
- the USD value of that minimum;
- reference prices for the input and output tokens.
The minimum received amount is the important protection. It defines the lowest quoted output the transaction is prepared to accept after accounting for slippage. It is not a promise that market conditions will remain unchanged indefinitely; quotes expire.
What happens when a swap fails
Rhino.fi documents a refund path for failed swaps. The SDK may report a SwapFailed error with the refund chain, token, amount, and transaction hash. Status updates progress from swap-failed to failed-swap-refunded once the refund is processed.
This is why a missing destination balance should not immediately be described as “lost.” First distinguish a pending bridge, a failed swap awaiting refund, a completed refund on the source chain, and a completed destination settlement. Each state points to different on-chain evidence.
Which route should a user choose?
Use bridge-only when the destination accepts the same token representation and preserving the asset is the priority. Consider bridge-and-swap when the destination explicitly requires a different supported token and the combined quote is preferable to performing a separate swap.
The Rhino Bridge route options provide the live operational check. Confirm the source token, output token, networks, recipient, minimum received amount, and quote expiry before signing.
A technical boundary worth remembering
The source-chain transaction and destination settlement are distinct events. A wallet may show the first as successful while the route is still being processed. Rhino.fi’s status documentation uses a bridge or quote identifier to retrieve progress, while chain explorers independently show the source and destination transactions.
For accurate troubleshooting, preserve all three references when available: the source hash, bridge identifier, and destination hash. That evidence is much more useful than a screenshot of a wallet balance.
How does a bridge-only Rhino route work?
A bridge-only route accepts a supported token on the source chain and delivers the same supported token on the destination chain. Both networks must support that asset, and the recipient must accept the exact destination representation.
How does a Rhino bridge-and-swap route work?
A bridge-and-swap route changes both chain and token within one coordinated flow. Rhino.fi documents input and output assets, a minimum received amount, and external swap aggregation as part of this route type.
What can cause a bridge-and-swap route to fail?
Rhino.fi identifies market volatility as a common reason a swap can fail. Its SDK documentation describes a refund path and status metadata rather than treating a failed swap as completed destination settlement.
Which identifier is most useful for tracking?
Keep both the source transaction hash and the quote or bridge ID. The source hash proves the deposit action, while Rhino.fi status data and a destination or refund hash identify the later outcome.
Technical behavior assessed from Rhino.fi documentation on July 16, 2026.
Top comments (0)