# \[BIP-274\] Updated Pool: Enable wstETH/rETH Gauge \[Ethereum\] **URL:** \ **Category:** BAL Gauges\ **Created:** [April 27, 2023, 4:13am UTC](https://forum.balancer.fi/t/bip-274-updated-pool-enable-wsteth-reth-gauge-ethereum/4710 "2023-04-27T04:13:47Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![0x70626a](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.balancer.fi/0x70626a/32/2272_2.png) [@0x70626a](https://forum.balancer.fi/u/0x70626a)\ **Post date:** [April 27, 2023, 4:13am UTC](https://forum.balancer.fi/t/bip-274-updated-pool-enable-wsteth-reth-gauge-ethereum/4710/1 "2023-04-27T04:13:47Z")
> **Summary:** > This pool will be replacing the previous wstETH/rETH gauge as we’ll be deploying a different type of TWAMM pool that’s better suited for the type of asset pair, see previous post: [[BIP-265] Enable wstETH/rETH Gauge [Ethereum]](https://forum.balancer.fi/t/bip-265-enable-wsteth-reth-gauge-ethereum/4643). > > We’d like to request governance to disable the old pool gauge. No liquidity has been added and we have paused the pool so no liquidity can be added or trades can happen. > > We’d like to request a gauge for the new pool. We have launched a brand new Balancer pool type: TWAMM. This will be a cornerstone in Balancer’s vision of the go-to AMM for DeFi protocols to build and trade upon. TWAMMs are extremely capital efficient and are critical to improve the blockchain’s anti-fragility by facilitating large asset swaps completely on-chain, see asset monetary policy, whale liquidations, treasury management, index fund re-balancing, etc. **References/Useful links:** > Link to: > • Website: [GitHub - Cron-Finance/Cron-Finance](https://github.com/Cron-Finance/v1-twamm) > • Documentation: [https://docs.cronfi.com/](https://docs.cronfi.com/) > • Github Page: [https://github.com/Cron-Finance/twamm](https://github.com/Cron-Finance/twamm) > • Communities: [Mirror](https://mirror.xyz/0x70626a.eth), [Twitter](https://twitter.com/cronfinance) **Protocol Description:** > - Assets: wstETH/rETH > - Corresponding Protocols: Lido, Rocket Pool > - Price: [wstETH](https://www.coingecko.com/en/coins/wrapped-steth), [rETH](https://www.coingecko.com/en/coins/rocket-pool-eth) **Motivation:** > In order for trades to start on the pool, we need an initial resting (seed) liquidity. We believe the trading fees paid to LPs from traders and arbitrageurs of TWAMMs will far exceed the current status quo. We’re trying to execute a large treasury diversification for the Nouns DAO, more context here: [Nouns DAO](https://nouns.wtf/vote/275) _ **❌Disable Old Gauge** _ Link to old [pool](https://etherscan.io/address/0x3e953C6Bf97284F736c5F95b3c3BE8F4e48075f4) Link to old [gauge](https://etherscan.io/address/0xEeDEd342aa2Cc1b48ECcAfeB663fdf2c1d166934) **✅Enable New Gauge** Link to new [pool](https://etherscan.io/address/0x6910C4e32D425a834Fb61e983C8083a84b0EBd01) Link to new [gauge](https://etherscan.io/address/0xB5bd58C733948e3d65d86BA9604e06e5dA276FD1) **Specifications:** 1. **Governance:** - Factory Owner: [Gnosis Safe Deployer](https://app.safe.global/home?safe=eth:0xe122Eff60083bC550ACbf31E7d8197A58d436b39) - Admin Privileges: [Admin Privileges - TWAMM](https://docs.cronfi.com/twamm/fundamentals/admin-privileges) - Governance plans: initially the factory owner will be the default administrator of the pools. However, as new pools are created we plan on handing over the admin privileges to the token’s DAO or controlling party as needed. 2. **Oracles:** - No external reliance, we have a built-in oracle. 3. **Audits:** Provide links to audit reports and any relevant details about security practices. - SpearbitDAO: [portfolio/CronFinance-Spearbit-Security-Review.pdf at master · spearbit/portfolio · GitHub](https://github.com/spearbit/portfolio/blob/master/pdfs/CronFinance-Spearbit-Security-Review.pdf) 4. **Centralization vectors:** - The only centralization vector is the factory owner controls the admin privileges. The factory multi-sig is a 2/3 Gnosis Safe. The capabilities that the admin has is _ **pausing** _ and _ **setFees** _. Both of these are in place to ensure optimal operations of the pool. LPs can monitor these events and are free to withdraw liquidity at any time. 5. **Market History:** - Both tokens are wrapped staked ETH. 6. **Value:** Is this pool intended to be the primary source of liquidity for the token(s)? If this is not the case, explain the expected value add to Balancer (can this pool generate consistent fees?) - No, the pool would need roughly $100 - 200k in liquidity to begin with. TWAMMs are extremely capital efficient because they split the trade across thousands of blocks and dedicated arbitrageurs are constantly replenishing the capital when they correct asset price deviations. - Nouns DAO is interested in diversifying their treasury of stETH to rETH, roughly $28M at current prices - [wallet](https://etherscan.io/address/0x0BC3807Ec262cB779b38D65b38158acC3bfedE10). This will be an extremely important trade to prove the concept of our protocol and make Balancer the go-to venue for treasury diversification needs. - Once TWAMMs become the de-facto solution for large asset swaps, we believe Balancer protocol will become the schelling point for protocols interested in advanced trade execution. Please write a new bip-xxx post to encompass the changes of killing old gauge and adding the new one. Specifications: Part A: 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 `0xB5bd58C733948e3d65d86BA9604e06e5dA276FD1` and the corresponding gauge type for the data(bytes) argument. data(bytes) : `0x3a04f900000000000000000000000000b5bd58c733948e3d65d86ba9604e06e5da276fd10000000000000000000000000000000000000000000000000000000000000002` ### Killing Old Gauge Part B: The DAO Multisig `0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f` will interact with the AuthorizerAdaptor at `0x8F42aDBbA1B16EaAE3BB5754915E0D06059aDd75` and call performAction using `0xab8f0945` for the `data(bytes)` argument and `0xEeDEd342aa2Cc1b48ECcAfeB663fdf2c1d166934` for the `target(address)` argument. ---
**Author:** ![solarcurve](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.balancer.fi/solarcurve/32/1487_2.png) [@solarcurve](https://forum.balancer.fi/u/solarcurve)\ **Post date:** [April 27, 2023, 4:01pm UTC](https://forum.balancer.fi/t/bip-274-updated-pool-enable-wsteth-reth-gauge-ethereum/4710/3 "2023-04-27T16:01:26Z")
[https://snapshot.org/#/balancer.eth/proposal/0x085dac86fb8c5d1048632d66ae956c56690b937a8beb40a40723c287f52863a9](https://snapshot.org/#/balancer.eth/proposal/0x085dac86fb8c5d1048632d66ae956c56690b937a8beb40a40723c287f52863a9) ---
**Author:** ![0x70626a](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.balancer.fi/0x70626a/32/2272_2.png) [@0x70626a](https://forum.balancer.fi/u/0x70626a)\ **Post date:** [September 1, 2023, 6:31pm UTC](https://forum.balancer.fi/t/bip-274-updated-pool-enable-wsteth-reth-gauge-ethereum/4710/4 "2023-09-01T18:31:38Z")
Hey all, we’d like to kill this gauge as we’ve not found a good use case/need for it and have been sourcing liquidity without incentivizing it. Thanks for the help getting it set up 🙌 ---
**Author:** ![Tritium](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.balancer.fi/tritium/32/2011_2.png) [@Tritium](https://forum.balancer.fi/u/Tritium)\ **Post date:** [September 27, 2023, 4:11pm UTC](https://forum.balancer.fi/t/bip-274-updated-pool-enable-wsteth-reth-gauge-ethereum/4710/5 "2023-09-27T16:11:35Z")
Thanks the notice. We’ll probably wait till the next time we do some housekeeping to remove it. I you stage another BIP for a gauge, you also could request it’s removal then(or remind us to add it in).