[HARD][DASHBOARD] Build Stellar activity dashboard for ownership and payment events

[Obiajulu-gif]

Overview

Build a Stellar activity dashboard that prepares ChainMove for viewing Stellar Testnet activity, including asset ownership, payment history, payout records, and Soroban event data.

Problem

ChainMove is moving toward Stellar integration. Users and admins need a product-friendly dashboard that explains onchain activity without requiring them to inspect raw explorer pages.

Expected solution

Create a Stellar dashboard module that can display:

• linked Stellar account public key
• selected network status: testnet or mainnet-ready
• asset ownership records
• payment activity
• pool ownership events
• payout events
• repayment receipt events
• Soroban contract event placeholders
• explorer links where applicable
• mock Stellar activity when ENABLE_MOCK_STELLAR=true

Implementation notes

This issue can start with mock and testnet-ready data. It does not need to execute live production settlement flows.

Files likely involved

• Stellar dashboard page/components
• lib/stellar/*
• user account linking helpers
• dashboard navigation
• mock Stellar service
• README or docs

Acceptance criteria

• Dashboard can show mock or testnet Stellar activity.
• Users can see linked public account information where available.
• Admins can view aggregated Stellar activity where appropriate.
• Explorer links are generated safely.
• Empty/loading/error states are handled.
• npm run lint and npm run build pass.

Suggested labels

dashboard, stellar, soroban, frontend, backend, hard

Difficulty

Hard

[Peolite001]

I would love to work on this issue

[Kureszn]

I've reviewed the issue and believe I can contribute effectively. My experience spans software development, blockchain technologies, cybersecurity and open source collaboration. I take a structured approach to contributions carefully understanding the existing codebase, identifying the root cause and delivering a thoroughly tested implementation.

[davidacunalopez]

Hi, I’ve reviewed the issue and explored the repo. I’m ready to implement this.

I have experience with Next.js app-router dashboards, MongoDB-backed APIs, and blockchain read-only integrations. For this issue I’ll reuse the existing Stellar foundation (lib/stellar/config, client, indexer, account linking, and StellarActivityPanel), unify the mock layer behind a dashboard service + API route, wire the UI to the user’s linked stellarPublicKey, and add the missing sections (assets, payments, pool/payout/repayment events, Soroban placeholders) with proper empty/loading/error states and explorer links.

I’ll validate mock and testnet-ready flows, extend existing tests, and ensure npm run lint and npm run build pass. I´ll do it around 24h-48h

[JuliobaCR]

Hey! I'd like to claim this issue.

Understanding the problem

ChainMove is moving toward Stellar integration but currently has no user-facing layer that translates on-chain activity into something meaningful. Without a dashboard, users and admins are left inspecting raw explorer pages — which is a product experience problem, not just a technical gap. The goal here is a clean, maintainable dashboard module that abstracts Stellar and Soroban activity into readable UI, with mock support so development isn't blocked on live settlement flows.

Proposed implementation

1. Stellar account linking and network status
Display the user's linked public key with a clear testnet/mainnet-ready indicator. Account linking helpers from existing utilities where available, with graceful fallback for unlinked accounts.

2. Activity sections
Build out each required section — asset ownership records, payment history, pool ownership events, payout events, repayment receipts, and Soroban contract event placeholders — as composable components so each can be developed and tested independently.

3. Mock layer via ENABLE_MOCK_STELLAR
Implement a mock Stellar service behind the same interface as the live data layer so the dashboard works end-to-end in development without testnet dependency. Switching between mock and live is a single env flag.

4. Explorer links
Generate explorer links safely — sanitized, network-aware (testnet vs mainnet), and consistently formatted across all event types.

5. Empty, loading, and error states
Every section handles all three states explicitly. No silent failures, no blank panels with no context.

6. Admin vs user views
User view scopes to their linked account. Admin view surfaces aggregated activity where appropriate, reusing the same underlying components.

7. Validation
Mock and testnet-ready data flows tested end-to-end. npm run lint and npm run build pass clean.

Estimated timeline

2–3 days

Background

I have experience building full-stack dashboards with Next.js app-router, blockchain read-only integrations, and modular frontend architecture. I'm also actively building TrulyLedger on Stellar/Soroban, so I'm familiar with the account model, event structure, and explorer link patterns specific to this stack. I'll start by mapping the existing lib/stellar/* foundation before writing any new code. Let me know!