ACI Is Leaving Aave
01Summary
ACI is departing the Aave DAO and requests cancellation of their GHO stream (ID 100070) with a lump sum transfer covering 120 days of remaining obligations to treasury.aci.eth, with the unstreamed balance returning to the Collector. This ensures ACI can complete their wind-down transition without depending on governance decisions controlled by a single voting entity.
- Type
- treasury allocation
Key changes
- Withdraw accrued unclaimed balance from stream 100070 to treasury.aci.eth(medium)
- Cancel GHO stream ID 100070, returning unstreamed portion to Aave Collector(high)
- Transfer 120 days worth of stream value from Collector to treasury.aci.eth as lump sum(high)
Notable concerns
- ACI cites governance concentration risk, stating a single entity holds enough voting power to cancel streams unilaterally
- ACI threatens immediate cessation of all activity and self-termination of obligations if proposal fails
- Lump sum conversion requested to protect against future governance decisions outside ACI's control
- Original service contract and stream run through November 8, 2026 but acceleration to 120-day wind-down is requested
Generated by Kvorum
02Description
Simple Summary
Cancel ACI’s GHO stream (ID 100070) on the Aave Collector and transfer 120 days worth of stream to treasury.aci.eth. The remaining balance returns to the Collector.
ACI is departing the Aave DAO. The full context is in our departure post.
Motivation
ACI is leaving the Aave DAO. We’re not disappearing overnight. The plan is a four-month wind-down: continue governance activity, implement outstanding commitments, document every system, transfer every tool, and give successor service providers enough context to pick up where we left off.
ACI’s service contract and stream 100070 both run through November 8, 2026. We’re accelerating the exit to 120 days. This proposal requests only what covers that period, not the full remaining stream. The rest goes back to the DAO treasury. The question is whether we can count on the stream staying active while we do the work.
The AWW Temp Check demonstrated that a single entity holds enough voting power to pass its own budget proposals over community opposition. That same voting power could cancel any active stream at any time. We don’t consider the current governance process decentralized enough to guarantee that existing commitments will be honored.
Converting the stream to a lump sum is the only way to ensure ACI can deliver a seamless transition without depending on a process where the outcome is controlled by one party.
Specification
Contract: Aave V3 Ethereum Collector (0x464C71f6c2F760DdA6093dCB91C24c39e5d6e18c)
Stream ID: 100070
Token: aEthLidoGHO (0x18eFE565A5373f430e2f809b97De30335B3ad96A)
Recipient: treasury.aci.eth (0x55Ac902cb75cC15288D473ed8E3E185a75b3f330)
Payload actions:
- Withdraw accrued unclaimed balance from stream 100070 to
treasury.aci.eth - Cancel stream 100070 (unstreamed portion returns to Collector)
- Transfer 120 days worth of stream from Collector to
treasury.aci.eth
The exact amounts will be calculated at payload creation time based on the stream state at that block.
If this proposal fails
If the DAO rejects this AIP, we’ll treat it as a signal that the protocol doesn’t intend to honor its commitments to ACI. In that case we’ll cease all activity immediately, cut our own stream and consider our obligations terminated.
That’s not the outcome we want. We’re professionals. We want a graceful wind-down that benefits Aave users and leaves every system we built in good hands. This AIP makes it possible.
References
- Implementation: AaveV3Ethereum
- Tests: AaveV3Ethereum
- Discussion
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The decoded on-chain action is a single, argument-less call to execute() on an external payload contract. This is the standard Aave governance execution pattern: the proposal itself only triggers a delegatecall into a pre-deployed, audited payload contract (referenced in the description's 'Implementation' link), and the granular logic (withdraw accrued balance, cancel stream 100070, transfer 120 days worth to treasury.aci.eth, return remainder to Collector) lives inside that contract's code rather than being visible as separate decoded calldata rows. Because the flat decoded action gives no arguments or sub-calls to inspect, there is no way to directly verify the specific stream ID, recipient address, or 120-day duration against calldata values — but there is also nothing in the decoded action that contradicts the description. No mismatched addresses, values, or targets are visible, and the pattern (execute() to a named payload) is routine and expected for this contract type. Given the inability to verify specifics due to the opaque delegatecall, confidence is low, but I found no evidence of a discrepancy, so I rate this consistent rather than flagging an unverifiable claim as a fault of the proposer.
Generated by Kvorum
04Actions
- Target
- 0xb942…bf93
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- aaveexecutedACI Service Provider Proposal83%
- aaveexecutedACI Ad Astra79%
- aaveexecutedACI Phase IV – “Road to 80”78%
- aaveexecutedACI Phase II76%
- aaveexecutedSet ACI as Emission Manager for USDS, aUSDS and awstETH74%
- aaveexecutedSet ACI as Emission Manager for Aave Liquidity Mining programs72%
- aaveexecutedSet ACI as Emission Manager for wstETH & tBTC71%
- aaveexecutedSet ACI as Emission Manager on the Avalanche network70%
- aaveexecutedMainnet PYUSD Emissions Admin64%
- aaveexecutedSet Aave Chan Initiative as Emission Manager for fdUSD on BNB Chain Aave V364%