HypernativeLabs(@HypernativeLabs ):The wallet that can pause your protocol should never be the wallet that can upgrade it. @Pybast, CTO of @Corkprotocol, walked through this at the Rekt Security Summit in Cannes. Giving Hypernative the pause role makes sense for rapid response. But if that role also carries upgrade permissions, you have introduced a new attack vector instead of closing one. The same logic applies to unpause. If the key that unpauses your protocol gets exfiltrated, an attacker can trigger a pause, wait, unpause, and exploit again. These are governance design decisions that need to happen before you integrate any security tooling. Learn more at

2026.05.13 17:02

The wallet that can pause your protocol should never be the wallet that can upgrade it. @Pybast, CTO of @Corkprotocol, walked through this at the Rekt Security Summit in Cannes. Giving Hypernative the pause role makes sense for rapid response. But if that role also carries upgrade permissions, you have introduced a new attack vector instead of closing one. The same logic applies to unpause. If the key that unpauses your protocol gets exfiltrated, an attacker can trigger a pause, wait, unpause, and exploit again. These are governance design decisions that need to happen before you integrate any security tooling. Learn more at