davidsiska-vega / vega_mm_bot_rust Goto Github PK

We don't check data node liveness, so bot may die if the data node it's using goes down. Add some heuristic and try switching data nodes both for API reads and transaction submission.

We should estimate order arrival frequency separately for buy and sell sides.

We should check whether the time to infinity horizon strategy can make use of this additional info and if yes use it, if not look at what computation to do to utilise it.

PoW is constant and minimum which means bot can get blocked, especially if it's using high frequency of submissions.

The ideal way to solve it would be to count the transactions it's doing and figure out the PoW difficulty needed.

A simpler way would be to add a config where optionally the difficulty level is incremented by that amount - user then configures this manually.