There is a serious limitation for the strategies we develop for trading using signals from TradingView at Finandy: the inability to calculate the number of contracts based on the current deposit amount.

More on this topic by requesting a feature in this thread → https://ru.logs.finandy.com/feature-requests/p/0c3770

To be able to bypass this limitation, the make.com service has implemented a chain that, when a signal is received, additionally requests the account balance and, based on the response, writes the required number of contracts to the “amount” variable. A JSON signal is then sent to Finandy.

But to receive a signal from a third-party service, you need to enter “Allowed IP”. At the moment, only 1 incoming IP is available for input.

The make.com service comes from 3 IP addresses (https://www.make.com/en/help/connections/allowing-connections-to-and-from-make-ip-addresses), which change depending on the load on their servers.

Thus, the probability of a signal passing through tends to 0%, not even to 1/3, because IP addresses do not change naturally, but by accident.

It makes no sense to switch to another service from which 1 IP address comes from, because several IP addresses are a normal and necessary practice for distributing the load on servers. The service from which 1 IP address currently comes from can be expanded at any time and the problem will reappear.

In general, due to this limitation, according to our strategies, it is simply impossible to scale the number of instruments we want to launch a strategy on at the same time. We can only trade one instrument at a time.

I already talked about this in a chat on April 25 (https://t.me/finandyru/192915/220921), where the conversation was summarized as follows:

— Denis Kondratiev: Is there an urgent need to make several ip's on 1 hook?

— Me: yes

— Denis Kondratiev: Okay, we'll suggest it to the developer. Stay tuned for more news. We will notify you how we will introduce this functionality

Please correct this restriction. If possible, in upcoming updates.

I could be wrong, but such an extension of functionality does not look technically difficult and seems like a minor task.

Please let us know if you already plan to complete this task. Solving this problem is of paramount importance for us and our community.