Add performance benchmarking suite and regressions

[Just-Bamford]

Problem

No performance baselines exist. SDK modifications may introduce regressions (slower parsing, allocations). No automated detection of performance degradation.

Solution

Create benchmark suite using vitest's bench API. Measure: XDR parsing, fee calculation, account fetch overhead, contract simulation. Set baseline thresholds. Flag regressions in CI.

Acceptance Criteria

• Benchmark suite created in \src/tests/benchmarks/\
• Benchmarks cover: XDR parsing, fee calc, account fetch, contract sim
• Baselines documented in README
• CI flags regressions (>10% slower)
• Results published in PR comments
• Benchmarks pass on Node 18 and 20

Note for contributors

Use vitest bench or hyperfine. Run on consistent hardware. Document baseline and acceptable regression threshold.

[BigElv]

@BigElv has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer I would love to work on this issue please

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

[Johnpii1]

@Johnpii1 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Sir,

I came across your project and I’m really interested in contributing.

I have experience with React for building responsive, user-friendly interfaces, and I’m also familiar with smart contracts and blockchain basics. I focus on writing clean, scalable code and improving user experience.

I’m a fast learner and ready to get started immediately. Please let me know the next steps.

Thank you.

Best regards,
Johnpaul

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

[OmniZlatoon]

@OmniZlatoon has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Maintainer, I am no pro, but I got the skills to take on this issue
I would really love to work on this issue.

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

[0xElyte]

@0xElyte has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I'd love to resolve this fast

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

[AJ0070]

@AJ0070 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Please assign me this issue, I would like to work on this.

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

[GauravKarakoti]

@GauravKarakoti has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Allow me to work on this one

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

[drips-wave]

Congratulations, @h53566186-web! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @h53566186-web: 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 🌊