Product
Wallet & chain
What connecting a wallet changes, and what it deliberately doesn't.
The header shows a chain badge (Base Chain) and a wallet-connect button on every page. Both are identity and context — they say which network a reading is scoped to and who, if anyone, is currently connected. Neither changes what any page shows: every price, table and graph renders identically connected or not, and the badge and button are present even on pages that show no wallet-specific data at all.
The technical connection
Connecting uses an injected-provider flow (EIP-1193, discovered via EIP-6963) wired through wagmi and viem — the standard stack most production dApps use, not a custom bridge. There's deliberately no WalletConnect project ID or relay session involved, because a relay exists to carry signing requests between a wallet and a dApp, and this surface never constructs one.
What's displayed vs. what's stored
Once connected, the header can show the connected address as context. That connection state lives in the browser's local storage only, wagmi's default client-side persistence — nothing about who connected, when, or from where is sent to or retained by any State.OS server.
If that ever changes
If a future version of State.OS adds anything that writes to a chain, it will live outside this read-only surface as new, clearly separated functionality — not folded into this connector. For now, the wallet button exists so identity is visible, not so a transaction is one click away.