Farm LQDR using treasury assets
We propose to put some portion of the liquidity tokens in the treasury assets into LiquidDriver farms to acquire LQDR. Currently, the treasury holds about $180K worth of liquidity tokens (FTM-USDC and FTM-USDC-ETH-BTC) that can be used for farming on LiquidDriver. The farmed LQDR will be held in the treasury, its use will be decided by future governance votes.
Pros:
- this would put some portion of the treasury assets in further use, to accumulate LQDR;
- as LiquidDriver plans to work closely with BeethovenX to acquire fBEETS, getting LQDR for the treasury would help better align interests of the two protocols;
- in case that LiquidDriver acquires a huge portion of fBEETS in the future, holding LQDR (in the form of staked xLQDR) would give DAO treasury more voting power;
Cons:
- it exposes our treasury fund to additional smart contract risks (while the LQDR contract involved is a variant of the battle tested Sushi masterchef contract), interacting with any smart contract involves risk;
- it will dilute the farm on LiquidDriver.
Options (the one with majority vote wins):
- Yes, deploy treasury assets to the farm with a cap of 50% of liquidity tokens;
- Yes, deploy treasure assets to the farm with a cap of 25% of liquidity tokens;
- No, more discussion needed.
About LiquidDriver: LiquidDriver is the first liquidity mining dApp providing liquidity-as-a-service in the Fantom ecosystem. They aim to bring its users more utility, rewards, and long-term benefits through their native token, LQDR, and ultimately become the leading liquidity-on-demand platform for dApps on the Fantom Opera Mainnet.
| Voter | Cast Power | Vote & Rationale |
|---|---|---|
0x9748...56f5D5 | 2.816M | Yes; deploy with 50% cap |
0xF7A8...3A6516 | 933,091 | Yes; deploy with 50% cap |
0xCD0f...caA95F | 654,266 | Yes; deploy with 50% cap |
0xA5d8...44AA40 | 562,770 | Yes; deploy with 50% cap |
0x999b...F6958E | 258,142 | Yes; deploy with 50% cap |
VOTE POWER
Proposal Status
- Sun January 09 2022, 05:00 pmVoting Period Starts
- Tue January 11 2022, 05:00 pmEnd Voting Period
Current Results
1-Yes; deploy with 50% cap
7.286M
2-Yes; deploy with 25% cap
421,036.17
3-No; more discussion needed
86,710.222
