You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is a parent issue for any improvements we will make to the vega capsule. The original MVP for Vegacapsule was that we would have system tests running locally, in CI and be able to use it to add/remove nodes (testing of validators joining/leaving and snapshots).
Currently DV does some configuration/set up that vegacapsule doesn't (multisig etc..), in order to make vegacapsule useful for development pleas capture any ideas in this ticket. I will then summarise into a bullet list *in this comment) ahead of a meeting to talk around them and prioritise into tickets to be delivered. Replicating DV may not be the best approach so we should add ideas of things we want/need maybe not just what we have today...
I think the having the validators added to the multisig control contracts is a must, because I don't think we can say that a valid network has been started if the validators perf-scores are all zero. The system-tests have a manual step to do this so you could argue that this would also benefit the system tests as well if this was brought into vegacapsule.
The next thing is what makes a usable network, and for me thats some parties with some vega staked because without being able to propose a market you can barely do anything. The config could look like:
parties {
count = 7 // generates 7 key pairs and stakes some vega
}
with something like vegacapsule state parties to see their public keys. DV also faucets in some builitin-assets, but I can live without this being automatic because its much much easier to do and depends a lot more on your genesis file. But staking vega is something you'll always need to do.
@wwestgarth I think number point number 1 make a lot of sense. @jeremyletang has mentioned that we can build a CLI to Vega to allow users to call ethereum contracts.. That would help a lot with it.
The second point - yeah sounds reasonable but it should not be part of tool itself. I think the system of plugins should be introduced and this could be one of them.
@fkondej@daniel1302 - Are there any plans to have vegacapsule running in a Private network - similar to what we have for dv?
Think having it will remove a lot of dependency from the local machine.
This issue is a parent issue for any improvements we will make to the vega capsule. The original MVP for Vegacapsule was that we would have system tests running locally, in CI and be able to use it to add/remove nodes (testing of validators joining/leaving and snapshots).
Current issues list
Currently DV does some configuration/set up that vegacapsule doesn't (multisig etc..), in order to make vegacapsule useful for development pleas capture any ideas in this ticket. I will then summarise into a bullet list *in this comment) ahead of a meeting to talk around them and prioritise into tickets to be delivered. Replicating DV may not be the best approach so we should add ideas of things we want/need maybe not just what we have today...
Suggestions:
The text was updated successfully, but these errors were encountered: