Today I translated an audit report for a re-staking project again, and saw a passage describing the punishment mechanism—it’s written pretty clearly and in detail, but as I translated I kept thinking: when many people discuss shared security, they only focus on stacking returns. To be honest, the risks are shared too. What you stack isn’t necessarily honey; it could also be a hidden chain-reaction outage risk. Recently, the air-drop season and point-earning tasks are everywhere. To counter Sybil attacks, everyone is doing “live-entity style” data farming, competing like it’s a job, but when people get anxious, they’re likely to miss those underlying logic.



In an anonymous group, there are guys who post screenshots every day showing auto re-compounding returns. I feel that before the core protocol logic has been fully worked out, this kind of compounding is more like a placebo. I’m not saying you shouldn’t do it—just don’t stack illusions.

That’s it for now.
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