fix(dashmate): status command shows tenderdash error before activation #2028
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue being fixed or feature implemented
Tenderdash RPC is only available after a platform activation, which will happen in 3 weeks from now. Since TD RPC is used to perform healthcheck on the service, we need to an additional check for softfork activation for the mainnet network configs.
What was done?
Added a
getblockchaininfo
core rpc request in thestatus platform
commandIt will only query tenderdash if the mn_rr softfork is already active.
An additional status line about platform activation time was also added.
How Has This Been Tested?
Locally
Breaking Changes
No
Checklist:
For repository code-owners and collaborators only