#1051 Add vault insurance fund mechanism

[vic-Gray]

Area: backend · Effort: L

What: Implement an optional insurance fund that vault operators can fund to cover depositor losses in the event of a smart contract exploit or strategy failure.

Why: Insurance funds are a powerful trust signal that separates professional vault operators from anonymous ones. They directly address the biggest user concern: 'what if I lose my funds?'

Acceptance Criteria:

• Vault operators can fund an insurance pool in a dedicated Stellar escrow account
• Insurance coverage ratio (fund / TVL) is displayed prominently on the vault page
• In the event of a declared incident, admins can trigger a pro-rata payout to depositors
• Insurance fund contributions and payouts are publicly auditable on-chain

Hints:

• backend/src/vaults/insurance-fund.service.ts
• Use a Soroban multisig account for the insurance escrow
• Model payouts as a separate insurance_claim entity

[aojomo]

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

I’d like to work on this because it adds an important safety mechanism to the protocol, and I’m interested in DeFi vault and risk-management features. I’m comfortable working through backend logic, understanding existing codebases, and implementing features carefully to fit the project’s architecture.

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

[mrmoney10010-design]

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

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

I plan to implement an insurance fund system with a dedicated escrow account, track and expose coverage ratios relative to TVL, support auditable funding and payout flows, and add an incident-triggered pro-rata claims process for depositors. I'll also ensure the feature is fully tested and documented.

Could this issue be assigned to me?

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

[drips-wave]

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

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