I recently did my third IBC-related task and realized that cross-chain isn't just a matter of clicking "transfer" and it's done... To be honest, you have to trust: both chains shouldn't be down at the same time; someone needs to be actively handling the message passing (relayer) and not just pretending to be dead; the verification proof mechanism shouldn't be bypassed; and the frontend/router shouldn't point you to strange "bridges." Some bridges also require additional trust in multi-signatures, oracles, or custodians, which broadens the trust assumptions. Now, with staking and shared security that stack yields and get criticized as "nested dolls," I can understand. Security layered on top of security—who's ultimately responsible for the backing... Anyway, I approach tasks with the worst-case scenario in mind: avoid using bridges if possible, go small first if you can, and keep updating my list of pitfalls.