External calls can fail accidentally or deliberately, which can cause a DoS condition in the contract. To minimize the damage caused by such failures, it is better to isolate each external call into its own transaction that can be initiated by the recipient of the call. This is especially relevant for payments, where it is better to let users withdraw funds rather than push funds to them automatically (this also reduces the chance of problems with the gas limit).
This does not appear to be actionable feedback. e.g. withdrawERC1155 only acts on inputs provided -- so what should be done differently here? Without additional context this seems to be invalid.
DoS with failed call in
Basket.sol
Impact
External calls can fail accidentally or deliberately, which can cause a DoS condition in the contract. To minimize the damage caused by such failures, it is better to isolate each external call into its own transaction that can be initiated by the recipient of the call. This is especially relevant for payments, where it is better to let users withdraw funds rather than push funds to them automatically (this also reduces the chance of problems with the gas limit).
Proof of Concept
CreationTX
call initialise
call withdrawERC1155
Tools Used
mythx
Recommended Mitigation Steps
It is recommended to follow call best practices: