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

Add validation description for LightClientBootstrap + Update #306

Merged
merged 1 commit into from
Jun 3, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions beacon-chain/beacon-network.md
Original file line number Diff line number Diff line change
Expand Up @@ -250,4 +250,20 @@ random gossip.

#### Validation

##### LightClientBootstrap

While still light client syncing a node SHOULD only allow to store an offered `LightClientBootstrap` that it knows to be canonical.
That is, a bootstrap which it can verify as it maps to a known trusted-block-root.
E.g. trusted-block-root(s) provided through client config or pre-loaded in the client.

Once a node is light client synced, it can verify a new `LightClientBootstrap` and then store and re-gossip it on successful verification.

##### LightClientUpdate

While still light client syncing a node SHOULD NOT store any offered `LightClientUpdate`. It SHOULD retrieve the updates required to sync and store those when verified.

Once a node is light client synced, it can verify a new `LightClientUpdate` and then store and re-gossip it on successful verification.

##### LightClientFinalityUpdate & LightClientOptimisticUpdate

Validating `LightClientFinalityUpdate` and `LightClientOptimisticUpdate` follows the gossip domain(gossipsub) [consensus specs](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/light-client/p2p-interface.md#the-gossip-domain-gossipsub).
Loading