Just ran another cross-chain task on the subway, and I thought: a message/asset going "from A to B" actually involves more than one bridge.

IBC seems more "regulatory," but you still have to trust each chain's consensus, ensure the light client/verification logic is correct, have relayers willing to forward (and not go offline), and make sure the modules on the other chain don't upgrade and send you into a black hole...
In short, it's a series of components connected together, and if any link is loose, it could cause a failure.

Recently, the stacking of yields from staking/sharing security has been criticized as "nested dolls," which I can understand. Cross-chain is more like nested dolls: adding an extra layer of middleware means an extra trust point.
Anyway, my current approach is pretty crude: first decide who to trust, who takes the blame if something goes wrong, then determine if it's worth saving that little bit of time/fees.
For now, that's it. I'll note down this pitfall later.