Integrate a real wallet (Freighter / Stellar Wallets Kit)

[DanielCotoJ]

Effort: L — Estimate: 10-14 h — Dependencies: none (pairs with #36) — Unlocks: #36 (real data source), #41 (vault dashboard)

Context

The session/holder layer (already merged) is complete, but the connector underneath is a mock. apps/credit-history/src/session/wallet-connector.ts always resolves to a fixed address:

const MOCK_ADDRESS = 'GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5';
// SEAM: … return a connector based on Freighter / Stellar Wallets Kit (address G… + signTransaction)

The UI (SessionProvider, useSession, the header WalletButton) must not change — only this factory and the concrete connector class.

Goal

Clicking "Connect" opens a real wallet (Freighter via Stellar Wallets Kit), returns the holder's real G… address, exposes signTransaction, and the DID is derived from it with didStellar (#34).

Step by step

1. Add the dependency to the app: pnpm --filter @acta-products/credit-history add @creit.tech/stellar-wallets-kit (or the Freighter API directly — justify the choice in the PR; verify Next 16 / React 19 compatibility).
2. Implement a RealWalletConnector implements WalletConnector that: detects the wallet, requests access, returns { address }, and provides signTransaction(xdr, { networkPassphrase }). Extend the WalletConnector interface with signTransaction (kept optional if needed for Secure presentation links (signed/encrypted, not plaintext base64) #39).
3. Make getWalletConnector() return the real connector, with a fallback to the mock when the wallet is unavailable (gate on an env flag, e.g. NEXT_PUBLIC_WALLET=real|mock, mock as default so CI/dev without an extension still works).
4. Read the network from NEXT_PUBLIC_STELLAR_NETWORK (same var as ActaProvider) and pass the right networkPassphrase. Handle user-rejected and wallet-not-installed errors with friendly UI states.
5. Verify session persistence still works after refresh (localStorage key acta:session:address).

Out of scope

• Querying credentials with the connected account → Wire the real ActaCredentialSource to the ACTA SDK #36.
• Signing real presentation transactions → Secure presentation links (signed/encrypted, not plaintext base64) #39.

Acceptance criteria

• Real connect flow returns the actual G… address; DID shows did:stellar:{network}:{G…}.
• SessionProvider / useSession / WalletButton are unchanged (only the connector/factory changed).
• Wallet-not-installed and user-rejected are handled without crashing.
• Mock fallback still works when NEXT_PUBLIC_WALLET is not real.
• pnpm lint && pnpm typecheck && pnpm build pass.

[ryzen-xp]

Hi maintainers 👋
I’m a blockchain developer with strong expertise in Stellar, Rust,TS and Stellar SDK integrations. I’ve worked on multiple Stellar-based smart contract and backend systems.

I understand the scope of this issue and can deliver a reliable, production-quality solution with proper tests and documentation.
Plz assign me !!

ETA: 24 hours

[delfinacorr]

Hi! I am a full stack developer and I would love to solve this issue. I have experience developing in the Stellar and Soroban ecosystem, and I am excited to work on this task to connect the interface with real wallets while maintaining a clean and robust transition. Thank you very much

[TheBigWealth89]

I would love to resolve this issue. Please assign it to me

[robertram]

Hi ACTA team! 👋
I'm a full-stack web3 developer with hands-on experience in the Stellar ecosystem. I led the frontend for a 20+ person team at Stellar GIVE Colombia 2026, building ACTA's verifiable credential solution for Corporación Interactuar (Next.js, TypeScript, ACTA SDK), so I'm already familiar with ACTA's architecture and conventions.
Beyond Stellar, I've shipped several wallet-connection integrations across chains, from wagmi/RainbowKit multi-wallet flows to custom connector abstractions sitting behind a factory pattern, which maps closely to what this issue needs.

I'll integrate the Stellar Wallets Kit to connect a real wallet, plugging it in behind the existing connector structure so the rest of the app (session handling, UI, etc.) doesn't need to change at all. I'll make it easy to toggle between the mock and the real wallet through an environment variable, so development and testing keep working smoothly even without a wallet installed. I'll also make sure the correct network is used, handle cases like a missing wallet or a rejected connection gracefully instead of crashing, and verify that the user's identity and session still persist correctly after a page refresh. Finally, I'll make sure everything passes linting, type-checking, and build steps before delivering, along with a short explanation of why I chose this wallet integration approach.

[real-venus]

Hi, I'd like to take this one on. Went through the issue and I'm familiar with the tech involved here — Stellar Wallets Kit / Freighter in a Next.js app. I'll implement a RealWalletConnector behind the existing factory (detect wallet → request access → return { address } + signTransaction(xdr, { networkPassphrase })), keep SessionProvider/useSession/WalletButton untouched, gate real-vs-mock via NEXT_PUBLIC_WALLET with mock as the safe default, read the network from NEXT_PUBLIC_STELLAR_NETWORK, handle not-installed/user-rejected without crashing, and confirm session persistence after refresh — all passing lint/typecheck/build. I move fast and deliver production-ready code — please assign to me and I'll get started immediately.