Validator-metadata/properties wonky

[opsecx]

Created a testnet (alpaca) validator with both commission-rate and max-commission-rate-change.

Later querying the validator metadata yields the following:

"Only one of the commission rate and max commission change per epoch was found for validator (redacted) in epoch 420. This is a bug and should be reported."

[opsecx]

Not quite sure how this happened, ran a fairly standard init-validator command, for reference:

namadac init-validator --account-keys (redacted) --signing-keys (redacted, same as account-keys) --commission-rate (redacted) --max-commission-rate-change (redacted) --email (redacted)

no errors from cli and went straight through

[opsecx]

Also not sure if this will keep the validator from functioning or cause issues on chain, will report on this. Would be interested to hear if anyone else is seeing this on Alpaca.

[brentstone]

Mind reaching out on discord to me to help debug? Curious to know your address. @Brent

[opsecx]

Validator looks to be in consensus set and working well. I wonder what will happen if I change commission-rate

[opsecx]

It looks to respect the set max-commission-rate-change when running chance-commission-rate. (ie can't change rate beyond initially set limits). not sure why cli displays the error as above.

[opsecx]

Update: As discussed with Brent, it displays fine now. Anyone else seeing this when querying newly created validators before becoming active?

[tzemanovic]

hi, thanks for the report! I confirm the issue is that the commission-rate is set at pipeline epoch offset but it tries to read it from the current epoch