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

Add updated bots to Vega Capsule #180

Open
zale144 opened this issue Jul 8, 2022 · 1 comment · May be fixed by #374
Open

Add updated bots to Vega Capsule #180

zale144 opened this issue Jul 8, 2022 · 1 comment · May be fixed by #374
Assignees

Comments

@zale144
Copy link

zale144 commented Jul 8, 2022

We expect that the primary use cases for VC initially will be people writing/testing their own bots and security researchers providing PoCs to supplement bug reports. In light of this we want to make the barrier to entry for using Vega Capsule as low as possible. This issue is to add a post start action in the config that:

  • adds the bots
  • creates 1 (or 2 max) markets
  • keeps them in trading mode until they settle

Note: the post start functionality must also be added to the frontend config file too as this is the one used as an example in the readme

@zale144 zale144 self-assigned this Jul 8, 2022
@gordsport gordsport added this to the 🤠 Oregon Trail milestone Jul 18, 2022
@gordsport gordsport linked a pull request Aug 10, 2022 that will close this issue
@gordsport gordsport changed the title Enable running liquidity bot Enable running updated liquidity bot Nov 9, 2022
@gordsport gordsport changed the title Enable running updated liquidity bot Add updated bots to Vega Capsule Dec 13, 2022
@zale144
Copy link
Author

zale144 commented Jan 10, 2023

The bots have been updated so that they can run in vegacapsule as binaries, as part of the post-start group. Vegacapsule has also been updated so that it can run any binary as part of the post-start-group.

Being able to setup a network in capsule along with the bots (or any other binaries) with a “one command” is possible provided that those binaries had already been installed in the local system.
Ideally, the capsule’s binary installer would install these binaries as part of the “bootstrap” command, however, it is designed to only install vega-related binaries, and modifying it so that it can install any provided binary would require additional work.

Another challenge is the issue of versioning. If the user wishes to run a “one command” and have all the binaries (network related and bots) installed and run as tasks in Nomad, the appropriate version of the bots needs to be matched with the version of Vega, and how that will be implemented is yet to be discussed.

@zale144 zale144 removed a link to a pull request Feb 1, 2023
@zale144 zale144 linked a pull request Feb 1, 2023 that will close this issue
@zale144 zale144 linked a pull request Feb 1, 2023 that will close this issue
@gordsport gordsport removed this from the 🤠 🤸 OT Stretch milestone Feb 6, 2023
@gordsport gordsport added this to the ☄️ Cosmic Elevator milestone Mar 20, 2023
@gordsport gordsport removed this from the ☄️ Cosmic Elevator milestone May 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants