Umami Finance STIP Addendum
Information about STIP
- Can you provide a link to your previous STIP proposal (round 1 or backfund)?
- How much, in the previous STIP proposal, did you request in ARB?
- 750,000
- What date did you start the incentive program and what date did it end?
- Start: November 13th 2023 End: March 29th
- Could you provide the links to the bi-weekly STIP performance reports and Openblocks Dashboard?
- Bi-weekly STIP Reports: Umami Finance Bi-Weekly Update - #10 by Neotokyocat
- Openblock Dashboard: OpenBlock Labs
- GMX Grant program Final Report (February 1st - March 15th) - Umami Finance GMX Grant Final Report - GMX Grants Reports - GMX
- Could you provide the KPI(s) that you deem relevant for your protocol, both in absolute terms and percentage change, month over month, for the first of each month starting from October 2023 until April 2024, including the extremes? If you don’t know what KPI might be relevant for you or how to properly define them, please refer to the following document:
- Started with $3,046,121 TVL in Umami’s GLP vaults and ended with $10,635,955 TVL in Umami’s GM Vaults
- $10m TVL retained after STIP ended
- Partnered with multiple projects including: GMX, Galxe, Defi Edge, Timeswap
TVL of vaults GLP+GM Vaults
DATE | 01/11/23 | 01/12/23 | 01/01/24 | 01/02/24 | 01/03/24 | 01/04/24 | |
---|---|---|---|---|---|---|---|
TVL ($M) | 4.1 | 5.4 | 5.3 | 5.7 | 11.3 | 11.1 | |
TVL % | 0% | +34% | +2% | +8% | +98% | -2% |
DAU
DATE | 01/11/23 | 01/12/23 | 01/01/24 | 01/02/24 | 01/03/24 | 01/04/24 | |
---|---|---|---|---|---|---|---|
DAU | 22 | 198 | 145 | 96 | 53 | 53 | |
DAU % | 0% | +800% | -27% | -34% | -45% | 0% |
The successful migration from GLP to GM Vaults is evident in the rapid growth of TVL during the launch phase. The sustained TVL post-STIP incentives indicate a strong product-market fit and user appreciation for the product’s performance. Notably, the significant TVL increase happened post-incentive start date which underscores that users are drawn to the vaults based on their ability to successfully create yield with single asset exposure using GMX’s GM pools.
- [Optional] Any lessons learned from the previous STIP round?
- Implementing oARB emissions, inspired by Dolomite’s system, proved effective in boosting liquidity and securing ARB supply. However, the system faced hurdles, particularly regarding the availability of ARB from vesting contracts. Rapid issuance of oARB tokens initially yielded high returns for early depositors, but challenges arose towards the end of the period. As more depositors opted for the non-ETH investment 40-week option, we encountered delays due to the need to taper emissions.
- This experience highlighted the importance of closely monitoring token availability and adjusting emissions to ensure a sustainable and consistent user experience. Additionally, while the requirement for increased ETH and ARB investment faced backlash from farmers accustomed to direct emissions, it was a critical aspect contributing to the success of our strategy. Mandating a vesting ARB and ETH investment commitment helped reduce the number of users taking advantage of the high emissions rate, allowing savvy users to achieve increased yield in a shorter timeframe.
- Overall, this experience provided valuable insights for future iterations that protect the ARB community, emphasizing the need for flexibility and adaptability in incentive programs.
- Going forward we will target a direct incentive approach with dynamic incentives based on where TVL is needed within our vault system.
- Without an oARB system and running two different types of emission schedules we can create a streamlined dune dashboard.
New Plans for STIP Bridge
- How much are you requesting for this STIP Bridge proposal?
- 375,000 ARB
- Do you plan to use the incentives in the same ways* as highlighted in Section 3 of the STIP proposal? [Y/N]
- No, in order to give users a better user experience we have changed the oARB incentive mechanism to a direct ARB emissions system using a simple master chef contract.
- [Only if answered “no” to the previous question] How will the incentive distribution change in terms of mechanisms and products?
- By employing a straightforward masterchef contract and dynamically distributing ARB incentives, we can incentivize TVL on vaults, enhancing the efficiency and scalability of our GM Vaults. For instance, to optimize the performance of the ETH GM vault, TVL should be evenly distributed between the USDC vault and the ETH vault. If the USDC vault requires additional TVL to maximize efficiency and minimize hedging costs, ARB incentives can be utilized to encourage TVL to flow towards the USDC vault creating optimal internal netting.
- Could you provide the addresses involved in the STIP Bridge initiative (multisig to receive funds, contracts for distribution, and any other relevant contract involved), and highlight if they changed compared to the previous STIP proposal?
- Multisig to receive the incentives: 0x8E52cA5A7a9249431F03d60D79DDA5EAB4930178
- Contracts that will distribute the incentives: 0x52f6159dcae4ce617a3d50aeb7fab617526d9d8f
- Contracts incentivized:
$gmUSDC (WETH) Vault Token - 0x959f3807f0Aa7921E18c78B00B2819ba91E52FeF
$gmUSDC (WBTC) Vault Token - 0x5f851F67D24419982EcD7b7765deFD64fBb50a97
$gmWETH Vault Token - 0x4bCA8D73561aaEee2D3a584b9F4665310de1dD69
$gmWBTC Vault Token - 0xcd8011AaB161A75058eAb24e0965BAb0b918aF29
The multisig used to receive the incentives will be the same, while the incentive distribution contract changed compared to original round 1 STIP proposal. The vault’s being incentivized has changed from GLP Vaults to GM Vaults.
- Could you share any feedback or suggestions on what could be improved in future incentive programs, what were the pain points and what was your general evaluation of the experience?
- While the overall experience was positive, we did find some difficulties ensuring openblocks data for Umami reflected the updates to our products and incentive system. Although we did update the appropriate forms for the bi-weekly updates a secondary form of communication or procedure should be had with openblocks so that protocol data is up to date when changes are implemented.