PR with Payload
Summary:
This is a proposal to enable the root gauge 0xa9390f0e0fd42d3a53a5ba8ed2a381ba29a2ed8e on Ethereum, [which redirects rewards to the child gauge 0x894c4BE2949CD8193B1107a09102955a12d2F8dA on Base] for the pool 0xdb373fd670c1767db9ac9f2512ccf3ef15fd9d3d (BAL / AURA / waBasUSDC).
This proposal seeks to onboard a 25% BAL / 25% AURA / 50% waBasUSDC pool on Balancer v3 (Base) with a 2% emissions cap.
References/Useful links:
Link to:
• Website aura.finance/Documentation docs.aura.finance/
Github Page Aura Finance ·
GitHub• Communities discord.gg/aurafinance•
Other useful links? forum.aura.finance/
Protocol Description:
Centered on veBAL, Aura coordinates incentives around vote-escrowed tokens to boost yield potential and governance power of DeFi liquidity providers, governance token stakers and voters. AURA and BAL tokens are the reward tokens of the Aura ecosystem. waBasUSDC is the wrapped version of Aave’s interest-bearing aBasUSDC on Base, which allows users to earn yield from USDC deposits in Aave.
Motivation:
Establish deep Bal/Aura/waBasUSDC on-chain liquidity on Base using Balancer’s weighted pool design. This reduces slippage for trading and routing volume while anchoring price discovery through Balancer. waBasUSDC allows liquidity providers to earn yield on their USDC thus making it attractive.This integration creates synergies between Aura, Balancer, and Aave, boosting activity across all three ecosystems. While Aura and Balance rewards can be claimed on-chain through Base network, there is currently low liquidity on Base network especially for Aura.
Specifications:
-
Governance: Provide current information on the protocol’s governance structure. Provide links to any admin and/or multisig addresses, and describe the powers afforded to these addresses. If there are plans to change the governance system in the future, please explain.
-
Oracles: Does the protocol rely on external oracles? If so, provide details about the oracles and their implementation in the protocol.
No
-
Audits: Provide links to audit reports and any relevant details about security practices.
docs.aura.finance
-
Centralization vectors: Is there any component of the protocol that has centralization vectors? E.g. if only 1 dev manages the project, that is a centralized vector. If price oracles need to be updated by a bot, that is a centralized vector. If liquidations are done by the protocol, that is also a centralization vector.
Aura is a non custodial, non pausable platform.
-
Market History: Has the asset observed severe volatility? In the case of stablecoins, has it depegged? In the case of an unpegged asset, have there been extreme price change events in the past? Provide specific information about the Balancer pool: how long has it been active, TVL, historical volume? You must provide a direct link to the pool AND a link to your pool’s gauge.
Pool address:
0xdb373fd670c1767db9ac9f2512ccf3ef15fd9d3d (BAL / AURA / waBasUSDC)
https://balancer.fi/pools/base/v3/0xdb373fd670c1767db9ac9f2512ccf3ef15fd9d3d
Gauge address
0xa9390f0e0fd42d3a53a5ba8ed2a381ba29a2ed8e on Ethereum, [which redirects rewards to the child gauge 0x894c4BE2949CD8193B1107a09102955a12d2F8dA on Base]
-
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?)
This will be the primary weighted Bal / Aura / waBasUSDC liquidity pool on Balancer (Base). It offers advantages to liquidity providers by generating additional yield on USDC. This will allow an on-chain opportunity to reinvest rewards from Aura into liquidity while taking advantage of the affordability of Base network.