Recently, I saw someone say, "Using IBC is no longer a bridge and is safer," and I can't help but laugh... To be honest, when you do cross-chain, whether you call it a bridge or message passing, you're trusting a chain of components: the source chain/target chain not crashing or rolling back, the light client/verification logic not making mistakes, the relayers not causing trouble (at least not causing you to get stuck), and the most easily overlooked—how the application layer handles the awkward state of "receiving a message but assets haven't arrived / arrived halfway."


IBC is indeed more visually appealing than many multi-signature bridges, but if you really treat it as "trustless," you're digging your own grave.
By the way, I see the funding rates in the group are extreme; everyone is arguing about reversals or continuing to inflate the bubble. I only care more about whether cross-chain messages will queue during liquidations or congestion, and in the end, you'll have to take the blame yourself.
That's all for now.
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • Comment
  • Repost
  • Share
Comment
Add a comment
Add a comment
No comments