First things first, I feel for LPs who got hit. I’ve already been hit once by hacks, including the multichain hack on Fantom, which still hurts and is a horrible outcome.
That said, I strongly oppose this proposal – not because of Beets or Sonic Labs as teams, but because of what it says about Sonic’s governance and incentives.
- The remaining airdrop budget was sold as ecosystem/growth capital. Turning ~27M S into a retroactive bailout for one protocol is a completely different mandate. If this passes, it’s hard to argue Sonic is chain-neutral in how it allocates shared resources.
- This was a DEX / pool design level failure, not a base-layer Sonic failure. Socializing that at the chain level sends the message: “If infra breaks, governance might plug the hole with community funds.” That’s a terrible precedent.
I want to be transparent: If something like this passes, it’s very hard for us to keep taking Sonic seriously as a credibly neutral, predictable environment. In that scenario, we would consider winding down our products on Sonic and focus on more serious chains.
Nothing personal against the teams – but on the idea itself, I’m firmly against and would encourage a No vote.
I’d also ask those supporting this: why is this more important than the Multichain hack? Shouldn’t compensating those victims come first?
Rafael – Origin