Claim History per User

[dDevAhmed]

📚 Overview

Show a list of all claims submitted by a user and their current statuses.

---

🎯 Objectives

• Display claims created by user
• Show status (pending / verified / disputed / resolved)

---

🧠 Scope

UI

• Claims list
• Status badges
• Pagination or infinite scroll

Logic

• GET GET /users/:address/claims

---

🎨 Design Reference

Follow canonical designs in:

truthbounty/designs/dashboard/4-history.png

---

✅ Acceptance Criteria

• Claims load correctly
• Status visible
• Links to claim detail page

---

⏳ Complexity & Effort

Complexity: Low
Estimated Effort: ~0.25–0.5 day

---

📌 Notes

This issue includes UI implementation and must follow canonical designs in the parent repository.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 100 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[No-bodyq]

@No-bodyq has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hello I will love to work on this issue
I am a fullstack developer
I can handle it in the stipulated time}
Please assign

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

[edehvictor]

@edehvictor has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi Team,

I am a Frontend Engineer with experience in building data-driven dashboards using Next.js and TypeScript. I can implement the Claim History page, ensuring it matches the design specifications and handles data states efficiently.

Implementation Plan:

Data Fetching: I will use a data fetching hook (like SWR or TanStack Query) to retrieve user claims from GET /users/:address/claims, implementing Pagination/Infinite Scroll to handle lists efficiently.

UI Components: I will build the ClaimHistoryList component, ensuring the Status Badges (Pending, Verified, Disputed, Resolved) use distinct, accessible colors as per the design reference (truthbounty/designs/dashboard/4-history.png).

Navigation: I will ensure each list item is clickable, routing the user to the specific Claim Detail Page.

Responsiveness: I will ensure the list layout adapts gracefully to mobile screens, potentially collapsing columns or switching to a card layout if necessary.

ETA: 2–4 hours.

I am ready to start immediately.

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

[MJ-RWA]

@MJ-RWA has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I’d like to work on this issue. I have experience building user-centric lists in React, including paginated and infinite-scroll views, status badges, and API-driven dashboards.

I can fetch and display user claims from /users/:address/claims, show clear status indicators, link each item to its detail page, and ensure the UI follows the canonical dashboard designs. This fits well within the estimated 0.25–0.5 day scope.

Please assign this issue to me so I can get started.

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

[Obiajulu-gif]

@Obiajulu-gif has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

GM maintainer, I would love to implement Claim History per User by wiring a reusable claims query layer to GET /users/:address/claims, then building a responsive history screen that matches the canonical dashboard design with status badges, pagination/infinite scroll, and deep links to claim details.

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

[simplicityf]

@simplicityf has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I'm applying for this issue because I’m a fan of building clean, informative dashboards where users can track their data at a glance. I’ll implement the claim history list by mapping the API response to the design's status badges, ensuring the flow to the detail pages is intuitive and quick. I'll also make sure the list handles pagination or infinite scroll smoothly so the performance stays snappy as a user's claim history grows.

ETA: 8hrs

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

[KingFRANKHOOD]

@KingFRANKHOOD has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hello, I’m a full stack developer with hands-on experience

I focus on writing clear, maintainable code and making sure features work as expected end to end, not just in isolation. I communicate progress regularly and keep things transparent as I work. I’m confident I can complete this task within an ETA of 24 hours while providing consistent updates throughout the process.

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

[Olowodarey]

@Olowodarey has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hello am a frontend dev and am ready to implement this function will be done within 24 hours

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

[tali-creator]

@tali-creator has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I’ve carefully gone through the issue description and taken time to understand the existing codebase and expected outcome. Based on my experience and the scope of this task, I’m confident I fully understand what needs to be done and how it fits into the project’s overall architecture.

I’m a full-stack Stark developer with 4+ years of hands-on experience, and I’m very confident in my ability to deliver a solid, production-ready solution. I’m 100% certain I can complete this task within 24 hours while maintaining code quality, clarity, and alignment with the project’s standards. I’d be glad to take this on and contribute effectively if assigned.

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

[Sendi0011]

@Sendi0011 has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hello, i will like to work on this, i am a frontend/smartcontract developer with experience skill solving issues like this. i am also an active Open source contributor.
ETA: 6 hours

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

[akordavid373]

@akordavid373 has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi! I’d like to implement the Hero Section. I have strong experience in React + Tailwind and a sharp eye for Figma-to-code fidelity. I'll ensure the layout is pixel-perfect and fully responsive across all devices. Ready to start now!"

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

[DIFoundation]

@DIFoundation has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I’d like to work on this issue because I’ve built user-specific history views in Web3 dashboards, including status-driven lists, badges, and pagination tied to wallet addresses. With experience integrating REST endpoints and matching existing design systems, I can implement a clean, accurate claim history that’s easy to scan and navigate.

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

[Lynndabel]

@Lynndabel has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

can i work on this please? ETA 10HOURS

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