Submitted by DarkTower
The Abracadabra team configures gas yield for all contracts in the Blast L2 except for the LockingMultiRewards contract. Therefore, gas yields accrued on the LockingMultiRewards staking contract since deployment will be lost as it was never configured using BlastYields.configureDefaultClaimables. If the contract holds native yield reward tokens in ERC20 such as WETHRebasing or USDB then these rewards will also be lost.
During deployment of the staking contract on Blast, the staking contracts gas yield mode should be configured to be able to claim accrued gas fees spent on the contract. We know that the bootstrap() function spawns the LockingMultiRewards staking contract below.
However, in the LockingMultiRewards contract, the BlastYields.configureDefaultClaimables function does not exist in the LockingMultiRewards constructor to configure the staking contracts gas yield mode. Therefore, gas yield cannot be claimed LockingMultiRewards.
We believe this to be a mistake by the Abracadabra team as all other contracts that use substantial gas except for this contract had their gas yield mode configured/ The gas spent for this contract will be very substantial considering that users will spend substantial amounts of gas claiming from the staking contract. Therefore the Abracadabra is missing out the gas fees in this contract by not configuring the gas yield mode and possibly native yield in such as WETHRebasing or USDB if such tokens are used
Foundry
Configure the Blast gas yield mode for the LockingMultiRewards staking contract in the constructor and expose a function for admin to collect the yields. Additionally, also consider whether Blast points need to be configured here.
cccz (Judge) commented:
Note: For full discussion, see here.
