Draft
Conversation
WIP: full ePBS implementation
fix: update based on latest gloas spec
…e instead of dependent block state)
# Conflicts: # indexer/beacon/block.go # services/chainservice_blocks.go
…cess This change modifies how blocks are processed in the beacon client. It checks the chain state for EIP-7737 enablement based on the block slot's epoch to determine whether to load the execution payload when processing a block from the stream. Additionally, it updates `GetSlotDetailsByBlockroot` and `GetSlotDetailsBySlot` to include the payload in the response if it exists, further integrating payload handling into block detail retrieval.
…2 check in processStreamBlock Removes the logic to determine if EIP-7732 payload loading is needed when processing a block from the head event stream because blocks received via head events are assumed to not require immediate execution payload processing for caching purposes initially. Updates `processExecutionPayloadAvailableEvent` to use `createOrGetBlock` when a block is not found in the cache during an execution payload availability event, ensuring the block object exists before proceeding.
…nto a single stream dispatcher Remove separate `blockDispatcher` and `headDispatcher` in `consensus.Client`. Introduce a unified `streamDispatcher` of type `utils.Dispatcher[*rpc.BeaconStreamEvent]` to handle both block and head events. Update `Client` methods (`SubscribeBlockEvent`, `SubscribeHeadEvent`) to remove them and introduce `SubscribeStreamEvent`. Update `runClientLogic` to fire block and head events through the new `streamDispatcher` to guarantee SSE ordering preservation on the consumer side. Update `indexer/beacon/Client` to use the new `streamSubscription` instead of separate block and head subscriptions, simplifying event handling in `runClientLoop` by processing a unified stream event type that maintains ordering. This change simplifies the event handling mechanism in the consensus client, ensuring that block and head events originating from the RPC stream are processed in the correct order as delivered by the RPC endpoint.
fix: execution requests gloas
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docker image:
ethpandaops/dora:gloas-supportspecs version:
v1.7.0-alpha.2specs path: specs/gloas
based on #227