Releases: consensus-shipyard/mir
Releases · consensus-shipyard/mir
v0.3.0
- After restoring the state of the app logic (by calling the app logic's
RestoreState
), Trantor now explicitly invokes theCheckpoint
method of the app logic with the very same checkpoint. - Code refactoring and cleanup without any impact on functionality.
v0.2.2
This release introduces consistent checkpoint certificates.
That means that Trantor now guarantees that the Checkpoint
function of the AppLogic
receives the same agreed-upon checkpoint certificate on all nodes. To this end, an extra round of agreement has been introduced to the protocol.
v0.2.1
Adds a few fixes around the newly-introduced ISS leader selection policy and makes it configurable.
v0.2.0
This release, apart from internal refactoring of the code, introduces a slight change in how Mir behaves towards its application:
- At the beginning of each epoch, it invokes the
NewEpoch
callback. Before this call was omitted in epoch 0 and when restoring state. - The nodes that propose transactions are now selected differently. If a node is suspected of being faulty (even if it is falsely), it might be suspended from proposing transactions.
v0.1.3
Fixes a bug in ISS' state restoration mechanism.
v0.1.2
- Fixes critical bug where a restarted node fails to catch up.
- Fixes typo in mircat.
v0.1.1
- Few new testing capabilities
- Convenience functions for checkpoint serialization
- Minor bugfix (shutdown)
First development release
The code, including all its interfaces, should not be considered stable yet.