On-chain Activity Feed — Transaction History per Wallet

[Villarley]

Overview

Add a transaction history / activity feed that shows a connected wallet's past on-chain interactions with Neko contracts (vaults, lending, swaps, pools).

Motivation

Users currently have no way to see what they've done inside Neko. An activity feed is a baseline feature for any financial app and is critical for trust — users need to verify their transactions happened.

Scope

• Index relevant Stellar/Soroban events via Horizon and/or RPC getLedgerEntries
• Events to track: vault deposit/withdraw, lending supply/borrow/repay, swap executed, pool join/exit
• UI: a feed component on the Dashboard page showing:
  • Transaction type (icon + label)
  • Amount and asset
  • Timestamp
  • Link to Stellar Expert
• Pagination or infinite scroll (last 50 txs)
• Filterable by type

Technical Notes

• Use Horizon /accounts/{address}/transactions + /accounts/{address}/operations as data source
• For Soroban contract events: rpc.getEvents() filtered by contract ID and topic
• Consider a lightweight React Query polling approach (no WebSocket needed for POC)

Acceptance Criteria

• Activity feed visible on Dashboard for any connected wallet
• Shows at least: vault deposits/withdraws and swap history
• Each entry links to Stellar Expert
• Works on mobile layout
• Empty state handled gracefully (new wallet with no history)

[devkryssie]

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

Hi Maintainer,

I’m a smart contract and full-stack developer and would love to contribute to this issue. I’m an experienced contributor with hands-on expertise in Rust, Soroban, Cairo, and TypeScript.

I’m passionate about building secure, scalable blockchain solutions, with a strong emphasis on writing clean and maintainable code. Based on the scope of this issue, I’m confident I can deliver a complete solution within 24 hours of assignment.

I’d greatly appreciate the opportunity to contribute and help move this forward.

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

[AbuJulaybeeb]

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

Hi Maintainer
I would like to hop on this issue

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

[drips-wave]

Congratulations, @AbuJulaybeeb! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @AbuJulaybeeb as part of the Stellar Wave Program's 4th Wave 🥳

Moderator's reason: [Auto-assessed] PR #205 has been open for more than 24 hours with no maintainer objections. The contribution comprehensively addresses the issue by implementing the Activity Feed UI, the data fetching service (combining Horizon and Soroban RPC), and the necessary React Query hooks, while also correctly handling pool states.

😎 @AbuJulaybeeb: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.