Skip to content

perf(backend): add stable cursor pagination for transfers and audit history #132

Description

@arisu6804

Problem

Offset pagination becomes expensive and unstable as transfers arrive while a user is paging through history.

Objective

Deliver a production-quality improvement to transfer and audit history APIs that creates measurable value for correctness, security, reliability, performance, or maintainability.

Implementation scope

  • Use indexed cursor pagination with deterministic tie-breakers, maximum page sizes, and filter-bound cursors.

Acceptance criteria

  • Pages have no duplicates or gaps under inserts; cursors cannot cross actor scope; oversized queries are bounded.

Required validation

  • Pagination contract, concurrent-insert, scope, filter, and large-fixture performance 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

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

Metadata

Metadata

Assignees

Labels

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions