Author(s): @mcfly
Status: BIP
Date Applied: 2023-03-01
Date Updated: 2023-03-13
Date Ratified: yyyy-mm-dd
Vote Start Date: yyyy-mm-dd
Vote End Date: yyyy-mm-dd
BAL grant amount: 50k BAL
This grant application requests 50k BAL to be awarded to Timeless as a participant in Balancer's program outlined in BIP-146, which aims to support all systems involving the staking/locking of 8020 BPT. This proposal follows a successful vote to enable veLIT gauge on Balancer.
More details about Timeless 8020 BPT here.
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.
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.
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
Transaction A will be executed immediately.
DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will transfer 50,000 BAL to 0x89f67f3054bFD662971854190Dbc18dcaBb416f6
Then, DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will call allowlistAddress on 0x7869296Efd0a76872fEE62A058C8fBca5c1c826C with the following argument:
contractAddress: 0x89f67f3054bFD662971854190Dbc18dcaBb416f6
This will whitelist the veBAL locking contract to lock veBAL in the system.
Transaction B, to be executed some time later once ETH is transferred by Timeless:
DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will call createLock on 0x89f67f3054bFD662971854190Dbc18dcaBb416f6 with following arguments:
unlockTime: 1712959367 which corresponds to 4/12/2024 (max lock)
minAmountOut: 0 placeholder value for now
Once A is executed and the ETH is sent to the contract we can use tenderly sim to figure out if transaction B parameters need to be edited. This wouldn't require another vote, just forum post explaining reasoning.