Recently, the proposals for cross-chain bridges have started to stir up again. Everyone is complaining that the "waiting for confirmation" line on the interface is too slow. Frankly, that is to give time for multi-signature and oracles to breathe. Multi-signature is not a deity; the signers also sleep. Oracles are not automatic truth machines; price feeds, rollbacks, and reorganizations all require someone to monitor. If you think it's slow, it's actually helping you extend the "window of potential issues" a little bit.



What's even more amusing is that some people are shouting about re-staking, sharing security, and stacking yields, with nested layers flying everywhere, while at the same time complaining that the bridge's confirmation steps are cumbersome... My current approach is very simple: split the cross-chain amount into smaller parts, wait if you can, and during voting, just ask, "How to change signing rights, who will take the blame for the oracle," anyway, if the bridge gets hacked once, the profit screenshots all become material for meeting minutes.
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
  • Pin