[BIP-234] Enable stMATIC / bb-a-wMATIC Gauge [Polygon]

PR with payload


This pool uses the ComposableStablePoolFactory-v3 1 which addresses the reentrancy vulnerability disclosed during February 2023. This gauge is uncapped, and would enter as a “core pool” under BIP-19. This means 65% of 50% of yield generated by this pool is to be used for bribing for votes on it via Hidden Hand.

The pool stMATIC/bb-a-wMATIC is to replace the primary stMATIC/wMATIC pool on Balancer v2. The current stMATIC/wMATIC contains $57.9M in TVL at the time of writing and is the largest pool on the Polygon deployment.

References/Useful links:

Protocol Description:

This pool utilises stMATIC and linear pool bb-a-wMATIC which deposits wMATIC into Aave v3 wMATIC reserve on the Aave v3 deployment on Polygon. The linear pool utilises a wrapper developed by Aave Companies.


Migrating from stMATIC/wMATIC to stMATIC/bb-a-wMATIC is expected to generate an additional 31.6 bps (158/2 x 0.5 x 0.8) of yield for Liquidity Providers (LPs) after fees and bribes relative to the current pool. This is due to the Aave v3 wMATIC reserve generation 158 bps of deposit yield. Historically, this yield has been higher.

Excluding token emissions, the inclusion of the bb-a-wMATIC linear pool, increases the passive yield for LPs by an estimated 10.2%, (0.316%/3.11%). This is equivalent to >15x the swap fee APR at the time of writing as most of the yield is derived from stMATIC within the pool.


  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: TBA
Link to Gauges: TBA


This proposal is the sole work of @Llama contributor, @Matthew_Graham, via the legal entity TokenLogic. Llama is a Service Provider to Aave DAO.

1 Like

Pool: 0x216690738Aac4aa0C4770253CA26a28f0115c595
Gauge: 0xBD734b38F2dc864fe00DF51fc4F17d310eD7dA4D

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

data(bytes) : 0x3a04f900000000000000000000000000 00BD734b38F2dc864fe00DF51fc4F17d310eD7dA4D 0000000000000000000000000000000000000000000000000000000000000003

1 Like