[Issue #42] Wallet: Freighter Connection Hook

[Ogstevyn]

Description

Create a React hook useFreighter that handles Freighter wallet connection, disconnection, and public key retrieval.

Requirements

• Detect if Freighter extension is installed.
• Implement connect(), disconnect(), and getPublicKey() methods.
• Store connection state in React context.
• Handle errors gracefully (extension not installed, user rejected).

Acceptance Criteria

• Hook returns { publicKey, isConnected, connect, disconnect, isFreighterInstalled }.
• Works in the browser environment only (SSR-safe).

Files to Create/Modify

• hooks/useFreighter.ts (Create)
• lib/stellar/wallet.ts (Create)

Test Requirements

• Unit test for hook state transitions.

[arandomogg]

@arandomogg has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi, I’d like to work on this issue.

I have experience building React hooks and integrating crypto wallets, so I can implement a robust and SSR-safe useFreighter hook for this. I’ll structure the solution to cleanly separate concerns by handling low-level wallet logic in lib/stellar/wallet.ts and exposing a simple, reusable API through the hook.

My approach:

Detect Freighter installation safely in the browser environment
Implement connect, disconnect, and getPublicKey with proper error handling (including user rejection and missing extension)
Manage and persist connection state using React context for easy access across the app
Ensure SSR compatibility by guarding all window-dependent logic
Write unit tests to validate state transitions and edge cases

The final hook will return exactly:
{ publicKey, isConnected, connect, disconnect, isFreighterInstalled }

I’ll keep the implementation clean, well-documented, and aligned with the existing project structure.

Estimated completion: a few hours.

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

[drips-wave]

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

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

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @arandomogg as part of the Stellar Wave Program's 3rd Wave 🥳

Moderator's reason: [Auto-assessed] The PR was merged and fully addresses the issue requirements by implementing the useFreighter hook and the underlying wallet logic in lib/stellar/wallet.ts. The contributor also included unit tests and went beyond the scope by adding balance fetching and contract contribution logic.

😎 @arandomogg: 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.