Submitted by WatchPug
BribeVault.sol#L317-L324
In the current implementation, DEFAULT_ADMIN_ROLE of BribeVault can call updateRewardsMetadata() to update the rewards metadata for the specified identifiers.
When a distributions metadata is updated, it will also increase the updateCount and reset the claimed tracker.
RewardDistributor.sol#L97-L119
However, when the network is congested, DEFAULT_ADMIN_ROLE of BribeVault may mistakenly send 2 updateRewardsMetadata() txs, and the transactions can be packaged into different blocks.
Lets say there 2 updateRewardsMetadata() tx with the same calldata, if someone claims rewards in between the two txs, then they can claim again after the second transaction.
Given:
Change to:
kphed (Redacted Cartel) disputed and commented:
Alex the Entreprenerd (judge) decreased severity to Medium and commented:
