My current view on cross-chain is to ask first: who did you really trust this time "in the past"? Even with more orderly message passing like IBC, it's not magic. The chain itself needs to produce blocks normally, the light client/validator set must be reliable, relayers shouldn't slack off, channel parameters shouldn't be misconfigured, and the application layer still has to prevent replay attacks and timeouts... Basically, each layer involves trust, just laid out more transparently.

Recently, there have been bridge thefts and oracle price anomalies, so everyone is starting to "wait for confirmation." I understand that—taking a little more time is better than rushing in. What helps me stay calm is: before entering, write down an exit plan, and the same applies to cross-chain operations—how long without confirmation counts as failure, how to handle rollbacks, and only try a small amount at most. Anyway, I’d rather wait two more rounds than use my tuition to test someone else's system.