Add a protocol revenue distribution history page for stakers showing past distributions and their share

[Chucks1093]

Summary

Stakers who received protocol revenue distributions have no record of what they earned. A distribution history page on the portfolio staking tab should list all past protocol revenue distributions with the amount received per event.

Scope

• Add a Protocol Revenue tab within the Staking section on the portfolio page
• Fetch distribution records from GET /staker/:wallet/protocol-revenue with cursor pagination
• Display distributionDate, totalDistributed, stakerCount, and amountReceived per row
• Sort by distributionDate descending
• Show 'No protocol revenue distributions yet' empty state when the list is empty

Acceptance Criteria

• All required columns displayed correctly
• Rows sorted by distributionDate descending
• Cursor pagination loads next page correctly
• amountReceived shows the correct per-staker amount
• Empty state shown when no distributions exist

ETA: 12 hours

---

Coordinate on Telegram

[oyinade247]

Can I work on this pleaseeeeeeee

[ZacLou]

I'd like to work on this issue. I have relevant experience with this tech stack and can deliver a clean, well-tested PR. I can submit within 1-2 days.

[Webghost01-NG]

I’m a Web3 full-stack developer experienced with React, TypeScript, and API integrations. I’m confident I can deliver this feature cleanly, including the revenue history, pagination, and required UI states.

[ZacLou]

I'd like to work on this. Happy to implement the UI/frontend pieces described and follow the existing codebase patterns.

[Ranjeet2063]

Hi maintainers, I would like to work on this issue.

I am an experienced Web3 frontend engineer (#1 contributor on Mova Store with 28 merged PRs) with deep expertise in React, TypeScript, and staking reward dashboards.

Implementation Plan:

1. Add a dedicated "Protocol Revenue" tab within the Portfolio Staking view.
2. Integrate distribution event history APIs to display timestamp, total distributed revenue, and the staker's proportional share.
3. Provide exportable transaction table with pagination, filtering by date/asset, and loading skeletons.
4. Add comprehensive unit and component tests verifying empty states, calculations, and responsive rendering.
5. Ready to submit a clean PR within 12–24 hours.

[Ranjeet2063]

Hi maintainers, I would like to work on this issue.

I am an experienced Web3 frontend engineer (#1 contributor on Mova Store with 28 merged PRs) with deep expertise in React, TypeScript, and staking reward dashboards.

Implementation Plan:

1. Add a dedicated "Protocol Revenue" tab within the Portfolio Staking view.
2. Integrate distribution event history APIs to display timestamp, total distributed revenue, and the staker's proportional share.
3. Provide exportable transaction table with pagination, filtering by date/asset, and loading skeletons.
4. Add comprehensive unit and component tests verifying empty states, calculations, and responsive rendering.
5. Ready to submit a clean PR within 12–24 hours.

[Ranjeet2063]

Hi maintainers, I would love to take up this issue.

I am a senior Web3 frontend engineer (#1 contributor on Mova Store with 28 successfully merged PRs), specializing in Next.js, React, TypeScript, Tailwind CSS, and Freighter/Stellar wallet integrations.

🎯 Technical Execution Plan for Add a protocol revenue distribution history page for stakers showing past distributions and their share:

1. Component Design & UI State: Implement Add a protocol revenue distribution history page for stakers showing past distributions and their share with clean component decoupling, responsive layouts, accessible forms/modals, and robust loading/skeleton/error boundaries.
2. Web3 & Client Logic: Wire real-time state streams, optimistic UI updates, and seamless Freighter wallet transaction signatures with user-friendly error alerts for rejections/timeouts.
3. Comprehensive Test Suite: Add component and unit tests (Vitest / Jest + React Testing Library) verifying state changes, input sanitization, and edge-case rendering.
4. Production Verification: Confirm zero TypeScript errors (noImplicitAny), zero ESLint/Prettier warnings, and clean production build (pnpm build).

💡 Why Assigning Me Directly Benefits You:

• Zero Maintenance Burden: Pixel-perfect UI with strict typing and responsive states that work out of the box.
• Rapid Turnaround: Ready to deliver a production-ready PR within 12–24 hours, clearing this task quickly.
• Track Record: 28 merged Web3 PRs — zero review ping-pong and immediate alignment with your conventions.

[Jafeth012]

I’d like to take on this feature; I have solid experience building responsive web interfaces, integrating paginated REST APIs, and implementing clean data tables, so I can directly add the new Protocol Revenue tab under Portfolio Staking, integrate GET /staker/:wallet/protocol-revenue with cursor pagination, render the specified dataset sorted by distributionDate descending, handle the empty state edge-cases, and deliver full coverage against all acceptance criteria within your 12-hour ETA—assign it to me and I will get started immediately!

[guptakumarranjeet150]

Hey team,

I can tackle Add a protocol revenue distribution history page for stakers showing past distributions and their share. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in accesslayerorg/accesslayer-client
• Implementation: Build Add a protocol revenue distribution history page for stakers showing past distributions and their share with clean React/Next.js components, responsive styling, and proper loading/error boundaries.
• Testing: Add component unit tests and ensure zero TypeScript/ESLint warnings.
• PR: Atomic commit with clean git hygiene and passing CI

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

[shobhamerabacha-star]

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

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

• Build Add a protocol revenue distribution history page for stakers showing past distributions and their share with clean React/Next.js components, responsive styling, and proper loading/error boundaries.
• Add component unit tests and ensure zero TypeScript/ESLint warnings.

Ready to deliver a clean, tested PR within 12–24 hours. Please assign!

[Chidi-Dev1]

The issue description is crystal clear, and I’d be glad to work on it. I’ll ensure the implementation is clean, tested, and submit a clean PR. Kindly assign it to me.