You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When in Babbage protocol version 8 and doing a proposal update to Conway protocol version 9, cardano-cli query tip will show the expected switch from Babbage to Conway era at the next epoch transition.
Now, while in Conway era, cardano-cli querying protocol-parameters still shows protocol version as 8.
# While in Conway era -- check query tip output:
> cardano-cli query tip
{
"block": 24516,
"epoch": 5,
"era": "Conway",
"hash": "86a514fce42ad660ed587b0afe4a731bd01090d82de2225c5a9e15517a8ca068",
"slot": 492091,
"slotInEpoch": 60091,
"slotsToEpochEnd": 26309,
"syncProgress": "100.00"
}
# Then query protocol parameters, however still show version 8:
> cardano-cli query protocol-parameters | jq .protocolVersion
{
"major": 8,
"minor": 0
}
# The proposal update logged in node does show pvMajor Version 9 for the hard fork:
Event: LedgerUpdate (HardForkUpdateInEra S (S (S (S (S (Z (WrapLedgerUpdate {unwrapLedgerUpdate = ShelleyUpdatedProtocolUpdates [ProtocolUpdate {protocolUpdateProposal = UpdateProposal {proposalParams = PParamsUpdate (BabbagePParams {bppMinFeeA = SNothing, bppMinFeeB = SNothing, bppMaxBBSize = SNothing, bppMaxTxSize = SNothing, bppMaxBHSize = SNothing, bppKeyDeposit = SNothing, bppPoolDeposit = SNothing, bppEMax = SNothing, bppNOpt = SNothing, bppA0 = SNothing, bppRho = SNothing, bppTau = SNothing, bppProtocolVersion = SJust (ProtVer {pvMajor = Version 9, pvMinor = 0}), bppMinPoolCost = SNothing, bppCoinsPerUTxOByte = SNothing, bppCostModels = SNothing, bppPrices = SNothing, bppMaxTxExUnits = SNothing, bppMaxBlockExUnits = SNothing, bppMaxValSize = SNothing, bppCollateralPercentage = SNothing, bppMaxCollateralInputs = SNothing}), proposalVersion = Just (ProtVer {pvMajor = Version 9, pvMinor = 0}), proposalEpoch = EpochNo 4}, protocolUpdateState = UpdateState {proposalVotes = [KeyHash "c1ad22cabb342cbb83ce3859708232f4945ccb669e9b5f932cffc0ed",KeyHash "c264bca994a3a5deee5a1d9b92a3d7e9d6cbdb81f2f6989bb7f7b437",KeyHash "d4bf7eb45b72dffa5ac33d5c902fe409e4e611f2e9a52fb0d09784c3"], proposalReachedQuorum = True}}]})))))))
The text was updated successfully, but these errors were encountered:
The current hypothesis is that the protocol update doesn't actually happen when transitioning to Conway, because Translation is losing the update proposals from the LedgerState. The explanation and plan is in this consensus ticket
ClosesIntersectMBO/cardano-ledger#3491 in
an ad-hoc but minimal fashion.
Primary motivation is to fix this bug on Sanchonet without having to
wait for the full HFC refactoring (see #345) that we will probably end
up with.
When in Babbage protocol version 8 and doing a proposal update to Conway protocol version 9, cardano-cli query tip will show the expected switch from Babbage to Conway era at the next epoch transition.
Now, while in Conway era, cardano-cli querying protocol-parameters still shows protocol version as 8.
The text was updated successfully, but these errors were encountered: