You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Line 227 sets the volume of the original trade and lines 342 and 362 use it. As the lowest buy or the highest sell is being depleted, it will create another trade of the opposite type because of the conditional close, and that new trade will be the lowest sell or the highest buy, which is the one whose volume gets used on line 227. bSides (the record used to find the highest sell and lowest buy for a pair) could be used to record the highest volume of each side, but that would cause the grid to always be extended with the highest volume, and that's not always what we want. I'm leaving this alone and open for now.
It now uses ESLint with the settings described in .eslintrc.
The function in bot.js, howMuch(), is used to create trades for the correct amount (given the current assets) when the grid is extended.
It does not yet adjust existing open trades, so only partially addressing Issue #33, but fixing Issue #22.
Circular dependencies have been eliminated to ease debugging.
Most imports of other modules in this project have been moved to init and bot.
Tests are still needed for the balance function and the webpage among other things.
I`m guessing this happens because the previous trade is only partially executed and the code uses only one part of the actual volume.
The text was updated successfully, but these errors were encountered: