Honestly, the first time I heard the word “modular,” I felt like rolling my eyes: can changing the structure really rescue the user experience? But recently I’ve really had an itch to go scrutinize the fees on a few chains and the block/transaction ordering. The reason is simple—when I see everyone arguing about concepts and flying into keyword wars, I just want to see whether, in the end, some unfortunate terminal user like me ends up paying the cost.



For ordinary users, what truly changes is probably just two things: first, whether it’s “stable in terms of whether it’s fast/usable and whether it’s expensive or not,” so you’re not smooth today and then crowded tomorrow, to the point you start doubting life; second, that hopping across should stop feeling like you’re playing an obstacle course—one asset bridge, one confirmation, and then another round of multi-signatures… Anyway, the more steps there are, the more I want to complain. If modular can move execution to cheaper places and make settlement more reliable, then I admit it’s useful. But if it only adds a few extra layers of “middleware” and the gas bills are still outrageous, then don’t blame me for being blunt.

And lately, with all that “yield stacking” around re-staking and shared security—honestly, it’s pretty much like nesting dolls: it looks like you can earn, but when something goes wrong, who actually has to cover it? Don’t end up relying on stacking for security and fees; otherwise users will just have to endure the experience. That’s it for now—I’ll keep staring at the mempool and getting angry.
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