Multi-wallet support for Stellar (Albedo, xBull, LOBSTR beyond Freighter)

[truthixify]

Labels: Stellar Wave, stellar, feature, drips, help-wanted
Tier: L (1–2 weeks)
Type: feature

Context

Today the demo's Stellar flow only supports Freighter. Stellar has a real wallet ecosystem — Albedo (web-based, no extension required), xBull (popular alternative), LOBSTR (web + mobile), Hana, and others. A visitor without Freighter installed gets a dead end. Many won't bother installing a new extension just to try a demo.

We should support at least three Stellar wallets out of the box.

Scope

1. Abstract the wallet layer:
   • Create src/wallets/stellar/ with a StellarWallet interface:

     interface StellarWallet {
       readonly id: string
       readonly name: string
       readonly icon: string
       isAvailable(): Promise<boolean>
       connect(): Promise<{ publicKey: string; network: string }>
       signTransaction(xdr: string, opts: SignOpts): Promise<{ signedXdr: string }>
       disconnect(): Promise<void>
     }

2. Implement adapters:
   • FreighterAdapter (existing, just refactor onto the interface).
   • AlbedoAdapter using @albedo-link/intent.
   • xBullAdapter using @creit.tech/xbull-wallet-connect.
   • LobstrAdapter using @lobstrco/signer-extension-api.
3. Connect-wallet UI:
   • On the chain switch to Stellar, show a wallet picker modal listing all detected wallets.
   • Each entry: icon, name, status badge ("Installed" / "Not detected" with install link).
   • Persist the chosen wallet in localStorage so reconnect skips the picker.
4. Stellar Wallets Kit — consider using @creit.tech/stellar-wallets-kit as a one-stop integration instead of writing adapters manually. Argue the trade-off in the PR (vendor lock-in vs. ergonomics).

Constraints

• Each adapter's signing must produce identical XDR — verify with a unit test.
• The auto-sign / stealth-key derivation flow (demo/04) must work with any wallet.
• Bundle size impact ≤ +15 KB per wallet adapter, lazy-loaded.

Acceptance criteria

• Wallet abstraction interface + ≥ 3 adapters.
• Wallet picker UI.
• Persistence of last-used wallet.
• Playwright tests for at least the Freighter and Albedo paths.
• Documented in docs/guides/stellar-quickstart.mdx (or follow-up issue).

Why this matters

Forcing a specific wallet is a 5-second bounce trigger. Supporting the top three wallets gives roughly 95% of Stellar users a connect-and-go experience.

Resources

• Stellar Wallets Kit: https://github.com/Creit-Tech/Stellar-Wallets-Kit
• Albedo: https://albedo.link
• xBull: https://xbull.app
• LOBSTR Signer: https://lobstr.co/signer

[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.

[drips-wave]

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

🧑‍💻 @Opeyemi01-del: 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]

Resolved by #49 (merged into develop).