I just brushed up on IBC and various messaging protocols, and the more I look at it, the more I think cross-chain is basically about "who do I trust." When transferring assets, it's not just about trusting the source chain and destination chain, but also trusting whether the proof/relay in the middle is functioning properly, whether the light client can keep up, and avoiding getting stuck during upgrades or downtime; further down, there are the bridge contracts, validators/multisig people, and even the front end and the route you click. Recently, some mainstream public chains are planning upgrades, and everyone in the group is guessing whether projects will move away. I'm more concerned about: making sure cross-chain messages aren't messed up before and after the upgrade, and that my assets don't stay stuck in "processing..." all night... Anyway, I can avoid using bridges if I want, and if I really need to cross, I prefer to choose ones with narrower trust assumptions.

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
  • Pinned