The word "modularization" sounds very grand, but for ordinary users, it boils down to two things: Is clicking confirm faster and cheaper, and who takes the blame if something goes wrong? After separating the execution layer and data layer, the experience might indeed be a bit smoother, but the trust chain is also longer, and in the end, users might actually perceive "more confirmation waiting"... Recently, when bridges are hacked or oracles report errors, the collective consensus to hold steady is more real than any roadmap. On-chain indicators are also quite honest: TVL will migrate, active addresses will disperse, but if real revenue doesn't pick up, the hype is basically just shell swapping. Anyway, I now look at how projects handle anomalies first, rather than how they talk about modularization.

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