MetaMask — connect any EVM wallet, read-only
MetaMask is the most-used self-custody wallet in Web3. We connect to it the same way an explorer does — read-only, no signing rights, no key access.
Connecting a MetaMask wallet to Wag3s is a paste-the-address operation, not an OAuth or signing flow. We track the wallet's on-chain activity across every supported EVM chain — Ethereum, Arbitrum, Optimism, Base, Polygon, BNB Chain, Avalanche, every L2, and the long tail of EVM rollups. ENS names resolve automatically; transaction labels follow.
What MetaMask connection does
Multi-chain EVM coverage
Same address across every EVM chain.
ENS resolution
Wallet labels, counterparty labels resolved via ENS where available.
History backfill + real-time
Past activity backfilled on connection; new transactions land in real time.
The connection in 4 steps
Import wallet address from MetaMask
Copy the public address from MetaMask (or your ENS name) and paste it into Wag3s. No extension, no signing, no access to private keys required.
Select chains to track
Choose which EVM chains to activate — Ethereum mainnet, Arbitrum, Optimism, Base, Polygon, BNB Chain, Avalanche, and the full L2 ecosystem. New chains can be added at any time.
Backfill transaction history
Wag3s fetches the full on-chain history for each selected chain, including swaps, transfers, DeFi interactions, NFT transactions, and gas costs.
Classify and label activity
Each transaction is classified by type — swap, transfer, payroll, DeFi yield, NFT sale, gas — and counterparty labels are resolved via ENS where available.
Common configurations
The founder holds ETH and ERC-20 tokens across Ethereum and Arbitrum in a MetaMask EOA. Wag3s tracks all activity read-only, produces monthly P&L from realized gains and DeFi income, and exports JEs ready for QuickBooks.
A DAO contributor receives periodic token distributions from a vesting contract directly to their MetaMask address. Wag3s classifies each incoming transfer as compensation income, with cost basis and FMV recorded at the grant date for tax reporting.
The treasury team uses MetaMask Institutional for multi-sig operations. Wag3s connects to the underlying EVM addresses, ingests all treasury movements across chains, and produces a consolidated treasury report for the finance committee.
MetaMask integration questions
Do I need to connect via MetaMask Snap?
No — a wallet address is enough. Read-only ingest doesn't require any signing.
Is MetaMask Institutional (custodial) supported differently from standard MetaMask?
MetaMask Institutional (MMI) provides an additional custody layer with transaction policies and approval workflows on top of the standard MetaMask interface. For accounting purposes, Wag3s connects to the underlying EVM addresses — the on-chain data is identical regardless of whether the wallet uses MMI or standard MetaMask. If your MMI setup connects to a custody provider (Fireblocks, Qredo, etc.), you can also connect those providers directly to Wag3s for policy-level attribution alongside the on-chain data.
Do MetaMask Snaps or third-party browser extensions affect transaction import?
No. Wag3s ingests transaction data directly from the blockchain using the wallet's public address — it does not interact with the MetaMask extension, Snaps, or any browser-level tooling. Extensions that modify MetaMask's UI or add functionality have no impact on the on-chain data Wag3s reads. The only dependency is that the public address is correct; the wallet software used to sign transactions is irrelevant to the import.
Other connectors that pair with this one.
Connect MetaMask in minutes
Free during Alpha. No credit card. Native sync, audit trail, no spreadsheets.