Summary: Proposal to add a gauge for Timeless' veLIT token on Ethereum, one of the first ve8020 based on the popular veBAL model.
This proposal is a first step aiming to align with the key strategic objective of Balancer, described in the [BIP-146].
References/Useful links:
Description: veLIT stands for vote-escrowed Liquidity Incentive Token, it is simply LIT locked for a period of time. veLIT is the core component of Timeless' liquidity engine, Bunni.pro. This engine is designed to maximize liquidity on Uniswap v3 by creating complex incentivization schemes. Timeless hopes that by launching LIT, other projects will be able to incentivize their token liquidity at a much higher level of efficiency on Uni v3. Additionally, Timeless use LIT and Bunni to bootstrap liquidity in its own yield token markets.
How does Timeless work? Timeless is a yield tokenization protocol. You can provide assets to Timeless (e.g. 100 USDC) and mint PYT and NYT (e.g. 100 PYT and 100 NYT). The assets will be deposited into a farm, and the yield earned can be claimed by the PYT holders. By holding either only PYT or only NYT, you can build either a long position or short position on yield rates such as stETH or aUSDC.
How does Bunni work? Bunni is a liquidity engine that was built on top of Uniswap v3. It was initially released in October 2022 as a public utility that represents Uniswap v3 liquidity positions as fungible ERC-20 tokens instead of NFTs. This allows for more complex incentivization schemes to be created for Uniswap v3 liquidity. Since its initial release, Timeless has continued to improve and develop Bunni, turning it into a full-fledged liquidity engine, with improvements to its tokenomics inspired by protocols such as Curve and Balancer. These improvements aim to:
For more information about the tokenomics, please see FOO: Fungible Ownership Optimization:` https://blog.timelessfi.com/posts/foo
Motivation: Timeless is a steadfast advocate of Balancer technology and will maintain its utilization in the long term. By incorporating a veLIT gauge, Balancer highlights the capabilities of the ve8020 model to a wide array of DeFi projects considering their tokenomics strategy. If LIT succeeds in becoming the CRV of Uni v3, both Timeless and Balancer will reap the benefits. This mutually beneficial outcome increases visibility for our respective ecosystems. The potential increase in liquidity, trades, and fees generated by the 80/20 LIT/WETH pool could result in significant revenue for the Balancer protocol and its LPs.
Specifications:
Oracles: NA
Audits:
Centralization vectors: LIT and veLIT don't rely on any centralized component in order to operate. The implementation of Timeless Improvement proposals submitted and voted by the community must be implemented by the genesis team. Cf governance process https://gov.timelessfi.com/discussion/9717-timeless-governance
Market History:
#1
The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will initiate a transaction to the Authorizer 0xA331D84eC860Bf466b4CdCcFb4aC09a1B43F3aE6 calling grantRole with the following arguments:
role: 0xf49d7ffb5922642adc9f29cfb52b2214e81e0b0e54e9cd1e9f70439f0011f368
This corresponds with the role for calling add_gauge on the gaugeController as seen here.
account: 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f
This allows the DAO Multisig to directly add gauges to the controller.
#2
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 0x56124eb16441A1eF12A4CCAeAbDD3421281b795A and the corresponding gauge type for the data(bytes) argument.
data(bytes) : 0x3a04f90000000000000000000000000056124eb16441a1ef12a4ccaeabdd3421281b795a0000000000000000000000000000000000000000000000000000000000000002
#3
The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will initiate a transaction to the Authorizer 0xA331D84eC860Bf466b4CdCcFb4aC09a1B43F3aE6 calling renounceRole with the following arguments:
role: 0xf49d7ffb5922642adc9f29cfb52b2214e81e0b0e54e9cd1e9f70439f0011f368
This corresponds with the role for calling add_gauge on the gaugeController as seen here.
account: 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f
This removes the ability for the DAO Multisig to directly add gauges to the controller.