Dynamic price filter no overlapping deals

[d_yo_r]

As we have just learnt from here

Issue with new Feature Uver&Under no overlapping deals

Hi, I have seen an issue regarding the new feature no overlapping deals. I have setup a bot to test the new function, therefore I start the Bot ASAP and set the value (over and under to 1%). Even if the price was rising 4% it did not open any new deals? can someone take a look at this? Thanks. https://app.gainium.io/bot/67dd11890cc65482bd27a240?a=4591&aid=share-bot&share=8d3ae090-708b-4159-835d-8d214dd082b8

and the Telegram chat

Ares in Gainium

“Is not intuitive that no overlapping deals should not include the dcas, that’s the specific way you use your strategy.”

But my point of view was and is, that the dynamic price filter without overlapping was and is meant to help us build a DCA grid. That is the DCA deals start at a certain distance and each of them DCAs separately.

The overlapping caused deals to start at almost the same level, which resulted in several funds stacked at the same level. That’s why this new feature should help to avoid the overlapping.

But it shouldn’t take the DCA of the deals into account to prevent deals in the DCA range of another deal. Only the entry price (respective the average price - where I currently have a use case for) should be taken into account to figure out where the next deal can be started.

Unfortunately

… reading back my own “Proposed solution” wasn’t that clear at this point.

Dynamic price filter no overlapping deals

Let’s ignore the fact that you mocked me not only directly, but also by asking Rosanno for an explanation instead of me, and try to focus on a simpler suggestion. (By the way, DeepSeek understood my solution perfectly.) Your current implementation is already pretty close to preventing stacked deals. It just needs the following tweak, for example. Proposed Solution: Remember the Last Deal’s Price: Track the price of the most recent deal (regardless of direction) as the reference point for …

My text was talking about deals where I meant the entry price of previous deals.

That’s why I have to modify my above idea. The changes are small but important.

Proposed Solution (Version 2):

1. Remember the Last Deal’s Entry Price:

   • Track the entry price of the most recent deal (regardless of direction) as the reference point for the dynamic price filter. (That’s what Gainium already does.)

2. Check for Existing Deals in an Epsilon Range:

   • Before opening a new deal, check if there’s already an open deal with an entry price in

     • either a small delta-epsilon range (e.g., 0.1% < currently relevant deviation over or under) around the current price. (This delta/epsilon (for under/over) could even be configurable.)

     • or the configured deviations for under and over.

   • If such a deal exists, do not open a new deal. Instead, update the “last deal’s price” reference to this existing deal’s entry price.

3. Apply the Dynamic Filter:

   • If no deal entry price exists in the epsilon range, proceed with opening the new deal and update the “last deal’s price” reference to this new deal’s price.