-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove options from create-protocol-parameters-update #388
Comments
For the record, as of 4def5e6, the cli for
|
As I'm about to log off for one week, I'm dumping the info I gathered here. As we would say in French, this is a bit zucchini tartlet (i.e. you can do it, but it doesn't taste great 😄). The presence of
So at first sight, it would be a bit complicated to remove those two fields from the parser. Note that this difficulty is not conway specific, it would be the same for all eras, since the concerned parameters are shared for all eras. |
On a second thought, there is a possible way that doesn't require changes nor in the ledger, nor in cardano-api:
@Jimbo4350, @newhoggy> any opinion on this? |
If I understand correctly @teodanciu's PR IntersectMBO/cardano-api#321, I believe it's anyway impossible to change the protocol's minor and major version in the ledger. But it's our parser that is off, as my previous message shows. Need to confirm on a more recent HEAD, in case I tested before Teodora's change. |
Confirming that the parser is still off after the integration of @teodanciu's PR, i.e. |
Following-up on my "On a second thought" message from above, I tried it and it doesn't work, because ultimately we want a single parser for However, while doing this, I found EraBasedProtocolParametersUpdate which is exactly designed to deal with different eras having different parameters. So I could:
|
Currently,
cardano-cli conway governance action create-protocol-parameters-update
gives the option of creating a proposal to change:protocol-major is used to trigger a hardfork See CDDL This kind of protocol parameter change is reserved to different type of governance action (Hardfork initiation), thus it makes no sense to have the option available under create-protocol-parameters-update
Reference from CIP1694
`
The text was updated successfully, but these errors were encountered: