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

Engine API: add getPayloadBodiesByRangeV1 to #146 #218

Closed
wants to merge 12 commits into from

Commits on Dec 10, 2021

  1. Configuration menu
    Copy the full SHA
    b1a4ebd View commit details
    Browse the repository at this point in the history
  2. Engine API: fix spellchecker

    mkalinin committed Dec 10, 2021
    Configuration menu
    Copy the full SHA
    6be1088 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    f500c48 View commit details
    Browse the repository at this point in the history

Commits on Feb 2, 2022

  1. Configuration menu
    Copy the full SHA
    b490341 View commit details
    Browse the repository at this point in the history

Commits on May 6, 2022

  1. Configuration menu
    Copy the full SHA
    f9ee0ff View commit details
    Browse the repository at this point in the history
  2. add by-range request

    Similar to the consensus p2p spec, a by-range request allows execution
    clients to store finalized blocks in linear by-number storage instead of
    relying on by-hash indices, significantly increasing efficiency in
    fetching them from cold storage.
    
    Clients whose database design does not permit efficient by-number
    lookups may opt to not implement this call, but must then give a
    well-known error code allowing consensus later clients to fall back to a
    less efficient method of fetching the blocks.
    
    This specification assumes that execution clients know nothing of slot
    numbers as seen on the consensus layer. Should execution clients later
    learn about these, the specification may be amended to work with slot
    numbers instead.
    
    Until then, consensus clients must be careful to compute block numbers
    correctly.
    
    Consensus clients must also be careful when this request is used to
    fetch non-finalized blocks, reverting to by-root requests if an
    unexpected chain is returned.
    arnetheduck committed May 6, 2022
    Configuration menu
    Copy the full SHA
    832c938 View commit details
    Browse the repository at this point in the history
  3. fight spellchecker

    arnetheduck committed May 6, 2022
    Configuration menu
    Copy the full SHA
    1091c2d View commit details
    Browse the repository at this point in the history

Commits on May 10, 2022

  1. Update src/engine/specification.md

    Co-authored-by: Mikhail Kalinin <[email protected]>
    arnetheduck and mkalinin authored May 10, 2022
    Configuration menu
    Copy the full SHA
    e189c5b View commit details
    Browse the repository at this point in the history
  2. Update src/engine/specification.md

    Co-authored-by: Mikhail Kalinin <[email protected]>
    arnetheduck and mkalinin authored May 10, 2022
    Configuration menu
    Copy the full SHA
    e19aa80 View commit details
    Browse the repository at this point in the history

Commits on May 31, 2022

  1. Configuration menu
    Copy the full SHA
    19c2e8a View commit details
    Browse the repository at this point in the history
  2. ByRoot -> ByHash

    arnetheduck committed May 31, 2022
    Configuration menu
    Copy the full SHA
    e1989ed View commit details
    Browse the repository at this point in the history

Commits on Sep 29, 2022

  1. Allow nil in response

    arnetheduck committed Sep 29, 2022
    Configuration menu
    Copy the full SHA
    de8fd3d View commit details
    Browse the repository at this point in the history