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:
- 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.
- 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!
Wrong pub_key registered — need UpdatePubKey function
What happened
During registration, I accidentally submitted the
node_idpub_key (P2P) instead of thevalidator_keypub_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
g1e5sxezpafa8lcv5xu3nmw4plz30mnepq2wv9xsgpub1pggj7ard9eg82cjtv4u52epjx56nzwgjyg9zp0t2w0z50qfz9zc9vcld59p8f77pw052whd8w6rpksfqrk2rh877ycv0xmgpub1pggj7ard9eg82cjtv4u52epjx56nzwgjyg9zqlfnw26wg5a6wph2k2cqhdwplq73nrckcz755e85yy047ykmlvhtdvw077Both keys start with the same prefix (
gpub1pggj7ard9eg82cjtv4u52epjx56nzwgjyg9z) and only diverge after that, making this a very easy mistake to make.What I need
Either:
UpdatePubKeyfunction added to the contract so validators can correct their registered pub_key — this would help anyone who faces this same issue in the future.Notes
The current contract exposes
UpdateMoniker,UpdateDescription,UpdateServerType, andUpdateKeepRunning, but there is no way to update thePubKeyfield once registered. Given thatpub_keyis the most critical field for validator operation, I think this is a gap worth addressing.Thanks in advance!