[BIP-260] Enable wstETH-bb-a-WETH/bbamUSD Gauge [Polygon]

PR with payloads


This pool contains a boosted / linear stable pool token bb-am-USD - Balancer’s AAVE boosted stable pool token & the wstETH-bb-a-WETH pool token. These pools leverage the yield bearing versions of stable coins, USDC, USDT, DAI and wstETH-bb-a-WETH pairing in a 50/50 weighted pool. This will make a highly capital efficient route for LPs to keep exposure to wstETH and stable coins while earning yield through AAVE. The protocol will be earning yield on the boosted portion of this pool, making the token pairing more efficient for both parties. This gauge would enter as a “core pool” under BIP-19, meaning protocol fees earned by this pool would be used to bribe for votes on it.

References/Useful links:

USDC: Link to:
Github Page
Communities - Coingecko link

Protocol Description:

bb-am-USD is a Balancer’s primary stable coin liquidity on polygon, leveraging AAVE’s boosted strategy. wstETH-bb-a-WETH BPT is the Balancer pool token containing the respective tokens governance token.


Balancer has been expanding into yield bearing tokens and with the release of AAVE v3 there is a migratory push to have assets earning passive yield while underlying trades are facilitate and optimized from both the trader and LP perspectives. This pool executes this by nesting various tokens with high trading volume and lending opportunities.


  1. Governance: Find more information about governance on Lido’s forum.
  2. Oracles: Polygon wstETH Oracle, see here
  3. Audits: For Lido Protocol and Aave v3, see below
  1. Centralization vectors: See here.
  2. Market History: See wstETH and wETH.
  3. Value: Balancer will earn the protocol fee on wstETH yield and deposit yield generated by Aave v3 on Polygon via bb-a-wETH.


Link to pool: 0x8fd39252d683fDB60BDDD4DF4B53C9380B496D59
Link to gauge: 0xCDb532170f8B524D047287bFEfAcd0cC02441b4A

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 0xCDb532170f8B524D047287bFEfAcd0cC02441b4A and the corresponding gauge type for the data(bytes) argument.
data(bytes) : 0x3a04f900000000000000000000000000cdb532170f8b524d047287bfefacd0cc02441b4a0000000000000000000000000000000000000000000000000000000000000003