Recently, I've been seeing L2 projects arguing over TPS, fees, and ecosystem subsidies, causing quite a stir, but I actually want to first see if "that pond of water" underneath is stable. Beginners wanting to judge credibility shouldn't just focus on those few logos in the audit reports: first, check GitHub to see if it's maintained by someone long-term, whether issues are being responded to, and if upgrades are suddenly major changes without explanation; don't blindly trust audits either, focus on the scope of the audit and whether known issues have been genuinely fixed or re-audited, otherwise it's just "reviewed but not fixed." Then there's multi-signature upgrades—who are the signers, how strict are the thresholds, are there delays or emergency switches, and whether permissions are concentrated enough to change logic with a single key... honestly, these are the hidden currents.


My mom asked me a couple of days ago, "If there's an audit, is it safe?" I can only say half of it: an audit is like a health check, it can find problems, but it doesn't mean you'll never get sick, especially when the project is upgrading daily. Anyway, I tend to raise a question in my mind when I see permissions that are too broad and there's no time to lock them down.
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