Governance can now pull funds from one strategy into Controller
Controller 1.1.0 is active on mainnet, letting the admin timelock move a specific strategy's funds back into Controller for strategy migrations.
- Funds always return to Controller; governance cannot send them to any other address.
- The Controller proxy address stays the same.
- Keeper access remains available; SECURITY gains no new permission.
Details & sources
Controller 1.1.0 activated
Executed on mainnet. Upgraded the Controller proxy to 1.1.0. The admin timelock can now call
withdrawFromStrategy alongside the keeper, providing a governed path to move a specific strategy's
funds back into Controller for migration. The function has no recipient parameter: StrategyManager
always withdraws to the Controller, so governance cannot transfer strategy funds to any other address.
SECURITY does not gain that permission. The proxy address remains unchanged.
Evidence: contracts #52, governance 018 payload, and execution receipt, block 26,176,319, 12:13:23 UTC. The receipt contains the implementation upgrade and timelock execution events. The proposal's older Scheduled wording predates this execution.