These days, I've been looking into the pitfalls of cross-chain bridges again. To put it simply, many bridges appear to be "decentralized," but at the core, they still rely on multi-signature wallets plus a set of oracles or observers feeding messages. Fewer signers make it easier for social engineers or insiders to take over everything, while more signers turn into governance issues like "who manages the keys and how to replace them." Anyway, you have to keep an eye on the structure.

Some people complain that "waiting for confirmation" is too slow and want to take shortcuts. In fact, those few minutes or hours are used to wait for more solid, irreversible on-chain confirmations. Otherwise, if you reorganize or the oracle reports and then changes, the bridge might release funds prematurely. You think you're saving time, but you're actually gambling with luck.

Modularization and DA development have excited many developers this round, but users are genuinely confused: where to put the data, who guarantees its availability... In the end, it all comes back to the same old issues on the bridge. We'll talk about this again next time.