Ampleforth Proposal 54 canceled after wallet requests 98% of treasury USDC
In brief
- Proposal 54 sought 2.5 million USDC from Ampleforth's treasury, representing 98.5% of displayed reserves
- Delegator transferred concentrated voting power to proposer 19 minutes before proposal creation
- Proposal canceled on-chain before voting opened; zero votes cast
- No treasury loss or exploit occurred; governance process requires formal discussion before binding votes
Delegation and Proposal Timeline
The proposing wallet submitted the request soon after receiving concentrated delegated power. Address 0x38cA…24D8 delegated 87,238.5461 FORTH of voting power to the proposing wallet, and the proposal-creation transaction followed approximately 19 minutes later. The proposal's sole executable action directed the USDC to proposing wallet 0x730C…dd82.
The proposal author presented the payment as a retrospective grant for Observatory for SPOT, a public open-source analytics interface. Tally records show zero votes for the proposal, and the cancellation block preceded the scheduled voting-start block.
Cancellation Mechanism
On September 14, the same delegating address transferred 87,238.5461 FORTH away and then called cancel(54) about 14 minutes later. Ampleforth's governor code includes a route allowing cancellation when a proposer's prior-block voting power falls below the proposal threshold. This mechanism enabled the removal of the proposal after the voting-power delegation was reversed.
Governance Process and Outcome
A September 15, 2026 treasury dashboard snapshot showed approximately 2.54 million USDC, meaning the request would have depleted nearly all liquid stablecoin reserves. GoPlus Security's X account warned about the still-pending proposal shortly before cancellation and characterized it as an attack.
The verified record shows a canceled proposal and no treasury loss or executed exploit. Ampleforth's governance documentation describes a progression through discussion, formal proposal development, targeted discussion, optional offchain signaling and technical work before a final binding onchain vote. The canceled proposal bypassed these steps.
Frequently asked questions
How did one wallet gain enough voting power to propose a large treasury transfer?
Address 0x38cA…24D8 delegated 87,238.5461 FORTH of voting power to the proposing wallet 19 minutes before the proposal was created. This concentrated delegation gave the proposer enough power to submit a governance action without needing broad community support.
Why was Proposal 54 canceled?
The delegating address transferred its 87,238.5461 FORTH away and then called the cancel function 14 minutes later. Ampleforth's governor code allows cancellation when a proposer's prior-block voting power falls below the proposal threshold, which triggered after the delegation was reversed.
What should happen before an Ampleforth proposal reaches voting?
Ampleforth's governance documentation describes a progression through discussion, formal proposal development, targeted discussion, optional offchain signaling and technical work before a final binding onchain vote. Proposal 54 skipped these preliminary steps.
