I’ve found that a lot of people still treat cross-chain as “just click a bridge and you’re done,” but the truth is: you’re packaging a chain of trust… Especially with IBC/message passing, it looks very “native,” but every cross-chain transfer at least requires that you trust: that neither side’s chain will “go rogue,” that the light client/verification logic isn’t written in a way that blows up, that the relayer won’t go offline or start rerouting things incorrectly, that the receiving contract on the other side doesn’t leave behind a backdoor, and that your frontend and routing don’t do anything sketchy. Last week, it was the third time I saw someone get wrecked by setting the slippage too high—while doing a cross-chain, they still got sandwiched in the middle. Honestly, that’s a double hit.

With modularization and the DA-layer narrative, developers are having a blast, and it’s totally normal for users to look confused: the more components you have, the more things you have to trust by default… Anyway, before I do any cross-chain transfer now, I check the path and the confirmation count first—if I can do one fewer cross-chain hop, I’ll do one fewer.