Stealth account labeling + personal organization

[truthixify]

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

Context

The Receive page shows every detected stealth address as a truncated string. After a few weeks of activity, users have dozens of these and no way to remember which one was "the rent payment" vs. "the freelance gig" vs. "the random tip." Even though stealth addresses are meant to not be linked, the user's own private labels are a legitimate UX affordance.

This is purely client-side — no labels ever leave the user's browser.

Scope

1. Storage: per stealth-address private notes in localStorage keyed by ${walletPubkey}:${stealthAddress}:

   type StealthLabel = {
     stealthAddress: string
     label: string          // user-chosen
     tags: string[]         // optional
     hiddenAt?: timestamp   // user can "archive" entries
     createdAt: timestamp
   }

2. Receive page UI:
   • Inline editable label field next to each stealth-address row (click pencil icon → text input → save on blur or Enter).
   • Tag chips below the label; clicking a chip filters the list to that tag.
   • "Hide" action per row to declutter (still findable via "show hidden" toggle).
   • Search input at the top filters by label substring or tag.
3. Privacy warning:
   • On first label save, show a one-time tooltip: "Labels are stored only in this browser. Clear browser data = lose labels. Wraith never sees them."
4. Import / export:
   • "Export labels" → downloads JSON file.
   • "Import labels" → file picker → merges (with conflict prompt).

Constraints

• Labels must NEVER leak to network calls (no telemetry, no error reporting with label data, no Sentry breadcrumbs).
• Storage is per-wallet — disconnecting and connecting a different wallet shows an empty label store.
• Label text length cap (e.g., 64 chars) to prevent UI breakage.

Acceptance criteria

• Labeling implemented and persistent across reloads.
• Search + tag filter working.
• Hide / archive flow.
• Export / import JSON.
• Privacy warning on first save.

Why this matters

A wallet without categorization is a spreadsheet. Even a power user has a memory budget — letting them write down "what was this for?" turns the Receive page from a haystack into a notebook.

[Opeyemi01-del]

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

I would love to work on this issue

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

[JafetCHVDev]

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

Hello Team,

My Background

My name is Cristian, and I’m a passionate full-stack developer from Costa Rica 🇨🇷💻. I’m excited about the opportunity to contribute to your Stellar-based project during Drips Wave! 🌊
I enjoy building web applications that combine clean user interfaces with solid back-end logic and reliable databases.

Experience

I have experience developing web applications using technologies such as React, .NET Core, SQL Server, and Firebase. I’ve worked on projects that include role-based systems, CRUD platforms, booking systems, and data-driven web apps.
While I’m still growing in Web3 and blockchain, I’m highly motivated to learn and apply these technologies, especially within the Stellar ecosystem.

I’m driven by the opportunity to improve my skills, collaborate with a talented team, and make a meaningful contribution to your project.

Links

You can find my profiles and links here:

GitHub: https://github.com/JafetCHVDev

Thank you for considering my candidacy. I am excited about the opportunity to contribute to this project and create a positive impact. Please let me know if you have any questions or need additional information.

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

[idrisososanwo]

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

Hi, I would like to work on this issue

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

[drips-wave]

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

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