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

Block Validation mechanism & behavior is implemented #329

Open
danlessa opened this issue Nov 19, 2024 · 0 comments
Open

Block Validation mechanism & behavior is implemented #329

danlessa opened this issue Nov 19, 2024 · 0 comments

Comments

@danlessa
Copy link
Member

danlessa commented Nov 19, 2024

Note: this happens at Network Time rather than L1 Time

eg.

First, the proposer sends both their block proposal, and their block content through the network (not on L1)
Then, each validator ”simulates” the block, and signs the block header if it is valid (this is not proving, just "checking"), sending the signed header back to the proposer
Invalid Proposals:
Block is not provable - An invalid proposal can land on the pending chain, if the committee signs it, eg. due to:
Committee tries to "attack"
Committee is compromised
Committee runs buggy client software (might not be intentionally compromised by someone)
Definition of "Land on the pending chain" = Received enough signatures to be considered "valid" for now, even though it will not be proven later but instead reorged
Then, the Proposer sends the signed block header of the proposal to L1

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