The chainlink price feeds used inside the KeeperProxy
contract are assumed to always have 8 decimals when converting the price from chainlink's format to GMX's price feed format.
For example PEPE/USD Arbitrum Chainlink Price feed has 18 decimals: https://docs.chain.link/data-feeds/price-feeds/addresses?network=arbitrum&page=1&search=Pepe
PEPE/USDC is an available market on GMX V2: https://app.gmx.io/#/trade/long
The contract uses a constant value when converting chainlink price feeds to the GMX price feed format.
Most likely inside the KeeperProxy::_check
it will revert with "price offset too big"
https://github.com/CodeHawks-Contests/2025-02-gamma/blob/84b9da452fc84762378481fa39b4087b10bab5e0/contracts/KeeperProxy.sol#L194C5-L197C7
And it will be impossible to open/close trades within a market.
Retrieve the decimals from the chainlink price feed during initialization
and the store the decimals in a mapping of priceFeedAddress -->decimals.
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.
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.