Add gas benchmarks for orchestrator cross-contract execution

[Baskarayelu]

Description

Create gas benchmarks for orchestrator execute paths to monitor cross-contract overhead and regressions.

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review
• Track per-step gas cost with baseline thresholds

Suggested execution

• Fork the repo and create a branch
• git checkout -b test/orchestrator-cross-contract-gas
• Implement changes
• Write contract: orchestrator/src/lib.rs
• Write comprehensive tests: orchestrator/src/test.rs
• Add documentation: benchmarks/README.md
• Include NatSpec-style comments
• Validate security assumptions

Test and commit

• Run tests: cargo test -p orchestrator -- --nocapture
• Cover edge cases
• Include test output and security notes

Example commit message

test: add gas benchmarks for orchestrator execute paths

Guidelines

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 96 hours

[Muhammadcodes112]

@Muhammadcodes112 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi, I’d like to work on this issue. I can add gas benchmarks for the orchestrator execute flows, track per-step cross-contract gas costs with clear baseline thresholds, add thorough tests and edge-case coverage, and document the benchmark approach, results, and security assumptions for an easy review.

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

[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

[drips-wave]

Congratulations, @Muhammadcodes112! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @Muhammadcodes112: 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 awarded 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 🌊