[BIP-239] Enable bb-a-USD gauge [Ethereum]

PR with payload


This is a proposal to enable a bb-a-USD gauge on Ethereum.

Protocol Description

The Aave Protocol is a decentralized liquidity protocol that is deployed across many EVM compatible networks including but not limited to Optimism, Arbitrum, Avalanche and Polygon.

Currently, the Aave Protocol has a TVL of approximately $5 Billion.


This proposal aims to add a veBAL gauge for bb-a-USD.

Bb-a-USD was the flagship boosted pool for Balancer. However, whilst Balancer recently launched new pools on Aave V3 to ensure continued payment of protocol fees, the bb-a-USD pool wasn’t migrated and was later wound down as it was built on Aave V2. Initially, there was no migration support for Aave V3, which has been deployed on Ethereum since 27/01/23.

Now that USDT is listed on Aave V3, as shown by this proposal, it is possible to add the bb-aUSD gauge through this proposal.


  1. Governance: AAVE and stkAAVE serve as the governance tokens for the Aave DAO. Holders can vote on proposals at both a Snapshot level and through the Aave DAO on-chain governance portal.

  2. Oracles: Aave uses Chainlink oracles for price feeds.

  3. Audits: You can find a record of audits of Aave V3 here.

  4. Centralization Vectors: Aave Governance is decentralized, and all changes must go through a transparent and well-tested governance process.

  5. Market History: There is a long history of bb-a-USD as a successful boosted pool within Balancers protocol.

Pool address: 0xfeBb0bbf162E64fb9D0dfe186E517d84C395f016
Gauge address: 0x0052688295413b32626D226a205b95cDB337DE86

Transaction: The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdaptor at 0x8F42aDBbA1B16EaAE3BB5754915E0D06059aDd75 and call performAction with the GaugeController at 0xC128468b7Ce63eA702C1f104D55A2566b13D3ABD for the target(address) argument and using 0x3a04f900 followed by the gauge address 0x0052688295413b32626D226a205b95cDB337DE86 and the corresponding gauge type for the data(bytes) argument.

data(bytes) : 0x3a04f900000000000000000000000000 0052688295413b32626D226a205b95cDB337DE86 0000000000000000000000000000000000000000000000000000000000000002