-
This project never ended up being what it was envisioned as. Currently it just votes on the superblock for DashCore and votes to remove expired proposals, and that functionality could be absorbed into…
-
OS : Ubuntu 20.04.6 LTS (GNU/Linux 5.4.0-169-generic x86_64)
Dashmate : 0.25.21
Dash Core : 20.0.4
CPU : Intel(R) Xeon(R) Gold 6136 CPU @ 3.00GHz / 8 cores
RAM : 24GB
Storage : 600GB
Masterno…
-
## Expected Behavior
Service configs (dash.conf, config.toml, etc..) are updated and rerendered only when necessary, i.e when config was updated.
## Current Behavior
Dashmate renders serv…
-
## Expected Behavior
Such dashmate e2e cases should exists:
* dashmate commands succesfully executes after migrations applied
* dashmate start/stop --platform works as expected
* dashmate …
-
## Expected Behavior
`dashmate status mastrenode` should show enabled / total count for each node groups, like total, hpmn and regular. Just like we have in the dashcore
Example:
## Current Behavior
Fails with `Running services detected`
…
-
## Expected Behavior
Seed nodes should only run core tenderdash and seed containers, without dapi, envoy and the rest of the stuff
## Current Behavior
Legacy mn_evo_services role is used …
-
** Provide a general summary of the issue in the Title above **
After Pasta released Dash Core v19.3.0 on Mainnet yesterday, i expected to just update using Dashmate. But it seems after issuing com…