INDEXER- Get a range of BlockEvents
/events/blocks
allows the caller to query a sequence of BlockEvents indicating which blocks were added and removed from storage to reach the current state. Following BlockEvents allows lightweight clients to update their state without needing to implement their own syncing logic (like finding the common parent in a reorg). /events/blocks
is considered an “indexer” endpoint and Rosetta implementations are not required to complete it to adhere to the Rosetta spec. However, any Rosetta “indexer” MUST support this endpoint.
Body
EventsBlocksRequest is utilized to fetch a sequence of BlockEvents indicating which blocks were added and removed from storage to reach the current state.
Response
Expected response to a valid request
EventsBlocksResponse contains an ordered collection of BlockEvents and the max retrievable sequence.