Skip to content
This repository has been archived by the owner on Sep 26, 2019. It is now read-only.

Ibft validates block on proposal reception #583

Merged
merged 5 commits into from
Jan 17, 2019

Conversation

rain-on
Copy link
Contributor

@rain-on rain-on commented Jan 16, 2019

Previously, IBFT only validated the header of the block on reception
of a proposal. However in order to minimise the risk of a "bad block"
being detected after a PreparedCertificate being created, it has been
decided to validate the whole block (i.e. exercise the transactions,
process the block and ensure hashes etc line up with the header).

There is still some (minor) risk of a failed block import, however
it is substantially reduced.

Previously, IBFT only validated the header of the block on reception
of a proposal. However in order to minimise the risk of a "bad block"
being detected after a PreparedCertificate being created, it has been
decided to validate the whole block (i.e. exercise the transactions,
process the block and ensure hashes etc line up with the header).

There is still some (minor) risk of a failed block import, however
it is substantially reduced.
@rain-on rain-on requested review from jframe and CjHare January 16, 2019 11:06
Copy link
Contributor

@CjHare CjHare left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rain-on rain-on merged commit b041062 into PegaSysEng:master Jan 17, 2019
@rain-on rain-on deleted the block_val_2 branch January 24, 2019 10:14
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants