main has no branch protection; broken code can merge

[Jaydbrown]

PR #373 merged a non-compiling contracts/stream/src/storage.rs (mangled attributes, use soroban_sdk:{;, a typo'd FLAG_ClAWBACK_ENABLED). main should require the Build WASM, Lint and Test checks to pass before merge, and disallow force-push. Right now a red PR can be merged with admin override and nobody notices until the next PR's CI fails.

[achebejohnpaul]

Am a full-Stack Engineer focused on frontend, backend, APIs, automation, and modern web technologies. Passionate about solving real-world problems, contributing to open source, and delivering clean, scalable, review-ready solutions.

[Ranjeet2063]

Hi maintainers, I would love to be assigned to this issue.

I am an active core contributor in the Stellar/Soroban ecosystem (#1 contributor on Mova Store with 28 successfully merged PRs), with deep expertise across Soroban SDK smart contracts, cryptographic access controls, and production test suites.

🎯 Technical Execution Plan for main has no branch protection; broken code can merge:

1. Module & Storage Analysis: Pinpoint the exact contract modules in conduit-protocol/streamFi-contracts handling this logic. Define explicit storage DataKeys, TTL policies, and auth boundaries (require_auth()).
2. Canonical Soroban Implementation: Implement the required state changes, validations, and structured event emissions (env.events().publish(...)) adhering strictly to official Soroban best practices and zero arithmetic overflow/underflow.
3. Exhaustive Unit Test Suite: Build comprehensive tests covering:
   • Happy-path state transitions and expected outputs.
   • Boundary limits, edge cases, and zero/saturating values.
   • Negative tests asserting unauthorized callers (mock_auths(&[])) and invalid parameter reverts with exact ContractError variants.
4. CI & Verification Gate: Verify 100% clean cargo check, zero clippy warnings, and full test suite passing locally before opening the PR.

💡 Why Assigning Me Directly Benefits You:

• Zero Maintainer Overhead: Self-documenting code with exhaustive tests so you don't spend valuable time babysitting, debugging, or fixing CI.
• Fast Issue Closure: Production-grade PR delivered in 12–24h, cleanly clearing this issue off your backlog.
• Proven Reliability: 28 merged PRs as #1 contributor on Mova Store — guaranteed senior-level execution from day one.

[Fading-Dev]

Hi! I'd like to work on this issue.

I'm a software engineer with hands-on experience in testing, debugging, and building reliable features across the stack. I'm confident I can take this on and deliver a solid, well-tested solution that follows the project's existing conventions.

I'll make sure to cover the core functionality as well as relevant edge cases to keep things reliable and regression-resistant.

Let me know if I can get started, and I'll provide updates as I progress.

[AvatarMiiDe]

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

I would like to take this off your list, kindly assign and i would work on it immediately

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

[pepkodex56]

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

Hello Maintainer, I’ve gone through the issue carefully and understand the expected result. I’m confident I can provide a solution that meets the requirements. I’d appreciate an assignment.

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

[stephaniepez21-art]

@stephaniepez21-art has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hi maintainer, I'd like to work on this. pls assign

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

[iyanujohn612]

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

Hello, may I work on this issue?

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

[drips-wave]

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

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

[drips-wave]

This issue has been completed by @iyanujohn612 as part of the Stellar Wave Program's 9th Wave 🥳

😎 @iyanujohn612: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.