Skip to content

Implement recipient insurance pool governance #888

Closed

Description

@Kingsman-99

Overview

Implement recipient insurance pool governance

Requirements

  • Implement core functionality
  • Add proper events and logging
  • Write comprehensive tests

Acceptance Criteria

  • Feature implemented
  • All tests pass
  • cargo test --workspace passes
  • cargo clippy produces zero warnings

Definition of Done

All CI checks must pass before the PR is reviewed.

Activity

  1. added
    complexity: highComplex feature requiring deep knowledge - 200 pts
    featureNew contract feature or operation
    on Sep 27, 2026
  2. guptakumarranjeet150 commented on Sep 30, 2026

    @guptakumarranjeet150

    Hello @maintainers,

    I am interested in working on this issue.
    Plan:

    1. Structure Soroban contract handlers for Implement recipient insurance pool governance following project idioms and storage invariants.
    2. Cover contract calls with hermetic unit tests verifying events and token balances.

    I can start working on this right away. Please assign!

  3. soma-enyi commented on Oct 17, 2026

    @soma-enyi
    Contributor

    @soma-enyi has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi team, I'd like to work on this issue. I'm a full-stack developer experienced in TypeScript, Rust, and smart contract development across EVM and Soroban/Stellar ecosystems. I've built and shipped production systems covering backend APIs, frontend interfaces (Next.js, React), CI/CD pipelines, and onchain protocols — so I'm comfortable working across whatever layer this issue touches. My approach I'll start by reproducing the issue locally and reading the surrounding code to understand context and constraints. I'll scope the fix tightly to avoid unnecessary churn, write or update tests to cover the change, and make sure linting, formatting, and existing CI checks all pass before opening a PR. If anything in the issue is ambiguous, I'll flag it early rather than guess. What you can expect A single clean PR with a clear description linking back to this issue. Minimal, well-tested changes that follow the project's existing conventions. Fast turnaround — I'm available to start immediately and responsive to review feedback. Happy to discuss the approach further if needed. Looking forward to contributing.

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

  4. drips-wave commented on Oct 17, 2026

    @drips-wave

    Congratulations, @soma-enyi! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

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

  5. grantfox-oss commented on Oct 19, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @soma-enyi's PR #982 was approved and merged by @Kingsman-99.

    🏆 @soma-enyi: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,188 total points). Track your full progress on GrantFox.

    👏 Great work, @soma-enyi! Keep contributing to Stellar-split.

  6. drips-wave commented on Oct 19, 2026

    @drips-wave

    This issue has been completed by @soma-enyi as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @soma-enyi: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programcomplexity: highComplex feature requiring deep knowledge - 200 ptsfeatureNew contract feature or operation

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions