MetaMask Connect

Connect your wallet

Modern dApps use the browser's Ethereum provider (usually MetaMask) to request the user's accounts and to sign transactions. This page shows both a simulated flow and an optional real request to your wallet.

Status: Not connected

What this demo demonstrates

How a dApp triggers a wallet connection request (`eth_requestAccounts`).
How to read the connected account and chain id from the provider.
Why dApps must never ask for seeds or private keys — the provider handles signatures.

Security reminder

Never share your seed phrase or private key. Real dApps request only permissions (accounts, signatures). If a webpage asks for your seed, it is malicious.

Demo only — safe by default

// Minimal example (dApp side) if (window.ethereum) { try { // ask user to connect accounts (opens MetaMask prompt) const accounts = await window.ethereum.request({ method: 'eth_requestAccounts' }); // accounts[0] is the selected address const chainId = await window.ethereum.request({ method: 'eth_chainId' }); console.log('Connected', accounts[0], chainId); } catch (err) { // user rejected or error console.error(err); } } else { // no injected provider (MetaMask not installed) alert('Please install MetaMask!'); }