The ability to set the lastDistribution combined with the function setStakingContract
in the FjordPoints contract supply more convenience for the admin.
The default value of lastDistribution is the deployed time when deployed the FjordPoints contract . It seems the startTime in the FjordStaking contract and the lastDistribution value in the FjordPoints contract are same when checking the deploy scripts.
So when users do operations(stake or unstake) , meanwhile the FjordPoints can record the users's rewards points in the corresponding's epoch.
It's more convenient to make the admin can set the lastDistribution instead of using the deployed time. For example, if the admin wants to start the points rewards campaign at a specific time or depending on their intention.
Another point is that the owner of FjordPoints can set stakingContract. If the owner sets the stakingContract, how do they sync their epochs for FjordPoints and stakingContract? The ability to set the lastDistribution would make it easier in this situation.
Applying this change will give the admin the ability to set the beginning time of points rewards based on their intention.
Manual
Add param: startTime in the constructor of FjordPoints contract.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.