Skip to content

Latest Events: On Reorg Update Only the Reorged Logs in the Resulting Vector #198

@0xNeshi

Description

@0xNeshi

Currently on reorgs the whole vector is disregarded, and the mode is restarted. This is ok for smaller number of latest events, but in case of a large number (e.g. in the thousands), and especially in a wide block range (e.g. months/years), this will be a huge performance bottleneck.

The obvious optimization is to only re-process the reorged block numbers, removing the reorged logs from the resulting vector and prepending the re-fetched logs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: refactorCode improvement without changing functionality

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions