Protect against frontrunning and sandwich attacks on subscription charges

[Smartdevs17]

Description

Subscription charges are visible in mempool and vulnerable to MEV. Implement protection mechanisms.

Acceptance Criteria

• Commit-reveal scheme for large charges
• Slippage protection with max fee bounds
• Private mempool integration option
• MEV extraction monitoring
• Gas price analysis for attack detection
• Documentation of MEV threat model

Technical Scope

• contracts/subscription/src/lib.rs
• Edge: commit-reveal UX impact, private mempool censorship, gas bidding analysis

[Wisdom2788]

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

Hey,

I’m a full stack Software Engineer with experience across frontend, backend, and some blockchain related work. I’m genuinely interested in contributing to real problems like this.

My main stack is React, TypeScript, and Next.js on the frontend, where I focus on clean component structure, responsiveness, and performance. On the backend, I work with Node.js, Java, and Python, building APIs, handling application logic, and working with data in a structured and secure way.

A few things I’ve built:
Portfolio:
https://my-portfolio-two-nu-80q0sjswsj.vercel.app/

I’m comfortable jumping into existing codebases, understanding patterns, and following established conventions. I care about writing code that is clear, maintainable, and easy to review.

Happy to take this on if it’s a good fit. Thanks for your time.

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

[Abdul-dev-creator]

@Abdul-dev-creator has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Gm maintainer i will love to work on this am capable

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Abdul-dev-creator to this issue.

[drips-wave]

Congratulations, @Chidubemkingsley! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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

[wagmiiii]

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

Hi, i would like to work on this issue

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

[drips-wave]

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

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

[wagmiiii]

@Smartdevs17 please kindly check, my pr issue #640 is not reflecting on drips waves as submitted, instead it shows #525 which is still open.