Skip to content

MetaMask 0.6.1 / Wallet

MetaMask connection lifecycle

Connect, change networks, disconnect, and reload without creating a stale wallet session.

MetaMask registers provider adapters while Blockchain Core owns the shared Wallet Session. A fresh page begins disconnected and does not request accounts until the visitor chooses Connect.

Use the Terminal wallet panel or wallet, connect, metamask, mm, and wallet-status. Confirm the provider, ecosystem, CAIP-2 chain, and shortened address before relying on the session.

Test connect, rejection, account change, network change, copy address, disconnect, reload, and a second explicit connection. A pending provider request must finish or be rejected before another begins.

Disconnect clears browser session state. It does not automatically remove a wallet deliberately linked to a WordPress account for login.

Was this documentation helpful?Your response helps us improve this page.