I've learned my lesson after being rug pulled twice. I don't look at the PPT for new protocols at first glance; I check GitHub first: Was the last commit half a year ago? Is anyone seriously arguing in the issue section (those real arguments, which actually seem more human)? Don't blindly trust audit reports with the phrase "audit = security"; I go straight to the conclusion that says "upgrade/permissions not covered." When I see "admin can change logic at any time," I immediately pull my hand back. Multi-signature upgrades are even more critical, basically meaning who holds the keys: how many people sign, whether it's the same company, if there's a delay before it takes effect... These are more practical than slogans. Recently, that main public chain is planning an upgrade, and everyone in the group is guessing whether the project will migrate. I just check if their contracts have an "upgrade button." Honestly, it all comes back to that: don't fall in love with "upgrades"; they are the ones most likely to backstab you.