Lines of code

Vulnerability details

MarketSequencer.initCurve() can callLiquidityMining.initTickTracking() any number of times, because their is no restriction for reinitialization. As stated in the comment section, putting the caller in charge of not reinitializing can lead to an unintentional reinitialization of the liquidity curve for the pool. This can lead to over-writing tick state data.

Recommendation: Add a state variable that checks if the liquidity cure has been initialized or that tick tracking has been initialized.

Assessed type

Other

The text was updated successfully, but these errors were encountered:

All reactions