Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improvements on the signals workspaces - $SA 2M bounty! #4728

Open
julian-molina opened this issue Feb 1, 2023 · 2 comments
Open

Improvements on the signals workspaces - $SA 2M bounty! #4728

julian-molina opened this issue Feb 1, 2023 · 2 comments
Labels

Comments

@julian-molina
Copy link
Member

There have been recent discussions on what is the right approach to recover from potential outages in the signals service from the perspective of followers.

The first and foremost conclusion is that automatically resuming trading is not desirable, as many things may have happened during the outage.

This bounty is about implementing the lead developer's recommendations at the level of the Trading System in the followers' workspaces (and, if necessary, in the broadcaster's workspace), to properly manage followers' risk.

A. If the follower stops getting signals, the receiving Trading System must detect the issue. It should react by executing orders to move balances, close positions, or do whatever is needed to protect the followers' capital.

A mature signal should include the conditions at the follower's workspace to handle missing signals at the different stages of execution of the strategies, on the follower's end.

The implementation should allow for followers' input/configuration so that followers may decide what specific actions to take when that makes sense. The options should be properly documented and made available to followers in a clear manner. The implementation could involve userDefinedParameters that the follower may use to declare what is the preferred handling option for such events.

We would call this a GRACEFUL SHUTDOWN strategy.

B. Another situation that must be handled is when the signal provider -- for whatever reason -- restarts (or simply starts) the trading session broadcasting signals.

In this case, the currently existing follower's workspace has no way to know that the session was restarted, which opens up doors to all sorts of problems.

The solution is to have a WARM UP strategy: a strategy that is triggered when the broadcaster starts broadcasting. This strategy should move the balances of assets into the right asset. This would solve the issue of the follower reacting properly to a new trading session started by the broadcaster, and also avoid the current confusion of followers on how to declare the initial balance (base or quoted asset). Then followers could declare the balance in any of the assets, with no consequence whatsoever.

@Luis-Fernando-Molina
Copy link
Member

I will pledge another 1M SA for this bounty

@NAmorim NAmorim changed the title Improvements on the signals workspaces: 1M SA bounty! Improvements on the signals workspaces: 2M SA bounty! Feb 14, 2023
@julian-molina julian-molina changed the title Improvements on the signals workspaces: 2M SA bounty! Improvements on the signals workspaces - $SA 2M bounty! Aug 9, 2023
Copy link

stale bot commented Feb 6, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Stale Issue label Feb 6, 2024
@stale stale bot closed this as completed Feb 13, 2024
@Awhiteweb Awhiteweb removed the stale Stale Issue label Feb 13, 2024
@Awhiteweb Awhiteweb reopened this Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants