Skip to content

Feature request: add UpdatePubKey function to https://test11.testnets.gno.land/r/gnops/valoper #43

@RaulBernal

Description

@RaulBernal

Wrong pub_key registered — need UpdatePubKey function

What happened

During registration, I accidentally submitted the node_id pub_key (P2P) instead of the validator_key pub_key (consensus). Both keys share a similar prefix which made it easy to mix them up.

As a result, my validator is not signing blocks because the registered pub_key does not match the actual consensus key.

Details

Both keys start with the same prefix (gpub1pggj7ard9eg82cjtv4u52epjx56nzwgjyg9z) and only diverge after that, making this a very easy mistake to make.

What I need

Either:

  1. A new UpdatePubKey function added to the contract so validators can correct their registered pub_key — this would help anyone who faces this same issue in the future.
  2. Or a manual correction of my registration by an admin (if that action is possible)

Notes

The current contract exposes UpdateMoniker, UpdateDescription, UpdateServerType, and UpdateKeepRunning, but there is no way to update the PubKey field once registered. Given that pub_key is the most critical field for validator operation, I think this is a gap worth addressing.

Thanks in advance!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions