frontend: Implement Multi-Beneficiary Form Controls & Allocation Validation in Plan Creation & Editing

[ONEONUORA]

Problem Description

In frontend/components/plans/CreateInheritancePlanPanel.tsx and EditInheritancePlanPanel.tsx, the UI allows users to add multiple beneficiaries, set their allocation percentages, wallet addresses, and off-ramp anchor options. However, when submitting the form to plansAPI.createPlan, only the first beneficiary's name (beneficiaries[0]?.name) is transmitted, while all other beneficiaries, basis point allocations (allocation_bps), wallet addresses, and fiat anchor configs are discarded.

Missing Functionality & Specs

• Update CreateInheritancePlanPanel.tsx and EditInheritancePlanPanel.tsx to map the full list of beneficiaries into PlanBeneficiaryRequest[].
• Enforce strict allocation validation in basis points (100% = 10,000 bps) before form submission.
• Pass beneficiary wallet addresses, fiat anchor IDs, and daily fiat limits to both backend API requests and on-chain contract parameters.
• Provide clear error messaging if allocations do not equal 10,000 bps or if wallet addresses fail Stellar public key validation.

Affected Files

• frontend/components/plans/CreateInheritancePlanPanel.tsx
• frontend/components/plans/EditInheritancePlanPanel.tsx
• frontend/app/lib/api/plans.ts
• frontend/app/lib/api/inheritance.ts

[Just-Bamford]

I’d tackle this by updating both create and edit flows to transform the complete beneficiary list into PlanBeneficiaryRequest[], including allocation BPS, wallet addresses, fiat anchor IDs, and daily limits. Before submission, I’d validate that allocations total exactly 10,000 BPS and that every provided wallet address is a valid Stellar public key, returning clear errors before any API or contract call is made.

I’d then update the plans and inheritance API layers to preserve these fields through to the backend and on-chain parameters, ensuring create and edit behave consistently. Finally, I’d add tests covering multiple beneficiaries, allocation failures, invalid wallet addresses, and correct propagation of anchor configuration.

[anonfedora]

I'm interested in this

[grantfox-oss]

🦊 GrantFox — @anonfedora has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #1031)
2. Your PR will be reviewed by the Fracverse maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@anonfedora's PR #1053 was approved and merged by @ONEONUORA.

🏆 @anonfedora: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (707 total points). Track your full progress on GrantFox.

👏 Great work, @anonfedora! Keep contributing to Fracverse.