Adopt stellar-wallets-kit, replace freighter-api

[grantfox-oss]

Sprint: 1 — Foundations · Area: wallet · Size: 1.5 d · Depends on: —
Source: docs/SPRINT-1-ISSUES.md #1

Context

Today frontend/lib/wallet-context.tsx calls @stellar/freighter-api directly and hard-codes the testnet passphrase. We need an abstraction that also supports LOBSTR (via WalletConnect). The chosen library is @creit.tech/stellar-wallets-kit.

Scope

• Add @creit.tech/stellar-wallets-kit to p2p-safe-swap/package.json.
• Refactor WalletProvider / useWallet to use the kit internally while keeping the exact same public API (publicKey, network, isConnecting, connect, disconnect, signTransaction). No downstream call sites should need changes.
• Read the network from NEXT_PUBLIC_STELLAR_NETWORK (testnet | mainnet) and pass the correct passphrase to the kit.
• Remove the direct @stellar/freighter-api import from wallet-context.tsx. Keep the dep in package.json only if the kit needs it transitively.

Acceptance

• Existing "Connect wallet" button still works with Freighter after the refactor (regression check).
• Signing an XDR still returns a signedTxXdr string.
• Switching NEXT_PUBLIC_STELLAR_NETWORK between testnet and mainnet flips the passphrase used to sign.
• No consumer file changed except wallet-context.tsx and the env example.

[AbuJulaybeeb]

Hi Maintainer, haven reviewed the description of the issue, and well experienced with Js Library,
I would like to hop on the issue and sure to deliver at ETA 2hrs

[Shadow-MMN]

I'd like to work on this issue.

From my understanding, this task is about replacing the direct Freighter API usage with @creit.tech/stellar-wallets-kit while keeping the existing wallet interface unchanged for consumers. My implementation will include:

Adding @creit.tech/stellar-wallets-kit to the project dependencies and refactoring WalletProvider / useWallet to use the kit internally while preserving the existing publicKey, network, isConnecting, connect, disconnect, and signTransaction API. I'll also replace the hard-coded testnet configuration with NEXT_PUBLIC_STELLAR_NETWORK, mapping testnet and mainnet to their respective Stellar network passphrases, and remove the direct @stellar/freighter-api import from wallet-context.tsx.

I'll verify that the existing Freighter connection flow continues to work, XDR signing returns the expected signedTxXdr string, switching between testnet and mainnet uses the correct passphrase, and that no unnecessary downstream consumer changes are introduced.

ETA: Within 2 days.

[grantfox-oss]

🦊 GrantFox — @AbuJulaybeeb has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #375)
2. Your PR will be reviewed by the Kaizenode maintainers

Good luck! Track your progress on GrantFox.