DX-069: Write /get-started/wallets

[IbrahimIjai]

Context

The app supports Freighter directly and a broader set through Stellar Wallets
Kit, with smart-account and passkey flows on the horizon. Readers need to know
which options exist, what each requires, and what the trade-offs are.

Scope

• Enumerate supported wallets from the actual integration in
  apps/web/src/features/wallet/ — do not list a wallet the code does not
  support.
• Per wallet: install, connect, network switching, and the one thing that most
  often goes wrong.
• Explain what connecting does and does not grant, and what signing a
  transaction authorises. Be specific; this is where users are exploited.
• Cover session persistence and what "disconnect" actually clears.
• Note passkey/smart-account support and its current status honestly.

Acceptance criteria

• The wallet list matches the code, with the source file named in the PR.
• The authorisation section is reviewed for accuracy against the signing
  path in the code.
• Each wallet's common failure is described with its real error text.
• check:content, check:links, and prose lint pass.

Out of scope

• Wallet security advice beyond what is specific to using SO4.

---

Spec: docs/dx_1/003_content_map.md §2 · Depends on: DX-068

[ignaciojulio]

Hi team, I would like to take on this issue (Issue #581: DX-069: Write /get-started/wallets).

Proposed Implementation Plan

1. Codebase Audit & Wallet Integration Mapping:

• Audit apps/web/src/features/wallet/ to extract the exact list of actively supported wallets (Freighter direct integration and modules supported via Stellar Wallets Kit).
• Trace the connection, network switching, session persistence, and disconnect logic to capture exact behaviors and state management in the code.
• Inspect the signing and authorization paths to precisely distinguish between what connecting an account exposes (read-only identity/public key) versus what transaction signing authorizes.

2. Authoring /get-started/wallets Documentation:

• Document supported wallets per the code implementation with clear install, connection, and network switching steps.
• Include specific troubleshooting guidance for each wallet's primary failure mode along with the real error text observed during integration.
• Clarify session persistence mechanisms and what "disconnect" clears in local state versus the wallet provider.
• Detail current support status and expectations for upcoming passkey and smart-account flows honestly.

3. Validation & Checks:

• Align documentation structure with docs/dx_1/003_content_map.md §2 and reference the source integration file directly in the PR description.
• Run and pass all required documentation and formatting checks (npm run check:content, npm run check:links, and prose linting).

Deliverables & Acceptance Criteria

• Comprehensive /get-started/wallets document reflecting actual code integration from apps/web/src/features/wallet/.
• Clear authorization breakdown (connection permissions vs. transaction signing authorization).
• Per-wallet failure modes documented with exact real-world error messages.
• Accurate status documentation regarding smart accounts and passkeys.
• All check:content, check:links, and prose lint checks passing cleanly.

Could you please assign this issue to me? I am ready to begin drafting the documentation. Thanks!

[osaa4]

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

I would like to work on this issue because: The core technical problem lies in the domain of multi-step state synchronization and transaction lifecycle preview patterns. I have extensive experience in this specific area, particularly in designing complex multi-stage wizard flows and ensuring form state persistence without triggering premature side effects.

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

[nonso7]

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

Can i work on this issue

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

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@nonso7's PR #645 was approved and merged by @IbrahimIjai.

🏆 @nonso7: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (637 total points). Track your full progress on GrantFox.

👏 Great work, @nonso7! Keep contributing to SO4-Markets.

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @nonso7 as part of the Stellar Wave Program's 8th Wave 🥳

Moderator's reason: [Auto-assessed] The PR was merged by maintainer @IbrahimIjai (mergedAt: 2026-09-06T16:07:07Z), and issue #581 was successfully closed as completed. The contribution provides a comprehensive, high-quality implementation of the /get-started/wallets documentation page along with related concepts as requested in the scope.

😎 @nonso7: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.