Over the past couple of days, while browsing on-chain exhibits, I happened to click into a few cross-chain bridge pages. The UI was designed like a retro collage, and it actually looked pretty nice—until I thought about all the multi-signature setups and oracles behind it, and I instantly calmed down. Put simply, with something like a bridge, when things go wrong, it’s rarely because “the code was written incorrectly.” More often, it’s because of the people signing, the people providing—or feeding—the data, and that stretch of time when you think the funds have already arrived but they’re still on the way.

I used to find “waiting for confirmation” annoying, but now I think those few minutes are for cooling myself down. If it hasn’t been confirmed, don’t rush to keep stacking operations on another chain—especially not lately, with that whole criticized “re-staking and shared security” package, like nested doll after nested doll. Watching it, I feel a bit uneasy too: the higher the yields you stack, the more steps there are. And once the bridge chokes your process, everything gets stuck.

These days, I’m more inclined to move small amounts slowly. I’d rather wait a bit longer than bet that nobody in the multi-signature group will suddenly go offline, or that the oracle won’t give you some absurdly ridiculous quote. For now, that’s it.