Skip to content

glados-monitor for history does not handle reorgs #430

@Ktl-XV

Description

@Ktl-XV

Currently, whenever a block with a higher block number than the previously fetched is available, glados-monitor gets it and stores it in the DB. This means that it is likely that the glados DB currently contains blocks that where reorged and might miss-report audits since the verification would fail.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions