
Pinkcoin; getstakinginfo output clarification/update
Repository
https://github.com/Pink2Dev/Pink2
Components
As reported, there is an issue around the output of the RPC getstakinginfo, the output has
{
"enabled" : true,
"staking" : false,
"errors" : "",
...
}
However there is no method to absolutely diagnose why enabled may be true, whereas staking may be false. My original suggestion was to toggle the enabled boolean with the wallet being locked/unlocked.
Proposal
After discussion with the dev it appears the enabled boolean has another usage, but this still leaves the diagnosis of staking: false as somewhat hard to tie down, so there is the possiblility to enable some messages in errors: ""
Mockups / Examples
{
"enabled" : true,
"staking" : false,
"errors" : "wallet locked",
...
}
{
"enabled" : true,
"staking" : false,
"errors" : "out of sync",
...
}
Benefits
Improved clarity for uses over common issues that may be preventing their node from staking and supporting the network.
GitHub Account
Leave Pinkcoin; getstakinginfo output clarification/update to:
Read more #utopian-io posts
Best Posts From scalextrix
We have not curated any of scalextrix's posts yet. But you can encourage our curation team to review posts by visiting them regularly and by referring other readers. Because we give priority to frequently read content.
More Posts From scalextrix
- My Actifit Report Card: October 4 2020
- My Actifit Report Card: September 29 2020
- My Actifit Report Card: September 28 2020
- My Actifit Report Card: September 27 2020
- My Actifit Report Card: September 24 2020
- My Actifit Report Card: September 23 2020
- My Actifit Report Card: September 22 2020
- My Actifit Report Card: September 21 2020
- My Actifit Report Card: September 20 2020
- My Actifit Report Card: September 16 2020