[PROPOSAL 854][PASSED] Gaia v14.1 Upgrade

Hub Proposals Software Upgrade
22

Yes as the gov param only affects newly created validators and validators that are editing their settings.

23

Would be interesting to see some polling results of a public opinion on some of the proposed features in v15, e.g. “enforcement of 5% min commission” before they are implemented. I have the deepest belief that it would save a hell of a lot of time to dev teams and improve design efficiency =)

24

This was already put to a vote.

25

Then in my opinion there is no advantage of it being a gov paramter since it needs to be enforced to be fair for everyone.

26

Some big updates to the cryptographic equivocation feature are being included in a new release that will go through testing next week. This is to address concerns about:

  • Past equivocation on the Hub that has already been addressed via governance (e.g., Prop 818)
  • Multiple valid chains with the same chain-id, such as prior testnets, on which validators may have used their mainnet keys.

A feature has been added that does the following:

  • For new consumer chains:
    • Records the consumer chain block height at the time it enters the Hub’s security.
    • Filters out equivocation evidence that occurred prior to that block height.
  • For existing consumer chains:
    • Records the consumer chain block height at a specified time:
      • Neutron: block height 4552189
      • Stride: block height 6375035
    • Filters out equivocation evidence that occurred prior to that block height.

In effect, this means equivocation on consumer chains prior to entering the Hub’s security will not be punished by the Hub. For existing consumer chains which are already within the Hub’s security, any equivocation prior to today will not be punished.

I had raised some concerns specifically about a past noble-1 testnet, and this feature removes that risk in a very tidy way, as any equivocation taking place prior to to mainnet noble-1 joining the Hub’s security cannot be punished by the Hub.

Going forward, it is Hub validators’ responsibility to use new keys for each consumer chain and especially to not reuse keys on testnet chains that have the same chain-id as one currently on mainnet.

1 Like
27

Thats the issue. Instead of understanding the opinion on something, its proposed for voting.

28

Does this upgrade have the implementation of min 5% commission?

29

No, that is expected for v15. See Marius’s comment above.

1 Like
30

Thanks, and apologies for the laziness.

1 Like