Some solvers report Ignoring ill-defined AMM "3": Attempt to create an AMM with non-positive token balance. indicating that we are sending "empty" AMMs.
There are definitely some constant product AMMs that have either 0 or very little liquidity.
It probably makes sense to filter out any pool that has < X$ worth of tokens in them.
If an AMM does not actually have any liquidity we should not send it to the solver.
Additionally we should not attempt to fetch its state again on the next block if it's empty.
Background
Some solvers report
Ignoring ill-defined AMM "3": Attempt to create an AMM with non-positive token balance.
indicating that we are sending "empty" AMMs.There are definitely some constant product AMMs that have either 0 or very little liquidity. It probably makes sense to filter out any pool that has
< X$
worth of tokens in them.Examples:
instance.json
Acceptance criteria
If an AMM does not actually have any liquidity we should not send it to the solver. Additionally we should not attempt to fetch its state again on the next block if it's empty.