- Updated dependencies, but no changes to the interface.
-
Adapted to introduction of new
ChainOrder
type class. -
Changed the Praos chain order such that for two blocks
A
andB
by the same issuer with the same block number,A
is now preferred overB
only ifA
has a higher issue number and (new)A
andB
are in the same slot.This is in line with the motiviation for the issue number tiebreaker, and fixes the transitivity of the
Ord PraosChainSelectView
instance in a special case.
-
Allowed to configure Praos chain order to restrict the VRF tiebreaker based on slot distance.
-
Delete
Ouroboros.Consensus.Protocol.Praos.Translate
, moving the orphan instance toOuroboros.Consensus.Protocol.Praos
. -
Delete
Ouroboros.Consensus.Protocol.Translate
, movingTranslateProto
toOuroboros.Consensus.Protocol.Abstract
.
-
Remove unused
translateConsensusConfig
fromTranslateProto
. -
Add
praosRandomnessStabilisationWindow
toPraosParams
, allowing to configure in which slot the epoch nonce is snapshotted (which can now vary between different eras).
- Fix imports and type mismatches caused by
ouroboros-consensus
bumpingstrict-checked-vars
to^>= 0.2
.
- Praos'
LedgerView.lvMaxHeaderSize
type changed fromNatural
toWord16
. - Praos'
LedgerView.lvMaxBoxySize
type changed fromNatural
toWord32
.
- Replace all occurrences of
Ticked (LedgerView X)
withLedgerView X
. - Remove
Ticked (LedgerView X)
data family instances. - Rename
translateTickedLedgerView
totranslateLedgerView
.
- Update upper bound on
ouroboros-consensus
- Removed the
expose-sublibs
cabal flag, since Cabal/Nix handled it poorly. - Instead, added a
unstable-
prefix to the name of each sublibrary, to strongly indicate that we ignore them when evolving the package's version.
<a id='changelog-0.5.0.5>
- Relax upper bound on
ouroboros-consensus
- Relax upper bound on
ouroboros-consensus
- Rename
StrictMVar
toStrictSVar
- Relax bounds on
ouroboros-consensus
- Relax bounds on
ouroboros-consensus
- Apply new organization of Consensus packages.
Before this version, ouroboros-consensus-protocol
lived in a bundle of
packages with ouroboros-consensus
, thus the changelog was the same.
Before following a more structured release process, we tracked most significant changes affecting downstream users in the interface-CHANGELOG.md.