The third time I hear people talk about "data availability / ordering / finality" as if it's some kind of mysticism... I'm going to focus on one main point now: who do you trust to decide the "sequence," and whether it ultimately fails or not. DA, simply put, is "whether others can access the raw data for verification"; ordering is "who can cut in line"; finality is "whether you're willing to accept that it's already over." Many governance discussions argue over terminology, but in the end, it all comes down to whether to shift trust from one place to another. Recently, the stacking of benefits in pledge/sharing security systems has been criticized as a copycat scheme, which I can understand: packaging "finality" as multi-layered returns sounds appealing, but if something goes wrong, the person who takes the blame will immediately quiet down. Anyway, my microphone is still off, and I just want to ask: when problems occur, how long do you plan to make users wait before considering it "final"?

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