There is an issue in the VaultReader contract position validation logic that incorrectly blocks the opening of valid positions and can cause significant trading disruption. The issue stems from incorrect validation in the willPositionCollateralBeInsufficient function.
In the willPositionCollateralBeInsufficient function, the function always assumes insufficient collateral if position = 0 without validating the actual collateral amount provided, does not check market-specific minimum collateral requirements, and does not consider the proposed position size and leverage. This may prevent new positions from being opened that are actually valid.
All new position openings are blocked
Valid trades with sufficient collateral are rejected
Users cannot enter positions even with excess collateral
1.User attempts to open a new position with valid collateral:
2.System calls willPositionCollateralBeInsufficient to validate
3.Function sees position size is 0 (new position)
4.Returns true automatically, rejecting the valid trade
5.Position is blocked despite having sufficient collateral
Manual review
Remove immediate true return when position = 0, add minimum collateral required based on position size, and add safety buffer to avoid too close liquidation.
There is no real proof, concrete root cause, specific impact, or enough details in those submissions. Examples include: "It could happen" without specifying when, "If this impossible case happens," "Unexpected behavior," etc. Make a Proof of Concept (PoC) using external functions and realistic parameters. Do not test only the internal function where you think you found something.
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.