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

feat: CN 2 BN protocol communications #518

Draft
wants to merge 12 commits into
base: main
Choose a base branch
from
Draft

Conversation

AlfredoG87
Copy link
Contributor

@AlfredoG87 AlfredoG87 commented Jan 22, 2025

Description:
This PR introduces support the following CN 2 BN communication scenarios:

  1. When CN sends the expected block
  2. When CN sends the expected block but fails verification
  3. When CN sends an old (duplicate) block
  4. When CN sends a Future (block number ahead of the expected block number [currentBlock+1] )

Does not cover the following scenarios (pending):
5. When CN sends the expected block but BN already got it from somewhere else in a multi-stream environment.
6. When CN sends the expected block but BN fails Persistence (due to internal issues). / Internal Issues.

Related issue(s):

Fixes #519

Notes for reviewer:

This is a WIP, lacks UTs or actual UTs fixes (other than allowing them to compile)

Checklist

  • Documented (Code comments, README, etc.)
  • Tested (unit, integration, etc.)

Signed-off-by: Alfredo Gutierrez <[email protected]>
…on blockHash Verification using the signature of the blockProof instead of the prevHash of the next block and general improvements

Signed-off-by: Alfredo Gutierrez <[email protected]>
…f directly sending items to the notifier

Signed-off-by: Alfredo Gutierrez <[email protected]>
@AlfredoG87 AlfredoG87 self-assigned this Jan 22, 2025
@AlfredoG87 AlfredoG87 added Block Node Issues/PR related to the Block Node. New Feature A new feature, service, or documentation. Major changes that are not backwards compatible. labels Jan 22, 2025
@AlfredoG87 AlfredoG87 added this to the 0.4.0 milestone Jan 22, 2025
… as is the first block on the blockNode, once the blockNode has its own state and configuration, it will have to start from that one.

Signed-off-by: Alfredo Gutierrez <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Block Node Issues/PR related to the Block Node. New Feature A new feature, service, or documentation. Major changes that are not backwards compatible.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for Block Acknowledgement from BN to CN
1 participant