Fix bech32 prefixes of committee keys

[smelc]

Changelog

- description: |
    Fix that bech32 prefixes for CC keys were incorrect
# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  - breaking       # the API has changed in a breaking way
  # - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  # - improvement    # QoL changes e.g. refactoring
  - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
  # - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
  # - documentation  # change in code docs, haddocks...

Context

Was looking at CC keys code for IntersectMBO/cardano-cli#586 and stumbled upon what looked like a copy/paste typo.

How to trust this PR

• That is a good question. Probably we should be testing this in cardano-cli.
• That being said, I ran cardano-cli's tests against this PR, and all tests passed. So at least we're not breaking anything, but it's consistent with my impression that we are not testing this.

Checklist

• Commit sequence broadly makes sense and commits have useful messages
• New tests are added if needed and existing tests are updated. See Running tests for more details
• Self-reviewed the diff

[smelc]

cc @gitmachtl, as I'm a bit surprised we are only seeing this now, but maybe this wasn't tested yet?

[Ryun1]

Hey @smelc

We have defined bech32 prefixes for committee keys already defined via CIP-05; here.

[smelc]

Thanks @Ryun1! I amended my changes so that they match the CIP-05.

Great catch 😍

[Ryun1]

Thanks @Ryun1! I amended my changes so that they match the CIP-05.

Great catch 😍

Thank @gitmachtl for giving me the heads up 🤩