Submitted by pauliax
I see no re-entrancy mitigations. Contracts interact with various outside sources (tokens, aave pools, other possible strategies that may be added in the future, etc). so, for instance, now you have to be careful and do not allow tokens that have a receiver callback (e.g. erc777) or untrustable sources of yield (strategies).
Consider using ReentrancyGuard on main action functions.
Evert0x (Sherlock) acknowledged
