[Executable] Treasury Flow Automation

We deployed the version from the exact commit hash that was audited by Cyfrin. We’ll always stick to the best practices possible on security (in that case meaning we would only deploy and use audited code), while also being aware of the time sensitivity of the situation.

The concerns Clowes addressed will be resolved. And we’ll be deploying a new version in the next weeks. It was already checked by Cyfrin and the new version address all the points. It’s not a critical vulnerability but it’s important to be addressed.

That said, the proposal passed and executed successfully. We have the first withdrawal going from the registrar controllers directly to the endowment!!

Next steps:

  • @kpk to calculate how much USDC we need to transfer in order to maintain 6 months of runway in the timelock
  • Execute the transfer ASAP so we don’t risk SPP streams being canceled and Labs can withdraw their stream
  • @kpk to include this routine each quarter, next run would be in the first weeks of July

Less coordination cost and capital getting yield sooner.

2 Likes

KPK swept ~4.9M USDC from endowment.ensdao.eth to wallet.ensdao.eth on April 23 to sustain operations through end of Q2. Transaction.

Starting in May, we will begin executing the 6-month runway sweeps established by the Treasury Flow Automation proposal. The runway calculation will use spending data from the ENS Steakhouse dashboard as the baseline. The primary goal is to ensure funding for large, known programs (ENS Labs, the Service Provider Program, Working Group budgets) remains uninterrupted.

Before finalizing the calculation by end of May, we will coordinate with the Meta-Governance Working Group to account for any spending changes that may follow from ongoing discussions around the DAO Retro, Working Group structures, the Service Provider Program, and a potential Foundation.

Beyond the projected runway, we remain available to execute additional transfers if funding needs change.

@Meta-Gov_Stewards

1 Like