Lately, I keep seeing people confuse IBC / message passing / bridges, anyway, cross-chain stuff is basically "who do you trust to pass the message for you." Once a cross-chain transfer happens, you at least have to trust: that the source chain and target chain themselves don't have any issues; that the group running the relay/validation in the middle isn't lazy or malicious; that the message proof mechanism has no holes; and that the front end / contract you're using has the parameters written correctly. Many bridge accidents aren't because the chain itself was hacked, but because a component silently loosened somewhere in the process.

Recently, before some mainstream chains upgrade or maintain, everyone is guessing whether projects will move away. I'm more concerned about whether cross-chain messages will get stuck, replayed, or delayed during upgrades, causing a series of liquidations... No need to rush into a big rise or fall; first, check if the queue and validation set on the bridge side are abnormal, and don't get carried away by the "migration narrative."