Skip to content

Conversation

@dapplion
Copy link
Member

It's possible that a DataColumnSidecars arrives before the beacon block it's referencing. We don't yet how builders / users will use Gloas and publish things. To prevent instability, the spec should suggest to cache DataColumnSidecars the same way we cache attestations and aggregates for unknown beacon blocks.


- _[IGNORE]_ The sidecar's `beacon_block_root` has been seen via a valid signed
execution payload header (builder's bid).
execution payload header (builder's bid). A client MAY queue the sidecar for
Copy link
Contributor

Choose a reason for hiding this comment

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

Any specific reason to use the word "queue" then just cache?

Copy link
Member Author

Choose a reason for hiding this comment

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

Same language as in previous forks

Copy link
Member

Choose a reason for hiding this comment

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants