We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Add the ability to pass sub-account names from the strategy in order to trade them on separate sub-accounts.
This is primarily to make PnL calculations more manageable. Also provides isolation between strategies for better risk mitigation.
The text was updated successfully, but these errors were encountered:
Nice - This means that Strategy will need the following:
a) The name of the sub-account. b) The env-var from which to load the API key.
The env-vars should be namespaced, e.g. FTX_KEY_SUBACCOUNT As we currently have only one strategy, this can be done now or later.
Sorry, something went wrong.
Would it be a bad idea to have API keys managed directly in the admin panel?
No branches or pull requests
Add the ability to pass sub-account names from the strategy in order to trade them on separate sub-accounts.
This is primarily to make PnL calculations more manageable. Also provides isolation between strategies for better risk mitigation.
The text was updated successfully, but these errors were encountered: