Skip to content

Add key split event notification and updated balance display #1151

Closed

Description

@Chucks1093

Summary

Display a notification banner on the key detail and portfolio pages when a key split has been executed, informing holders of their adjusted balance and the split ratio applied.

Scope

  • Split notification banner on KeyDetail for 48h after SplitExecuted event
  • Banner shows: split ratio, pre-split balance, post-split balance
  • Portfolio page highlights split keys with a 'Split Applied' badge for 48h
  • Updated balances fetched and displayed immediately after split event
  • Dismiss button on banner clears it for the session

Acceptance Criteria

  • Banner appears correctly for 48h after split execution
  • Banner displays correct ratio, pre-split, and post-split balances
  • Portfolio badge appears on split keys for correct duration
  • Updated balances reflect accurate post-split amounts
  • Dismiss correctly clears banner for session

ETA

12 hours

Activity

  1. ranjeetprabhatedu-dotcom commented on Oct 18, 2026

    @ranjeetprabhatedu-dotcom

    Hello maintainers,

    I reviewed "Add key split event notification and updated balance display" and would like to work on this.

    I have reviewed the problem description and acceptance criteria for this issue. I have a clear, tested implementation ready with defensive error handling and 100% green CI proof.

    I will deliver a clean, well-tested, and production-ready PR promptly upon assignment. Kindly assign this issue to me.

    Thank you!

  2. moon-code12 commented on Oct 18, 2026

    @moon-code12

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

    Hello Maintainers, I would like to express my interest in working on this issue. I have reviewed the issue description and understand the problem that needs to be addressed. My approach will be to investigate the existing codebase, identify the root cause, and implement a solution that follows the project's existing architecture and coding standards.

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

  3. VeronicDev commented on Oct 18, 2026

    @VeronicDev

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

    Hello Maintainer, I can fix this please assign.

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

  4. Muyideen-js commented on Oct 18, 2026

    @Muyideen-js

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

    Hi, I can fix this

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

  5. innocentharuna commented on Oct 18, 2026

    @innocentharuna

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

    hey maintainer, please kindly assign this to me, i can surely fix it

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

  6. Xcel-i commented on Oct 18, 2026

    @Xcel-i

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

    I understand the issue beyond the reported symptoms, including the expected behaviour and the changes needed to achieve it. I’ve considered how the fix should integrate with the existing implementation and am prepared to handle the code changes and testing. I’d like to work on this issue.

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

  7. whitezaddy commented on Oct 18, 2026

    @whitezaddy
    Contributor

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

    I have experience and have reviewed the code; I can submit a PR within 2 days.

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

  8. drips-wave commented on Oct 18, 2026

    @drips-wave

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

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

  9. grantfox-oss commented on Oct 22, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @whitezaddy's PR #1267 was approved and merged by @Chucks1093.

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

    👏 Great work, @whitezaddy! Keep contributing to accesslayerorg.

  10. drips-wave commented on Oct 22, 2026

    @drips-wave

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

    😎 @whitezaddy: You earned 150 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 program

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions