The LiquidationPool::position
function returns information about all the money staked in the contract, including pending and consolidated stake. However, it doesn’t take into account the poolFeePercentage
from LiquidationPoolManager
, leading to false information. Trying to anticipate the fees that have not yet been distributed results in an inaccurate representation of the staker's holdings. The returned information is higher than the actual value, which can potentially disappoint stakers who rely on this function to assess their holdings.
Users will perceive a lower value than indicated by the position
function due to the lack of consideration for poolFeePercentage
. This is particularly impactful since users often rely on the position
function to assess their holdings, given that the positions
array is private. Consequently, users might feel disappointed or confused by the inaccurate information, making it challenging for them to accurately determine the real amount for calls to LiquidationPoolManager::decreasePosition
. Users would need to calculate the actual amount themselves, introducing complexity and potential frustration.
Adjust the logic of the LiquidationPool::position
function to account for LiquidationPoolManager::poolFeePercentage
. An example of the modification is provided below:
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.