Rebuild Albedo, xBull, LOBSTR wallet adapters

[truthixify]

Extra labels: feature, wallets, stellar
Tier: L (5-7 days) | Type: feature

Context. Only Freighter + WalletConnect remain after Wave 6 cleanup. LOBSTR is the primary mobile wallet; xBull + Albedo are common on desktop. Rebuild against the current interface.

Scope.

• Implement three adapters under src/wallets/stellar/.
• Register in index.ts with capability detection.
• LOBSTR uses mobile deep-links.
• Contributor tests each on real extension / app; attaches recording.

Acceptance.

• All three compile without @ts-nocheck
• Wallet picker only shows installed extensions
• Recording proves connect + sign + send for each
• Missing-extension state links to install page

Files. src/wallets/stellar/FreighterAdapter.ts (reference), src/wallets/stellar/index.ts, src/components/StellarWalletPicker.tsx.

[ZeePearl56]

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

I would like to work on this issue because I will get it done well.

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

[afeezorobsco-cyber]

@afeezorobsco-cyber has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

i would like to work on this issue

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

[fathiaoyinloye]

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

Hi, I'd like to work on this issue. I have relevant experience with the technologies and concepts involved, and I'm confident I can make the necessary implementation to ensure the it meets the acceptance criteria. I'd be happy to contribute to this task.

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

[collinsezedike]

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

GM Truthixify, I'd glad to scratch this one off your list.

Capability detection ties these three together, since Albedo, xBull, and LOBSTR each have a fundamentally different connection model and the picker needs a consistent way to ask each one whether it's actually available before showing it as an option.

Albedo and xBull can be detected via an injected global. LOBSTR can't, since it's mobile-only and deep-link based. I'll handle that difference explicitly rather than forcing one detection method onto all three.

Here's my plan:

• AlbedoAdapter.ts: wrap Albedo's intent-based API, following FreighterAdapter.ts's interface shape for connect/sign/send
• XBullAdapter.ts: wrap xBull's browser extension API (window.xBullSDK or equivalent), detecting installation via the injected global
• LobstrAdapter.ts: implement via mobile deep-links, since LOBSTR has no browser extension; capability detection here means checking whether the deep-link scheme can plausibly be handled (likely defaulting to "available" on mobile user agents rather than a hard detection, since deep-link presence can't be queried the way an injected extension global can)
• Register all three in src/wallets/stellar/index.ts alongside the existing adapters, each exposing a consistent isAvailable()-style check the picker can query uniformly
• Update StellarWalletPicker.tsx to only render adapters that report as installed/available, and to show a "missing extension" state linking to the install page for ones that aren't
• Ensure all three compile cleanly with no @ts-nocheck
• Manually test connect, sign, and send against the real extension/app for each of the three, recording each session as required

Happy to start as soon as I'm assigned.

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

[JinadJay]

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

LOBSTR wallet adapters is something similar to what i've been working on, kindly assign this issue to me to resolve.

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

[drips-wave]

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

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