Finance Steward Deployment: Pool Exposure Module
01Summary
This proposal deploys the PoolExposureSteward smart contract module across 11 blockchain networks to enable approved signers (via a 3-of-4 multisig) to perform routine financial operations: migrate assets between Aave V2 and V3 pools, deposit idle collector funds into V3, and withdraw funds for runway or swaps. The module will be deployed on Mainnet, Polygon, Avalanche, Optimism, Arbitrum, Scroll, Base, BNB Chain, Gnosis, Sonic, and Linea with role-based guardrails.
- Type
- contract upgrade
Key changes
- Deploy PoolExposureSteward module across 11 chains to enable asset migrations between Aave V2 and V3 pools(high)
- Grant approved signers ability to withdraw assets from Aave V2/V3 into Collector for runway or swaps(high)
- Enable deposit of idle Collector funds into Aave V3 pools(medium)
- Establish 3-of-4 multisig guardian (Marc/AaveChan, Matt/TokenLogic, Chaos Labs, Val/LlamaRisk) to oversee module operations(high)
- Initialize DustBin reserves with ~$100 worth of each reserve token per pool to prevent pools from being emptied(medium)
Notable concerns
- Centralization risk through 3-of-4 multisig control of PoolExposureSteward operations
- Module permissions span multiple chains and pools requiring careful oversight to prevent misuse
Generated by Kvorum
02Description
Simple Summary
This publication details the initial configuration of the Aave Finance Steward PoolExposure module.
The Finance Steward role is comprised of a set of Modules (Smart Contracts) that provide approved signers with the ability to perform DAO approved actions such as swapping tokens or migrating assets from Aave V2 to Aave V3.
Motivation
The Finance Steward modules enables the DAO to define a core set of financial capabilities to be carried out within strict role-based guardrails. As the role matures or new use cases arise, we plan to bring forward additional capabilities for the DAO to discuss.
The initial set up of the Finance Steward includes deploying two separate modules (smart contracts), the PoolExposureSteward and the MainnetSwapSteward, this publication deploys the PoolExposureSteward smart contract across various chains.
PoolExposureModule
Features
The PoolExposureModule is granted permission to facilitate the following routine operational tasks:
Migrations
- Withdraw assets from Aave V2 and deposit into Aave V3.
- Withdraw assets from a given Aave V3 pool and deposit into another Aave V3 pool (ie: Core to Prime).
Deposit Passive Assets
- Deposit idle Collector funds into Aave V3.
Withdraw Assets
- Withdraw funds from Aave V2 or Aave V3 into the Collector. These funds can then be used for runway or to perform swaps where applicable.
Specification
The PoolExposureSteward contracts have been deployed, across all chains, with the DAO as the owner of the contracts and the following SAFE acting as the guardian 0x22740deBa78d5a0c24C58C740e3715ec29de1bFa.
The SAFE is configured as a 3-out-of-4 multi-sig, and the signers for the SAFE are the following:
Marc (AaveChan) - 0x329c54289Ff5D6B7b7daE13592C6B1EDA1543eD4
Matt (TokenLogic) - 0xb647055A9915bF9c8021a684E175A353525b9890
Chaos Labs - 0x5d49dBcdd300aECc2C311cFB56593E71c445d60d
Val (LlamaRisk) - 0xbA037E4746ff58c55dc8F27a328C428F258DDACb
The PoolExposureModule will be deployed on the following chains, with the listed pools approved for interaction.
| Network | Pools |
|---|---|
| Mainnet | V2, AMM V2, V3 Core, V3 Prime |
| Polygon | V2, V3 |
| Avalanche | V2, V3 |
| Optimism | V3 |
| Arbitrum | V3 |
| Scroll | V3 |
| Base | V3 |
| BNB | V3 |
| Gnosis | V3 |
| Sonic | V3 |
| Linea | V3 |
For each pool, ~$100 worth of each reserve will be sent to the DustBinSteward contract. The DustBin is a special contract that, as the name implies, holds a dust amount of tokens. This is done to ensure that the pools are never emptied and the PoolExposure module can operate without having to worry about possibly emptying a given reserve.
If the corresponding DustBin for a specific reserve holds about ~$100 worth of the token, then that token will not be transferred. If the DustBin does not yet have that token, the mentioned amount will be sent alongside this proposal.
References
- Implementation: AaveV3Ethereum, AaveV3EthereumLido, AaveV3Polygon, AaveV3Avalanche, AaveV3Optimism, AaveV3Arbitrum, AaveV3Base, AaveV3Scroll, AaveV3BNB, AaveV3Linea, AaveV3Sonic
- Tests: AaveV3Ethereum, AaveV3EthereumLido, AaveV3Polygon, AaveV3Avalanche, AaveV3Optimism, AaveV3Arbitrum, AaveV3Base, AaveV3Scroll, AaveV3BNB, AaveV3Linea, AaveV3Sonic Snapshot
- Discussion
- PoolSteward Code and Review: PoolSteward, PoolStewardTests, CertoraReport
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The decoded calldata consists of only two mainnet 'execute()' fallback calls to payload contracts, which is the standard Aave governance pattern where the actual deployment/configuration logic (module deployment, guardian assignment, pool approvals, DustBin transfers) lives inside the bytecode of these payload contracts rather than being visible as discrete decoded arguments. This means the granular claims in the description — specific chain deployments, pool lists, guardian Safe address, signer list, and ~$100 DustBin transfers — cannot be independently verified from the decoded actions alone. However, nothing in the two decoded actions contradicts the description: they are consistent with triggering the Ethereum and Ethereum-Lido payload contracts referenced in the proposal's implementation links, and cross-chain deployments are typically handled via separate bridged proposals not captured in this action list. Since the decoded data is too opaque to confirm or refute most of the description's specific claims, I mark this as consistent but with low confidence rather than flagging speculative discrepancies. No value, target, or scope mismatches are evident from what is decodable.
Generated by Kvorum
04Actions
- Target
- 0xb74a…b732
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
- Target
- 0x3136…ff78
- 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
- aavecanceledFinance Steward Deployment: Pool Exposure Module98%
- aaveexecutedSteward Deployment: MainnetSwapSteward and RewardsSteward87%
- aaveexecutedAave Generalized Risk Stewards (AGRS) activation79%
- aaveexecutedRisk Stewards Cooldown Reduction & Umbrella Pauser Role Reassignment76%
- aaveexecutedDiscount Rate Risk Oracle Activation and update manual AGRS75%
- aaveexecutedClinic steward activation75%
- aaveexecutedAave Umbrella Activation74%
- aaveexecutedFreeze Stewards73%
- aaveexecutedAGRS (Risk Stewards) migration to Risk Agents72%
- aaveexecutedCaps Plus Risk Steward72%