Proposal requests 2.5M USDC from a timelock reported near 2.538M USDC; voting active through Sep. 16; no confirmed loss.
Proposal 54 requests a 2,500,000 USDC transfer from Ampleforth's treasury timelock to the proposer. The timelock was reported to hold about 2.538M USDC, making the request close to the full liquid USDC treasury.
Why it is a governance risk
Security monitors flagged the proposal because of the size of the request, the newly used proposer wallet and the economic relationship between governance thresholds and treasury value. The proposal threshold is 75,000 FORTH and quorum is 600,000 FORTH.
These facts do not prove malicious intent. The proposal describes the transfer as a completed-work grant. The risk is that governance can authorize a treasury-scale transfer if voting participation and delegation allow it.
Current status
Voting opened September 14 and is scheduled to close September 16. No confirmed treasury transfer or loss is established in the verified reporting used here.
Evidence Status
Confirmed / On-chain governance + monitoring: requested amount, treasury estimate, voting window and thresholds. Unproven: malicious intent, successful execution or loss.
Risk Assessment
High while the vote remains live.
What to Watch Next
Vote totals, delegation changes, cancellation/defeat/pass status, timelock queueing and official response.
FAQ
Is the event confirmed?
The core facts above are limited to the latest verified official, on-chain or reputable incident reporting.
Are community claims included as facts?
No. Community-only claims remain Community / Unverified.
Can the status change?
Yes. Recovery, exchange freezes, votes and liquidation execution can materially change the status.
Does an application exploit mean the base chain failed?
No. Application-layer and governance failures are separated from base-layer consensus.
What should be monitored next?
The event-specific recovery, execution, governance or compensation milestones listed above.