Activity export (CSV / JSON)

[truthixify]

Tier: S (½-1 day) Type: feature

Context

good-first-issue

Scope

The Activity page (/history from PR #37) stores entries locally but offers no export path. Users want to export for accounting.

Acceptance criteria

• Export button on Activity page
• CSV format (one row per entry, with timestamp, kind, direction, amount, asset, counterparty, tx hash, status)
• JSON format (typed structure)
• Download triggered client-side
• No server upload

Files to start with

• Export button + format selector
• CSV + JSON downloads correctly
• Test with 100+ entries
• Documentation in /help

Why this matters

• src/pages/History.tsx
• src/stores/activityStore.ts

[Husten150]

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

as a good developer i would love to work on this issue, with years of experience let me work on this.

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

[Meet-hybrid]

@Meet-hybrid has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Can I work on this please?

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

[Bokky73]

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

Hello sir, I would be so glad to work on this issues as I have a wonderful experience on problem solving.

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

[abbys-code-hub]

@abbys-code-hub has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to work on this issue. it's a small, complete feature: users need records, the data is already available locally, and client-side export respects privacy. Getting the formatting, scale testing, and documentation right means it actually works when users need it.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @abbys-code-hub to this issue.

[Chrisland58]

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

hi maintainer i will like to work on this issue

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

[drips-wave]

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

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

[truthixify]

@Chrisland58 Assigned. Welcome to wave 6 (or welcome back).

Quick expectations:

1. Branch from develop (default branch now, GitHub auto-picks).
2. Open a draft PR within ~3 days so we see direction.
3. Update at least every 5 days. Silence costs the assignment.
4. Acceptance criteria in the issue body are the merge bar.

Ask on the issue if anything is ambiguous before building.

[truthixify]

Resolved by #83 (merged into develop).