GIP-09: Update GFI rewards param for Curve LP

Proposals
1

Authors

@alvinh, @emilyh

Summary

Update the configurable effectiveMultiplier parameter in the StakingRewards contract from 0.50 to 0.75 on the FIDU-USDC Curve LP positions to be staked for GFI liquidity mining rewards. This is important to properly incentivize liquidity to be deposited into the FIDU-USDC Curve pool by bringing projected APYs of staking the Curve LP position closer inline with staking FIDU-only.

Motivation

After the successful governance vote and development of GIP-01, the FIDU-USDC Curve LP factory pool has been created (Curve.fi).

However after discussing with Senior Pool LPs, and doing some spreadsheet modeling, we’ve realized that we will need to change the effectiveMultiplier parameter used to determine award GFI tokens for the staked Curve LP position in order to bring the projected APYs of staking the Curve LP position closer in line with staking FIDU-only, in order to properly incentivize Senior Pool LPs to deposit FIDU-USDC liquidity into the Curve pool.

Note: There are no changes to the Goldfinch Senior Pool Liquidity Mining program with this update.

Specifications & Requirements

Key Requirements

  1. Update effectiveMultiplier parameter from 0.50 to 0.75 in the StakingRewards contract

Background

To support staking the Curve LP token described in GIP-01, we perform an additional calculation at the time of staking to get the exchange rate that will be used to convert the Curve LP tokens to an effective FIDU amount. The exchange rate for a Curve LP position will be calculated using the virtual price of the LP token given by Curve. We use Curve’s virtual price to calculate the effective FIDU amount instead of spot prices or live ratios of the FIDU-USDC Curve pool to prevent flash loan attacks. You can read more details about how Curve has been exploited here.

Rationale

Goldfinch governance should vote to change the effectiveMultiplier parameter in order to incentivize users to deposit sufficient liquidity into the FIDU-USDC Curve pool. Changing the parameter value from 0.50 to 0.75 will properly incentivize liquidity to be deposited into the FIDU-USDC Curve pool by bringing projected APYs of staking the Curve LP position closer inline with staking FIDU-only.

Benefits

  • Incentivizes liquidity deposits on the FIDU-USDC Curve pool by bringing projected APYs of staking the Curve LP position closer inline with staking FIDU-only

Downsides

  • As Senior Pool APYs and GFI reward APYs fluctuate over time, we may need to make additional periodic updates to the effectiveMultiplier parameter value. These changes will go through governance voting, as the community should decide what behavior to incentivize with the effectiveMultiplier parameter.

Voting

YES vote: Approve a change to update the effectiveMultiplier parameter from 0.50 to 0.75.

NO vote: Reject the proposed changes.

Resources

GIP-01: Allow FIDU-USDC Curve LP positions to be staked for GFI liquidity mining rewards

Goldfinch Senior Pool Liquidity Mining program

4 Likes
2

Hi Alvin/Emily -

As usual you are doing great with the proposals - kudos on that.

Just to make sure I got this correctly - this proposal is to update the technical parameter for the approved proposal GIP-01 without impact to any rewards distribution or anything - is that correct ?

Thanks,

1 Like
3

Thanks @nisa !

Yes – this proposal is to update a technical parameter for the approved proposal GIP-01. The updated value will make it so that the GFI rewards for staking the Curve LP position are more closely aligned with the APYs that users receive when staking FIDU-only.

If we do not update this parameter, the GFI rewards for staking the Curve LP position will be significantly lower than staking FIDU-only. As a result, it’s unlikely that we see meaningful FIDU-USDC liquidity deposited into the Curve pool, and so the benefits of GIP-01 would not materialize.

2 Likes
4

I thought technical parameter update comes as part of technical implementation after council approval and we did not need an explicit proposal to update that.
I might have had wrong assumption on that.

I support and vote yes for this proposal because this is an update to technical parameter for the previous approved proposal.

Thanks

1 Like
5

@alvinh - can you push this for snapshot vote ?

6

This proposal is now up for voting on snapshot.

https://snapshot.org/#/goldfinch.eth/proposal/0x478aeb76c14d6d944558fdf4ec68d4cbbeace464f8d1d7364bcd2442e807c73e

You have 72 hours to vote !

edit: 03/29/2022:
Council has approved this proposal !