Ensure on-chain that cache is synced #217
Labels
2 (Med Risk)
Assets not at direct risk, but function/availability of the protocol could be impacted or leak value
bug
Something isn't working
Handle
GreyArt
Vulnerability details
Impact
Currently, many core operations (like NestedFactory.create(), NestedFactory.swapTokenForTokens()) are dependent on the assumption that the cache is synced before these functions are executed however this may not necessarily be the case.
Proof of Concept
This flow is not aware that the cache is not in synced.
Recommended Mitigation Steps
Add a modifier to require that the cache is synced to all functions that interact with the operators.
The text was updated successfully, but these errors were encountered: