If you want to add a gauge for your pool to receive BAL emissions, please create a new topic in this category following the template which will appear upon creating the new topic.
Note that after you create a pool you must create a gauge for it before you start a governance proposal. Include the address of the gauge you deployed in your proposal.
This is the gauge factory on Ethereum. Simply call the 1. create function with your pool’s contract address.
Once you, the proposer, feel sufficient discussion has taken place you can request the proposal be moved to a snapshot vote by simply replying to the topic. If there is significant discussion ongoing and you request a vote too early it will increase the risk of a failed vote. You must wait 30 days after a failed vote before another vote can be attempted.
After a vote is requested, the Governance Council (solarcurve, zekraken, Mike B, Xeonus, and mkflow) will vote on whether your proposal includes all the necessary information outlined in the topic creation template. Once a majority has voted in favor, one of us will post the proposal to snapshot.
All snapshot votes must last for three full days and be announced in Balancer’s discord and twitter. A quorum of 100k BAL must be reached and the majority must vote in favor for a proposal to pass.
Approved gauge votes will be bundled together every Thursday into an omnibus proposal for execution with the aim to have them vote eligible by Monday
For reference, the template:
Describe what this proposal is about
• Github Page
• Other useful links?
Describe the proposed asset(s), the corresponding protocol(s), and historic prices of the token (price must come from the source of highest liquidity).
Explain why this pool needs incentivization
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.
Audits: Provide links to audit reports and any relevant details about security practices.
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.
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.