Blockchain Core 0.17.2 / Core Concepts
Networks and wallet sessions
Configure public network metadata and understand Core’s provider-neutral wallet lifecycle.
Networks
Open Blockchain → Networks and enable only chains the site deliberately supports. Browser manifests contain public identifiers and safe metadata; private RPC credentials never belong in public configuration.
Use canonical CAIP-2 chain identifiers. A wallet address does not identify a network, and an enabled network does not guarantee that every provider adapter supports it.
Wallet Session
Core exposes a provider-neutral Wallet Session facade for reviewed surfaces. Provider packages discover wallets, request accounts, and react to account or chain changes. Core owns the shared state and lifecycle contract.
A fresh document starts disconnected and waits for explicit visitor interaction. Disconnect clears the current browser session; it does not revoke an account link owned by an authentication provider.
Acceptance checks
Test connect, rejection, account change, chain change, copy address, disconnect, reload, and a second explicit connection. Surfaces must agree on the active provider, ecosystem, chain, and account. If two components show different state, update Core and every provider consumer before enabling transactions.