• vlAURA Vote sheet managed here
    • Submit the csv every 2 weeks for voting based on the readme from jalbrekt. Xeonus has done before, i basically reference partner convos, top performing pools, and snapshot for recent additions to help bootstrap. Quant, Lido, Rocket, Aave and other partners normally incentivized https://github.com/BalancerMaxis/multisig-ops/blob/2113b142f183bb2d5f7a00b1f8005a9129b67ef5/MaxiOps/vlaura_voting/README.md
    • Also ear mark incentives for new products, can be done via HH refund. Check this repo for HH refund details. Requests are made once a month usually. Gosuto has done before.
    • Would suggest Ops handles and BD + Strat team decide placement when needed.
    • When we have grants based on TVL milestones, normally i allocate extra incentives to those networks to push for unlocking new tranches.
  • Essentially partner checklist when a new team comes on board
  • What pool type do they want ? Depends on asset type usually
  • Boosted? Hooks? ReCLAMM?
  • Will they have initial TVL or incentives, do they need gauges, a proposal or a guide on how to bribe on HH or Paladin? Walk them through the governance process.
    • Helping create gauge + instructions on forum for a proposal
  • If they are yield bearing, we need a rate provider.
    • Determine if Chainlink, API3, Redstone, or ERC4626 interfaces can be used to leverage on of our factories.
    • If not, explain the getRate interface, they must have a fixed point 18 decimal number return “getRate” and share our review repo/registry to them to clarify. Usually sharing sDAI or a simple one to explain.
    • They or we must submit a review issue to the repo, keep on top of mkflow and the integrations team to get this done in a timely manor and merge. Must merge to keep governance / ops team satisfied.
    • Likely every yield bearing asset has an APR associated with it so we must navigate that and share the api endpoint with Jarek and Franz for them to add it to the backend.
    • Help them configure the pool properly once rate provider is reviewed. Sometimes needing to use the CombinedRateProviderFactory or AaveRateTransformer is a yield bearing asset is in a boosted market as well. ReadME
    • Metadata repo must be properly configured either by BD lead, ops team, personally think FE team should do this but up to you guys. Logos + points programs must also be added.
      • Self service can be a push for people but it is quite complex to do all the above.
    • For new chains I would suggest having integrations deploy all the RateProviderFactories 3 weeks in advance of expected launch date so you have ample time to create all vaults, run fork tests, seed buffers, get logos made, and configure rate providers properly.
      • If there are incentive programs deploying injectors, pools, gauges etc all important in advance of marketing campaign
  • Note all these steps must be done for new lending markets as well. Redirection of external incentives + showing aprs to be coordinated with Gosuto, Xeonus, the external team, and APRs shown by Franz and Jarek