-
Notifications
You must be signed in to change notification settings - Fork 22
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
Tasks Executer #8
Comments
Maybe set the condition of "Market Open "%" of available_balance" with an function that is based on % of portfolio (and if that amount is not available to then use the available balance). That should help with ensuring that profitable trades make up for lost trades in the win/lose ratio. |
@JerryVdV You mean to divide balance into portfolio as well? (Eg. always take 30% of total Balance as Solana positions with a max of $ value at any time)? |
Yes sir, otherwise the positions will get smaller the more there are open
at any given time. In theory making it harder to recuperate losing trades
(if those had a larger position in terms of the margin).
Just a thought off course.
|
Got it, nice idea. Will add as a separate ticket. |
Are you planning to try limit close? |
Would be nice yes.
…On Mon, 22 Nov 2021 at 08:22, amesas ***@***.***> wrote:
Are you planning to try limit close?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHBEZDAXY5ZINVHLLU326LLUNHVUBANCNFSM5H6I4AHQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
@amesas Yes on the list |
Uses a First-In-First-Out (FIFO) approach to execute the Tasks:
Tasks to support:
NOTE: If Hedge Mode is not enabled, a "CLOSE" is an order with "Reduce-Only".
The text was updated successfully, but these errors were encountered: