Vasil protocol parameters / genesis configuration

[KtorZ]

Will there be any new / altered protocol parameters or genesis configuration for the upcoming Vasil hard-fork (talking about parameters themselves / their semantic here, not about a change in their values)?

Should there be any, would it be possible to document them as a CIP before the hard-fork is actually submitted to the network, in a similar fashion to what was done for Alonzo's parameters?

Thanks a lot 🙏

[JaredCorduan]

The Babbage era does not introduce any new protocol parameters (so, in particular, there is no Babbage config). There is one small semantic change which will need to be accounted for in the HFC translation from Alonzo, namely coinsPerUTxOWord is changing to represent lovelace per byte (not word). Does this merit a CIP?

(Edit: I just checked, we haven't actually made this change yet, the semantics are still tied to 8 bytes, but I think we still want to change this...)

[KtorZ]

Thanks @JaredCorduan 👍

Does this merit a CIP?

Arguably yes, we want a CIP for all era parameters changes; though if that's the only change it can be very short :)
Shall I keep this issue open as a "reminder" and close it once we've got the CIP out, Kevin is usually doing this so that may already be on his TODO list.

[JaredCorduan]

yea, let's keep it open, I'm excited to get the chance to embrace the CIP process more myself. thanks for opening this!

[KtorZ]

(for the record, related previous CIPs)

https://github.com/cardano-foundation/CIPs/tree/master/CIP-0009#readme

https://github.com/cardano-foundation/CIPs/tree/master/CIP-0028#readme

[JaredCorduan]

cardano-foundation/CIPs#265

[JaredCorduan]

I'm going to close this issue here since I have a PR up for the CIP.