Bug info:Jason Reducefund webhook in the paper only works once at ID: 67a0752edd02487b100fc89a, after that it doesn’t work anymore, instead it has to be closed manually because the webhook has closed the transaction twice, it’s still running at ID: 67a0d46add02487b102eb394, and there’s something that makes me confused in the paper, Base order is calculated in total with leverage? because the BO is 500, the carrying cost is under $50.
Why doesn’t Gainium make something like 3commas signal bot that can go Long and Short in one bot?
Thank you for your report regarding the Reducefund webhook issue. We have received your information and will investigate the inconsistencies you’ve mentioned.
Could you please provide the deal ID for the transaction where the webhook closed it twice? This will assist us further in resolving the issue.
Additionally, your suggestion about a potential bot feature that can go Long and Short is noted, and we appreciate your input.
Regarding the Reduce Fund webhook inconsistency, we understand the issue and are working on improving the calculation of the reduce order size in futures bots when using a percentage-based approach. This will be included in our next release, so stay tuned!
For the Base Order clarification:
When setting up a futures bot, you configure the order size based on your preferences, not the actual carrying cost. Leverage affects the position size, but the order size you set remains unchanged. This means your Base Order (BO) will stay at 500, regardless of leverage or costs.
We appreciate your suggestion about creating a bot that can handle both long and short positions simultaneously, similar to 3commas’ signal bot. While this feature isn’t available yet, your feedback is valuable and will be considered as we develop new features.
Let us know if you have any more questions or concerns!
After fix, still in the same bot:
: Gainium app
deal id : 67a41b2b4f87b0a87a8291be.
Bot closed the deal on TP2 with an error message, there should still be TP3
