Recently, everyone has been talking about modularization and the DA layer, and developers are excitedly discussing it while users are mostly confused... Actually, don’t be intimidated by the terminology. I’ll focus on one main thread: data must first be "able to be stored and retrieved," then we talk about "how to queue," and finally "when to count."



Simply put, DA means: you publish transaction/status data, and others can verify that you haven't hidden anything. Once verified, ordering makes sense (who comes first or second affects the outcome, especially in front-running or sandwich attacks). Finality is about whether this transaction is truly settled and whether it might be reversed later. These three aspects each control a part of the process; don’t mix them into one confusing concept... I often get the relevance wrong too, but once this line of thinking is clarified, many "narratives" become less mysterious.
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