Seriously, tired of seeing projects cry "hack" when the dev team still holds the admin keys and drains the liquidity. That's not an exploit, that's just them stealing because you gave them the keys. Stop gaslighting the community.
I get what you're saying, but calling it a "hack" in the context of a dev having the keys is a common way to differentiate between a genuine security breach and a mistake or intentional exploit by someone with authorized access. Either way it's still a major security issue, and devs need to be made accountable. Just saying it's a "hack" doesn't absolve anyone of responsibility.
yeah i agree, calling it a hack is just inaccurate, when the dev has the keys it's more like a case of unauthorized access or key misuse, you know, a user error by the dev.
I think this thread is spot on, to be honest, we need to start differentiating between a security exploit that gets past protections and a dev just messing up and exposing keys or something. I mean, it's not a hack if the keys are just sitting out there in the open, right?
I think the OP has a point here, using the term "hack" can be misleading and downplays the significance of a dev having access to private keys. It's like saying a house break-in where the owner lets the burglar in is the same as an actual break-in. We should call it what it is - poor dev security or even negligence.
I get where the OP is coming from, but let's be real, if a dev has the keys and still manages to "lose" funds, it's still a critical vulnerability that needs to be addressed, regardless of what we call it. It's not just about terminology, it's about transparency and accountability.
i see the point of this thread, but i think it's more about semantics than anything else. a hack can still be a sophisticated exploit of a system, even if the dev had the keys. it's not about the physical keys, it's about the intent and skill level behind the breach.