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
{{ message }}
This repository has been archived by the owner on Feb 1, 2024. It is now read-only.
The bot is unable to submit transactions if it has hit capacity limits for non-XLM assets. This requires at least 2 levels in the strategy.
Expected behavior
I think the correct behavior in this situation is for the bot to handle this smoothly.
Frequency
The frequency is: Sometimes (in the above scenario)
Steps To Reproduce
Here are the steps to reproduce the issue:
The bot should be configured to place at least 2 levels.
Use a price feed such as kraken so there is some variability in the asset price.
Configure the bot with the buysell strategy for an amount that will more than max out the non-XLM asset it is selling after it successfully places the full first level.
Start the bot.
Very soon the bot will have op_underfunded errors in the transaction result for the first operation.
Possible Solution
The native XLM asset is configured to provide a operational buffer of 20 XLM which prevents this issue from being hit with the XLM asset. A similar buffer can be added for non-native assets.
related to #40
Describe the bug
The bot is unable to submit transactions if it has hit capacity limits for non-XLM assets. This requires at least 2 levels in the strategy.
Expected behavior
I think the correct behavior in this situation is for the bot to handle this smoothly.
Frequency
The frequency is: Sometimes (in the above scenario)
Steps To Reproduce
Here are the steps to reproduce the issue:
op_underfunded
errors in the transaction result for the first operation.Possible Solution
The native XLM asset is configured to provide a operational buffer of 20 XLM which prevents this issue from being hit with the XLM asset. A similar buffer can be added for non-native assets.
Your Environment
Context
I am unable to adjust the bot's amounts as desired or run the bot reliably because of this bug.
Attachments
The text was updated successfully, but these errors were encountered: