Skip to content

Base repository TimelockController does not expose operations, relying on centralized indexer #213

@aviggiano

Description

@aviggiano

The TimelockController contract from the base repository currently does not provide any view methods for inspecting scheduled operations.

This means that all visibility into pending or scheduled operations must come from an external indexer, introducing a centralization point for interfaces that want to minimize off-chain dependencies.

It would be useful if the contract exposed simple view functions (e.g., returning currently scheduled operations or details about a given operation) so that clients and dapps can directly query the contract without depending on an indexer.

While this functionality can be added by extending TimelockController, having it available by default in a vetted contract would improve transparency and usability.

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