Skip to content
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

BFT Block Puller: A block validator that is updated immediately after a config block is sent to gossip / orderer-pull-buffer #4346

Closed
Tracked by #4240
tock-ibm opened this issue Aug 3, 2023 · 1 comment

Comments

@tock-ibm
Copy link
Contributor

tock-ibm commented Aug 3, 2023

In the peer, the blocks and headers fetched from the orderer are validated using a component in gossip that is validated every time a config block is committed. We need to change that to a mechanism that keeps an earlier view of the config, that is, a config that is updated when a block is given to gossip, rather than committed.

This kind of mechanism already exists in the orderer block puller, and when we unify the two implementation we will create a single instance that behaves in that manner.

@tock-ibm tock-ibm changed the title A block validator that is updated immediately after a config block is sent to gossip A block validator that is updated immediately after a config block is sent to gossip / orderer-pull-buffer Aug 3, 2023
@tock-ibm tock-ibm changed the title A block validator that is updated immediately after a config block is sent to gossip / orderer-pull-buffer BFT Block Puller: A block validator that is updated immediately after a config block is sent to gossip / orderer-pull-buffer Aug 3, 2023
@tock-ibm
Copy link
Contributor Author

Make sure to incorporate #4490 in this PR

@tock-ibm tock-ibm closed this as completed Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant