https://github.com/Pink2Dev/Pink2
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.
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: ""
{
"enabled" : true,
"staking" : false,
"errors" : "wallet locked",
...
}
{
"enabled" : true,
"staking" : false,
"errors" : "out of sync",
...
}
Improved clarity for uses over common issues that may be preventing their node from staking and supporting the network.
