Wallet adapter abstraction + LOBSTR extension support

[ScriptedBro]

Context: Connection is hard-wired to Freighter . LOBSTR ships a browser extension with a similar API surface; users outside Freighter's audience are locked out.

Tasks:

• Define a StellarWalletAdapter interface: id, name, detect(, connect(, getAddress(, getNetwork(, signTransaction(xdr), disconnect( (sign used by the fE-013 Client-side Soroban signing for escrow release and approval confirmations)
• Refactor useWallet to consume adapters; Freighter becomes the first adapter (behavior unchanged)
• Implement a LOBSTR adapter behind the same interface
• Wallet picker UI on the wallet page/connect entry point listing detected adapters, with "not installed → install link" states

Acceptance criteria:

• Connecting via either extension works on testnet; selection persisted per browser
• Existing Freighter flows show no regression (manual pass + unit tests)
• Adding a third adapter requires only a new file implementing the interface (documented)

---

---

Estimated effort: 3 days

[Rufai-Ahmed]

@Rufai-Ahmed has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I'd love to work on this

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

[IsaacMsheliaSamuel]

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

Hello maintainer, I’m interested in working on this issue. I understand the requirements and I’m ready to implement the fix and submit a PR. I’d appreciate the opportunity to contribute. Thank you!

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

[princesslux]

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

Hi, I can handle adding tool call duration budget reporting to mcp. I'll implement the reporting, update the package and confirm all local checks pass while maintaining tight scope boundaries. Please assign this issue to me.

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

[drips-wave]

Congratulations, @Rufai-Ahmed! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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