Drift governance backlash widens
- Drift is facing governance aftershocks after a recent exploit, with users pressing questions about recovery mechanics and protocol transparency. - Protocol operators maintain Insurance Fund deposits are safe, but community criticism has focused on DIP-10 and clarity around remediation steps. - The episode turns a technical incident into a governance test, increasing market caution toward protocols that socialise losses. (ambcrypto.com)
1/ Drift’s latest backlash is no longer just about the April 1 exploit. It’s about who absorbs losses, how recovery will work, and whether governance is being used to ratify decisions after the fact. (drift.trade) 2/ What Drift has said publicly: on April 16, the protocol said it was working with law enforcement and third-party forensics firms, designing a “full user recovery” framework, and rebuilding the platform before relaunch. (drift.trade) 3/ The scale of the hole is central to the dispute. Drift said the April 16 recovery update was designed to address about $295 million in outstanding user losses over time as exchange revenue grows. (drift.trade) 4/ Drift also said it had secured proposed support from Tether and other partners: up to $127.5 million from Tether and $20 million from others, including a $100 million revenue-linked credit facility, an ecosystem grant, and loans to market makers. (drift.trade) 5/ The governance flashpoint is DIP-10. Reporting on the proposal says it would authorize Drift Foundation to convert remaining assets in the affected borrow/lend pool into USDT, then use the proceeds to seed a recovery pool for impacted users. (cryptotimes.io) 6/ Why that upset users: DIP-10 is described as a plan to sell residual pool assets, lock in a snapshot of claims, and reimburse over time. For critics, that raised the question of whether users were being asked to accept socialized losses through governance rather than via pre-understood rules. (cryptotimes.io) 7/ The snapshot mechanics matter. Reporting on DIP-10 says Drift would calculate affected balances using a snapshot taken when the protocol was paused on April 1, 2026, at 18:31:47 UTC. No further interest would accrue after that point. (cryptotimes.io) 8/ Drift’s defense is that direct token-by-token return is not feasible. The foundation’s position, as reported, is that the borrow/lend product operated as a shared liquidity pool, so remaining assets cannot be cleanly matched back to individual depositors. (cryptotimes.io) 9/ The Insurance Fund became the next pressure point. Drift’s own documentation says the Insurance Fund is the protocol’s “first backstop” for bankruptcies and AMM deficits, with stakers earning a share of revenue in return for taking that risk. (docs.drift.trade) 10/ That is why reassurance on Insurance Fund deposits was so important. AMBCrypto reported on May 21 that Drift said Insurance Fund deposits were not impacted by the exploit and would remain withdrawable after the protocol relaunches. (ambcrypto.com) 11/ Drift’s docs also show the limits of that reassurance. The Insurance Fund is designed to cover certain liabilities, but the docs say excess losses beyond allotted limits are handled through a “socialised loss mechanism.” That phrase is exactly why users are scrutinizing recovery language now. (docs.drift.trade) 12/ Another detail drawing attention: Insurance Fund staking is not instant-liquidity capital. Drift’s documentation says unstaking has a 13-day cooldown, and withdrawals can also be constrained when spot market utilization is high. (docs.drift.trade) 13/ So the governance issue is broader than “are IF deposits safe?” The harder question is whether protocol users fully understood where contractual risk ended, where governance discretion began, and how losses would be allocated after a crisis. That is an inference from Drift’s recovery plan, DIP-10 reporting, and Drift’s own Insurance Fund docs. (drift.trade) 14/ Drift has tried to answer the trust problem with process changes. Its April 16 update said relaunch would depend on two independent audits, from Ottersec and Asymmetric, and that it would introduce a new community-governed multisig for core protocol assets. (drift.trade) 15/ The next concrete markers are already on Drift’s own site: the protocol’s updates page lists “Recovery Plan for Affected Users” dated May 5, 2026, following the April 16 incident-recovery post. Until those recovery mechanics are clearer in public governance, the backlash is likely to stay focused on DIP-10, Insurance Fund boundaries, and who ultimately bears the losses. (drift.trade)