Skip to content

feat(frontend): show live streamed amount with bounded polling and clock handling #133

Open
Open
feat(frontend): show live streamed amount with bounded polling and clock handling#133
Labels
GRANTFOX OSSOpen-source issue tracked by GrantFoxMAYBE REWARDEDThis issue may carry a rewardThird CampaignThird Campaign contributionenhancementNew feature or requestpriority:highHigh implementation priority

Description

@arisu6804
arisu6804
opened on Aug 21, 2026

Problem

A live balance display can be misleading when polling is unbounded, browser time is wrong, or the stream state has changed.

Objective

Deliver a production-quality improvement to stream detail, accrual display, and refresh behavior that creates measurable value for correctness, security, reliability, performance, or maintainability.

Implementation scope

  • Use server/chain timestamps and bounded polling; show last-updated and pending states; stop polling when terminal or hidden.

Acceptance criteria

  • Displayed accrual never exceeds the authoritative cap; polling is bounded; clock drift and stale status are visible.

Required validation

  • Fake-clock, polling-limit, tab-visibility, terminal-state, and reconciliation tests.
  • Existing tests and CI remain passing.
  • Add regression coverage for the original failure mode.
  • Do not weaken, delete, or skip unrelated tests to obtain a green build.

PR quality bar

  • Keep the PR focused and explain design tradeoffs, compatibility impact, and test evidence.
  • Avoid typo-only, documentation-only, cosmetic-only, or unrelated refactor submissions.

Out of scope

  • Broad rewrites not required by the acceptance criteria.
  • Changes to unrelated services, contracts, or user flows.

Activity

  1. arisu6804
    added
    enhancementNew feature or request
    GRANTFOX OSSOpen-source issue tracked by GrantFox
    MAYBE REWARDEDThis issue may carry a reward
    priority:highHigh implementation priority
    Third CampaignThird Campaign contribution
    on Aug 21, 2026

  2. guptakumarranjeet150 commented on Sep 9, 2026

    @guptakumarranjeet150
    guptakumarranjeet150
    on Sep 9, 2026

    Hey team,

    I would love to take this on. My planned approach:

    • Build feat(frontend): show live streamed amount with bounded polling and clock handling with clean React/Next.js components, responsive styling, and proper loading/error boundaries.
    • Add component unit tests and ensure zero TypeScript/ESLint warnings.

    I am ready to start immediately—please assign this to me!

  3. ranjeet150 commented on Sep 13, 2026

    @ranjeet150
    ranjeet150
    on Sep 13, 2026

    Hello! I'd like to work on this issue.

    I would like to resolve this issue. Here is my proposed execution plan:

    • Implementation: Build feat(frontend): show live streamed amount with bounded polling and clock handling with clean React/Next.js components, responsive styling, and proper loading/error boundaries.
    • Testing & Verification: Add component unit tests and ensure zero TypeScript/ESLint warnings.
    • Delivery: Ready to ship a thoroughly tested PR within 12–24 hours with passing CI.

    Excited to work on this—please assign to me and I'll submit a clean PR shortly!

  4. Rodrigoue9 commented on Oct 7, 2026

    @Rodrigoue9
    Rodrigoue9
    on Oct 7, 2026

    Hi @maintainers! I'd like to work on this issue. Here is my proposed technical approach:

    Proposed Technical Approach:

    1. Stream Lifecycle & Idempotency: Implement idempotent creation/withdrawal guards and clock drift mitigation for live stream calculations.
    2. UI & Precision Handling: Ensure bounded polling and zero precision loss during balance rendering.
    3. Unit Tests: Implement comprehensive test suites simulating disconnects and concurrent withdrawals.

    Key Files:

    • src/** (streaming service and hooks)
    • tests/**

    Verification & Testing:

    • Run test suite ensuring all specs pass.

    Relevant Track Record:

    I have successfully implemented and merged multiple production PRs across the Stellar ecosystem and Web3 open-source projects (e.g., cybermax4200/stellar-did-credit #898 & #900, Bitcoindefi/OpenAO #218, and FindMalek/sonaraem #416).

    Please feel free to assign this issue to me so I can proceed with the implementation. Thank you!

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    GRANTFOX OSSOpen-source issue tracked by GrantFoxMAYBE REWARDEDThis issue may carry a rewardThird CampaignThird Campaign contributionenhancementNew feature or requestpriority:highHigh implementation priority

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions