This is a production React 18/TypeScript single-page application that serves as a self-custodial crypto wallet and dApp-connect hub for the Unicity network. The codebase implements the full wallet lifecycle (create, restore, backup, password encryption, auto-lock, cross-tab lock synchronization), token/NFT management, payment requests, a Connect protocol for iframe/popup dApp approval flows, network switching, a cross-chain bridge module, subscription/API-key gating, DM and group chat, marketplace browsing, and a desktop-like app launcher for embedded iframe agents. The architecture is a monolith SPA with a provider-based SDK wrapper (`SphereProvider`, `ConnectProvider`, `UpgradeProvider`), TanStack Query for server state, and a runtime-config system that rewrites deployment-specific values in `runtime-config.js` via Docker, enabling build-once/promote-many delivery behind nginx. The application is heavily security-focused: Connect intents go through settle-window shields, duplicate-send guards, verified-origin checks, per-network approval stores, and fail-closed network capability allowlists. Sentry telemetry is deliberately scrubbed to send route patterns rather than URLs or query strings, and NFT loading is fingerprint-verified and privacy-gated by minter-chosen hosts. Testing is extensive, with hundreds of Vitest unit tests covering security invariants, SDK version pins, localStorage corruption tolerance, prototype-pollution resistance, and wallet-lock race conditions, plus Playwright smoke/perf tests. The code is heavily commented with references to historical bugs and SDK contract canaries, which aids maintenance but also creates coupling to the upstream `@unicitylabs/sphere-sdk`. The main external dependencies are the Sphere SDK, bridge-core/plugin packages, a bridge return service, wallet-api backends, a subscription gateway, Nostr relays for chat, and Paymento for paid-plan checkout. The repository is purely an application; there is no data-research or analytics content beyond runtime telemetry and marketplace API consumption. Notable engineering strengths include the runtime-config indirection, isolated module boundaries around bridge logic, and small, well-tested utility modules for storage, URL safety, error humanization, and privacy scrubbing. The main drift risks are the `file:`-linked SDK packages, SDK-version-pinned tests, heavy mock usage, and a very large `ExplorePage.tsx` that is approaching component-split territory.