Skip to content

feat: Add CLI extensions so users can run custom inspectors & classifiers without forking. #503

@Will-Smith11

Description

@Will-Smith11

Description:

Currently, if someone wants to write custom inspectors for Brontes, they would need to fork the project and add their code directly. This approach isn't maintainable in the long term due to potential merge conflicts and the need to modify the database schema for storing newly classified data.

To improve the extensibility of Brontes, we want to add support for custom inspectors that can be defined and installed by users without requiring them to fork the project. This will enable users to create and use their own inspectors while keeping their codebase separate from the main Brontes repository.

Requirements

  • Implement a mechanism for users to define custom inspectors in their own repositories by implementing the existing Inspector trait.
  • Provide a way to install and load custom inspectors dynamically in Brontes.
  • Ensure that custom inspectors can be run alongside the built-in inspectors.
  • Modify the inspector initialization and execution logic to incorporate custom inspectors.
  • Maintain backward compatibility with the existing inspector system.

Additional Context|

See reth's CLI extension reth cli ext

LibEVM reth cli extension guide

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-enhancementNew feature or requestD-2Difficulty 2/5 (easy)P-2Priority 2/3 (average criticality)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions