Skip to content

Add Co-Surety/Reinsurance Participation Tracking for Large Bonds #1002

Closed

Description

@vjuliaife

Description:
get_account and get_collateral_history model a single surety per account, but large bonds are often syndicated across multiple co-sureties. Add tracking of participation percentages across multiple surety parties for a single importer bond.

Acceptance Criteria:

  • Data model supports multiple co-surety participants with percentage splits
  • New endpoint to record and view co-surety participation for a bond
  • Percentages must sum to 100% and are validated on save
  • Compliance dashboard reports exposure per co-surety participant
  • Existing single-surety bonds continue to work unchanged

Relevant Files:

  • contracts/tariff-shield/src/lib.rs — get_account/get_surety functions this extends conceptually off-chain
  • apps/api/src/routes/compliance.ts — dashboard that would report co-surety exposure

Activity

  1. added
    apiAuto-created by repotool publish-folder
    contractAuto-created by repotool publish-folder
    featureAuto-created by repotool publish-folder
    on Aug 22, 2026
  2. Jefeistop commented on Sep 24, 2026

    @Jefeistop

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

    Hi maintainer I would like to work on this issue please assign

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

  3. prissca commented on Sep 24, 2026

    @prissca
    Contributor

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

    i will love to work on this issue

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

  4. 3m1n3nc3 commented on Sep 24, 2026

    @3m1n3nc3

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

    Hi, I would love to work on and resolve this issues, I am a fullstack and web3 egineer with multiple years of exprience working on solutions for similar problems. ETA is 5hrs.

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

  5. drips-wave commented on Sep 24, 2026

    @drips-wave

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

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

  6. drips-wave commented on Sep 28, 2026

    @drips-wave

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

    😎 @prissca: 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.

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 programapiAuto-created by repotool publish-foldercontractAuto-created by repotool publish-folderfeatureAuto-created by repotool publish-folder

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions