Implement raffle detail page with merged contract + metadata

[Otaiki1]

Context

The raffle detail page should show both onchain data (price, tickets sold, end time, winner) and off-chain metadata (title, description, image). The backend merges these; the client just consumes GET /raffles/:id.

Goal

• Raffle detail page (e.g. /raffles/:id) fetches GET /raffles/:id and renders: image, title, description, ticket price, tickets sold / max, end time, status, and CTA (buy ticket, or winner/refund if finalized/cancelled).
• Handle 404 and loading state; optional: real-time updates or refetch on focus.

Contributor guide

1. Directory: client/
2. Add route and page component for /raffles/:id. Use a hook (e.g. useRaffle(id)) that fetches from backend.
3. Map backend response to UI: use merged fields (title, description, image_url from metadata; price, tickets_sold, status from indexer/contract).
4. Add "Buy ticket" button that triggers SDK ticket purchase flow (separate issue if not done).
5. Ensure design matches existing Tikka UI (cards, typography).

References

• ARCHITECTURE.md — Data Merging Pattern; REST GET /raffles/:id.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 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

[Luluameh]

@Luluameh has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I would love to work on this.
kindle assigned me

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

[Codekill33]

@Codekill33 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Please can i take this on?
i am experienced with smart contracts and frontend development

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

[Stephan-Thomas]

@Stephan-Thomas has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

hi, i would like to work on this

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

[drips-wave]

Congratulations, @Stephan-Thomas! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @Stephan-Thomas: 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 issued 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 🌊