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

Specify blobs by root condition if there's equivocating blobs #3530

Closed
wants to merge 1 commit into from

Conversation

terencechain
Copy link
Contributor

@terencechain terencechain commented Oct 27, 2023

h/t to @realbigsean for the comment

This PR introduces an explicit condition for handling blob responses by root in cases of blob equivocation. Ensures clients adhere to specified behavior for serving blobs with matching KZG commitments or the first valid blobs they encounter, depending on whether the block has been seen.

Notes:

  • I'm not convinced the second must is truly necessary. Open for feedback
  • An alternate solution is to add the kzg commitment to the RPC request
  • An alternate solution specify that clients MUST NOT serve blobs until the corresponding block has been fully validated. (This slows down the overall blob propagation speed)

@@ -292,6 +292,10 @@ Clients MUST support requesting sidecars since `minimum_request_epoch`, where `m
Clients MUST respond with at least one sidecar, if they have it.
Clients MAY limit the number of blocks and sidecars in the response.

In the event of equivocating blobs, clients MUST serve only blobs with matching KZG commitments if they have seen the block.
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not sure this is necessary if #3531 is merged. Because you now have an explicit tie between the blobs and the block header at the point of gossip acceptable

@ppopth
Copy link
Member

ppopth commented Oct 29, 2023

How is this different from #3532 ?

@terencechain
Copy link
Contributor Author

How is this different from #3532 ?

This is RPC behavior. 3532 is Gossip behavior. We most likely won't need both once blob sidecar has inclusion proof. These can be closed once inclusion proof is merged

@hwwhww hwwhww added scope:networking Deneb was called: eip-4844 labels Oct 31, 2023
@djrtwo
Copy link
Contributor

djrtwo commented Nov 2, 2023

closing in favor of #3531

@djrtwo djrtwo closed this Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Deneb was called: eip-4844 scope:networking
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants