These days, I've been thinking about the IBC/message passing system again. The more I look at it, the more I realize that the question of "who to trust for cross-chain transactions" needs to be carefully considered first; otherwise, even if the returns are tempting, you won't sleep peacefully. To put it simply, there are many levels of trust involved: the source chain and target chain themselves must not have issues; the intermediaries responsible for forwarding/relaying the messages must not go offline or act maliciously; the verification logic of the light client/proof for this message must be correct; above that, how the application contract handles this message (whether replayed or with limits) matters, and finally, there's your own signature.

Recently, hardware wallets have been out of stock again, and phishing links are also on the rise... Before cross-chain transactions now, I first review the "components I need to trust" in my mind: avoid using bridges if possible, and if I must use them, I split the limits into layers and batches, preferring to go slower. Anyway, if the weeds in the garden aren't pulled out, they'll eventually grow into a disaster.