[BIP-328] Enable Initial zkEVM Gauges [zkEVM]

PR with Payloads


Balancer recently passed going forward with deployment on zkEVM here. Given their launch, it is in the Balancer’s best interest to add core liquidity on zkEVM and to support this with the approval of several gauges. This proposal will activate gauges for the following pools if passed: wstETH/WETH , rETH/WETH, rETH/wstETH, bb-o-USD (Ovix boosted) , bb-o-USD/rETH and bb-o-USD / wstETH. This pools all contain yield bearing assets and in turn will be added to the core pool cycle.

References/Useful links:

Link to:
• Website: Polygon zkEVM , Ovix
• Documentation: Polygon zkEVM , Ovix
• Github Page: Polygon zkEVM , Ovix Contracts
• Communities: Polygon zkEVM , Ovix
• Other useful links?

Protocol Description:

The LST pools in this proposal are reiterations of pools Balancer has on several networks outside of the Ovix boosted addition. The 0VIX protocol enables users to effortlessly lend, borrow and earn interest with their digital assets. Depositors providing liquidity to the protocol may earn passive income, while borrowers are able to borrow using over-collateralization. The lending market is where boosted yield will be sourced from.


These pools will act as the initial base of liquidity for Balancer’s zkEVM expansion.


  1. Governance: Ovix governance is outlined here. Pending their token launch.

  2. Oracles: The rate providers utilized in these pools are powered by layer zero and have been reviewed by the Balancer Labs integrations team.

  3. Audits: Ovix audit reports can be seen here.

  4. Centralization vectors: No centralization vectors outside of USDC and USDT inherent risks in the boosted Ovix USD pool.

  5. Market History: rETH , wstETH, WETH, USDC, USDT

  6. Value: These pools will be the core liquidity on zkEVM during this initial launch stage.

Transaction Specifications:

The Balancer Maxi LM Multisig eth:0xc38c5f97B34E175FFd35407fc91a937300E33860 will interact with the GaugeAdderv4 at 0x5DbAd78818D4c8958EfF2d5b95b28385A22113Cd and call the addGauge function with the following arguments:

gauge(address): 0x54f220a891f468629027C3Cc8A58722D4F576402
gaugeType(string): PolygonZkEvm

gauge(address): 0xce99399fb4De36056A6831b159572E271360ea40
gaugeType(string): PolygonZkEvm

gauge(address): 0xF7d515DC47d5BD57786494628ed766d6bF31cd39
gaugeType(string): PolygonZkEvm

gauge(address): 0x7949426d750FEFC25754F149B2FB446B60c39387
gaugeType(string): PolygonZkEvm

gauge(address): 0xc85679E41f1F98E694D9F8983fdD484F98F2eB02
gaugeType(string): PolygonZkEvm

gauge(address): 0x48799A2B0b9ec11E4fa158c781AD8bFAbB892D58
gaugeType(string): PolygonZkEvm