Stellar transaction history view (per chain)

[truthixify]

Labels: Stellar Wave, stellar, feature, drips, help-wanted
Tier: M (2–4 days)
Type: feature

Context

The demo lets users send and receive but provides no view of what they've done. After a successful tx, the success card disappears and the user has only the explorer link they may or may not have clicked. We need a persistent "Activity" view per chain.

Stellar first; other chains as follow-ups.

Scope

1. Add an /activity route in the demo navigation (next to Send / Receive).
2. Persist tx events to localStorage per chain + per wallet address (key: wraith:activity:${chain}:${address}):
   • kind: "send" | "receive" | "withdraw" | "register-name"
   • chain: "stellar"
   • direction: "out" | "in"
   • amount, asset, counterparty (truncated stealth address or .wraith name)
   • txHash, timestamp, status (pending | confirmed | failed)
3. Hooks: every successful tx submission writes an entry; on app load, poll Horizon for pending entries to update their status.
4. UI: reverse-chronological list with chain badge, kind icon, amount, counterparty, and a chevron to open details.
5. Filter chips: by chain, by direction, by status.
6. Empty state with a CTA to Send.
7. "Clear history" with confirm — purges localStorage for this wallet + chain.

Constraints

• Don't show entries from other wallets on disconnect/reconnect-as-different-account.
• Don't leak stealth keys — never store derived private keys in localStorage.
• Size cap: keep the most recent 100 entries per chain + wallet.

Acceptance criteria

• /activity route with per-chain filtering.
• Local persistence working across reloads.
• Pending → confirmed transitions on Horizon poll.
• Empty state, clear-history flow.
• Playwright test exercising a send-and-see-it-in-activity loop.

Why this matters

A user with no history view doesn't trust the app. A user with a history view trusts it instantly.

[Maxxi4l]

@Maxxi4l has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I've viewed the issue and know what is required to solve it. I would like to help with it

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

[thebabalola]

@thebabalola has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi! I'd love to build the activity view for Wraith's transaction history. A persistent /activity view is key. I'll add this route next to Send/Receive and pull chain-specific historical logs from Stellar. I've built transaction history UI grids with paginated data fetching and filters for Stellar Horizon endpoints. I will integrate a responsive, clean table. Ready to integrate this UX!

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

[D-Ochuko]

@D-Ochuko has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Gm! I'd like to work on this.

I've gone through the issue and understand what needs to be done. I'll keep the fix scoped, clean, and tested — and communicate clearly if anything comes up along the way.

Ready to start immediately. Feel free to assign it!

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

[truthixify]

@Maxxi4l has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I've viewed the issue and know what is required to solve it. I would like to help with it

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

What's required to solve it @Maxxi4l ???

[drips-wave]

Congratulations, @thebabalola! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @thebabalola: 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 awarded 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 🌊