stataToken operational update
01Summary
Transfer ownership of stataToken helper contracts across 5 blockchains (Ethereum, Polygon, Arbitrum, Optimism, Avalanche) from Aave governance to Balancer DAO governance to enable faster, synchronized implementation upgrades and support improvements to the underlying asset structure and incentive management.
- Type
- governance change
Key changes
- Transfer proxy admin permissions of stataToken contracts from Aave governance to Balancer DAO on Ethereum, Polygon, Arbitrum, Optimism, and Avalanche(high)
- Enable Balancer governance to execute synchronized upgrades across multiple networks(high)
- Support change of underlying asset from aToken to underlying asset (e.g., aUSDC to USDC)(medium)
- Improve management of incentives on Aave v3(medium)
Notable concerns
- stataTokens are non-core helper contracts currently controlled by Aave but used almost exclusively by Balancer, representing a shift in governance responsibility across multiple blockchains
Generated by Kvorum
02Description
Simple Summary
Transfer of the ownership of the stataToken helper contracts used exclusively by Balancer to their governance, in order for them to execute efficient and time-synced implementations upgrades.
Motivation
The Balancer team approached us regarding potential improvements:
Change the underlying asset to be underlying on Aave instead of aToken (e.g. USDC instead of aUSDC). Improvement in the management of incentives on Aave v3. However, as the stataTokens are currently Aave governance-controlled and multi-chain, both this operational effort and the (required) time synchronizing across networks becomes complicated, as proposals execute at different times (Ethereum ~5 days, all other networks ~7 days).
For that reason, and given that currently these non-core (helper) contracts are almost exclusively used by Balancer, we think the best solution is to transfer the ownership of these stataTokens to the Balancer governance and have them execute a sync upgrade.
Specification
The proposal calls changeProxyAdmin(proxy, newAdmin) on the respective token, moving the permissions from the current proxyAdmin to the Balancer DAO on the respective network:
References
- Implementation: Ethereum, Optimism, Arbitrum, Polygon, Avalanche
- Tests: Ethereum, Optimism, Arbitrum, Polygon, Avalanche
- Discussion
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The description promises a straightforward action: transfer stataToken proxy admin ownership to Balancer DAO across five networks (Ethereum, Polygon, Arbitrum, Optimism, Avalanche) via changeProxyAdmin calls. The decoded calldata shows a pattern consistent with Aave's typical cross-chain governance execution: one direct execute() call (likely the Ethereum-native action) and three execute(address) calls to forwarder/bridge contracts that relay execution to other networks. This structure is plausible and consistent with the described intent, but there is a numerical gap — five networks were named in the description while only four calldata actions exist. Without on-chain source verification of the forwarder contracts' targets, I cannot confirm whether all five networks are covered (e.g., one forwarder might handle two chains, or one network might be inadvertently omitted). This raises a moderate but not severe concern: the core mechanism (ownership transfer via proxy admin change, routed through governance-controlled executors) matches the description, and no funds or unrelated permissions are being moved, but the discrepancy in network count deserves a note of caution for reviewers before finalizing their vote. Confidence is medium due to limited visibility into the exact behavior of the forwarder contracts referenced in actions 1-3.
Discrepancies
- mediumextra in description
The description explicitly lists five networks (Ethereum, Polygon, Arbitrum, Optimism, Avalanche) where changeProxyAdmin should be executed, but the decoded calldata only contains four actions: one direct execute() (presumably Ethereum) and three execute(address) forwarder calls (presumably three of the remaining four networks). Without visibility into the exact identity/behavior of the forwarder contracts and target addresses, it cannot be confirmed that all five networks' proxy admin transfers are actually included — one network's transfer may be missing or bundled unexpectedly.
“The proposal calls `changeProxyAdmin(proxy, newAdmin)` on the respective token... - Ethereum - Polygon - Arbitrum - Optimism - Avalanche”
Generated by Kvorum
04Actions
- Target
- 0x5825…010e
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
- Target
- 0x5f5c…6711
- Value
- 0 wei
- Function
- execute(address)
- Arguments
{ "0": "0x4E99b8dC5c5b24b8904b640Ea9342dcEa233818A" }- Calldata
- Target
- 0xd1b3…cfa3
- Value
- 0 wei
- Function
- execute(address)
- Arguments
{ "0": "0xcfC26009618ec2Ca8787180116a37Caa354a465C" }- Calldata
- Target
- 0x158a…d45b
- Value
- 0 wei
- Function
- execute(address)
- Arguments
{ "0": "0xcfC26009618ec2Ca8787180116a37Caa354a465C" }- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- aaveexecutedRobot Maintenance72%
- aaveexecutedAave Governance V3 Activation70%
- aaveexecutedMigrate Robots to Chainlink Automation v270%
- aaveexecutedAave Governance V3 Activation Short70%
- aavecanceledAave Governance V3 Activation Short70%
- aavecanceledGovernance V3 Activation70%
- aaveexecutedGovernance v2.5 Activation68%
- aaveexecutedMigration of remaining Gov v2 permissions & DAO's Paraswap positive slippage66%
- aaveexecutedAdjust Aave Governance Level 2 requirements66%
- aaveexecutedFunding Aave Robot for Governance V2 Automation64%