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
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
Inspectortrait.Additional Context|
See reth's CLI extension reth cli ext
LibEVM reth cli extension guide