-
Notifications
You must be signed in to change notification settings - Fork 628
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node_key missing in /status endpoint for non-validator nodes #7672
Comments
It looks like, |
Shoot. I didn't even notice. I would change this and drop |
This is super confusing and in long run, as painful as it is, I would break people scripts, but scream loud that this is going to happen. |
Currently, response to the /status request returns a `node_key` field. However, the field does not include node key but rather validator key. Rename this field to `validator_key`. Furthermore, reuse `node_key` for the actually node key. The massive problem with this change is of course that it will silently break any existing code which thinks node_key in the response is the validator key. Fixes: near#7672
I think node key should go into public_addrs but in reality I think it might not matter. The node will connect, notice node key is different and update its bookkeeping. @pompon0, any thoughts on what to do here? |
Then why you created |
Under
/status
endpoint,.node_key
is missing for an RPC node. At present, from my observation, only Validators have.node_key
present. I think all nodes should have that json entry, no matter are they validator, or not.From above output my expectation from operational perspective would be that all nodes would return public part of node key via
curl -s rpc:3030/status | jq -r .node_key
however non-validators returnnull
.The text was updated successfully, but these errors were encountered: