Build Plugin System for Custom Inspector Modules

[Timi16]

Description

Design and implement a plugin architecture allowing the community to write custom inspector plugins as shared libraries and load them into the debugger at runtime — making the debugger infinitely extensible.

Requirements

• Define a stable InspectorPlugin trait as the plugin API
• Load plugins dynamically from ~/.soroban-debug/plugins/ at startup
• Plugins can hook into execution events, add new CLI subcommands, and add output formatters
• Plugin manifest file (plugin.toml) with name, version, and author metadata
• Document the plugin API with a worked example plugin

Suggested Execution

1. Branch: git checkout -b feature/plugin-system
2. Define InspectorPlugin trait in src/plugin/api.rs
3. Implement dynamic loading using libloading
4. Create plugin registry in src/plugin/registry.rs
5. Load plugins from disk at startup
6. Write an example plugin in examples/plugins/
7. Write plugin authoring documentation
8. Commit: feat: implement plugin system for custom inspector modules

Acceptance Criteria

• InspectorPlugin trait defined and stable
• Plugins load from ~/.soroban-debug/plugins/ at startup
• Example plugin builds and loads correctly
• Plugins can hook into execution lifecycle events
• Plugin API fully documented with examples

Difficulty: Advanced — requires dynamic library loading knowledge

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Hallab7]

@Hallab7 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

i would love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Hallab7 to this issue.

[OlamideAfunsho]

@OlamideAfunsho has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I would like to work on the issue to increase my level of experience

ℹ️ Repo Maintainers: To accept this application, review their application or assign @OlamideAfunsho to this issue.

[drips-wave]

Congratulations, @OlamideAfunsho! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @OlamideAfunsho: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are issued when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊