I got the transfer into the wallet I meant to use, not the first account my browser extension happened to show.
The catch is simple and expensive: a bridge can be working perfectly while you send funds to the wrong address on the destination chain. That was my earlier mistake. I assumed the account selected in the wallet popup was the account receiving the transfer. It was only the account approving it.
For this attempt, I treated the destination address as a separate field from the start. I opened the rhinobridge.app flow for a rhino bridge transfer, chose the networks, and stopped before approving anything. The amount was not the thing to check first; the receiving address was.
The check that fixed it
My wallet had two accounts. The extension displayed Account 1, while the address I wanted belonged to Account 2. I copied the intended address directly from Account 2, pasted it into a blank note, then compared it against the destination address shown in the bridge flow.
- Match the first six characters.
- Match the final six characters.
- Confirm the chain named beside that address.
I did this before the approval popup appeared. Once the popup arrived, I checked only that it was asking to use the same sending account and that the amount matched what I had entered. Those are two different jobs; mixing them up is how I missed the problem before.
What I would do again
I sent a small test amount first. The transfer completed to the intended destination, so I repeated the exact route with the remainder. I did not switch accounts, reopen the wallet, or edit the destination between the test and the second transfer.
That is the whole routine now: choose the route, paste the receiving address from the actual destination account, compare twelve visible characters, then test. The bridge step was not the fragile part. My assumption about which wallet address mattered was.