Lately, I've seen people complain again about "still waiting for confirmation" on cross-chain bridges. I actually think this step shouldn't be skipped. Multi-signature, simply put, is a group of people pressing buttons together; no matter how many there are, they can't prevent the same set of risk control logic from making the same mistake. Oracles are more like mouths feeding prices and states; once the data source is biased, even if the bridge is more "automated," it just speeds up the mistake. Waiting for confirmation actually gives time for finality on the chain and for anomaly windows, not just to be slow. And I can also understand the criticism of on-chain data tools and tagging systems being laggy; once tags are misled, monitoring might look "safe," but that's just an illusion. I'm just a tech enthusiast who loves dissecting routing; anyway, I prefer to be slow when bridging, looking at multiple layers: who's signing, who's feeding, and whether it can be stopped if something goes wrong. That's all for now.