Recently, I've been looking into cross-chain bridge risks again, and the more I look, the more I feel that "waiting for confirmation" is seriously underestimated. Many people focus on transaction speed, but what's really important is who is signing on the multi-signature on the bridge side, how arbitrarily the signature threshold is set; plus, with oracle errors or manipulation, everything may look normal on-chain, but the bridge itself could already be smoking. Anyway, I now prefer to be slower, wait for a few more confirmation rounds, at least to avoid half of the pitfalls of "rollback/reorganization/delayed price feeds."

By the way, I also understand why some people have recently complained about the lag of on-chain data tools and tagging systems, or even being misled: what you see as "a certain address is very safe/a certain bridge is stable" might be a conclusion from yesterday. Today, if the signers change or permissions are altered, you might not even know. There are many tutorials, but I prefer those that can be verified through reproduction: how to check changes in multi-signature members, whether permission upgrades have a timelock, whether the oracle data sources and fallback logic are clearly written... For now, slow is fast.