[BIP-259] stMATIC-bb-a-WMATIC/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 stMATIC-bb-a-WMATIC pool token. These pools leverage the yield bearing versions of stable coins, USDC, USDT, DAI and stMATIC-WMATIC pairing in a 50/50 weighted pool. This will make a highly capital efficient route for LPs to keep exposure to stMATIC 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

stMATIC Link to:

Protocol Description:

bb-a-USD is a Balancer’s primary stable coin liquidity on polygon, leveraging AAVE’s boosted strategy. stMATIC-bb-a-WMATIC 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 specific to Polygon network.


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

Link to pool: 0x7F4f4942F2a14B6AB7B08b10ada1AAcede4EE8D4
Link to gauge: 0x02DFcC6ca6611cCBDCe51049a332afDB91465584

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

data(bytes) :