Initialization of the FundFlowController
doesn't initialize timeOfLastUpdateByGroup
to the block.timestamp
.
When inititializing the FundFlowController
, the timeOfLastUpdateByGroup
for all groups is initialized to 0
:
This means all group start within the claimable window, since the claim period initializes as active:
Additionally, we must remember that the claim period is periodic - therefore in order to introduce a claim period at an offset date from the starting timestamp, the deployer would need to configure a delay period that's at least the length of the lifespan of the blockchain.
The first vesting period can be immaturely claimed for all groups since the unbondingPeriod
's first comparison starts from the beginning of time.
Manual Review
Initialize the timeOfLastUpdateByGroup
to the block.timestamp
.
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.