[{"data":1,"prerenderedAt":96},["ShallowReactive",2],{"navigation":3,"integration-metamask":31},[4,22],{"title":5,"path":6,"stem":7,"children":8,"page":21},"Introduction","/docs/introduction","1.docs/2.introduction",[9,13,17],{"title":10,"path":11,"stem":12},"Why","/docs/introduction/why","1.docs/2.introduction/1.why",{"title":14,"path":15,"stem":16},"Blockchain as solution?","/docs/introduction/blockchain-as-solution","1.docs/2.introduction/2.blockchain-as-solution",{"title":18,"path":19,"stem":20},"What's the Solution?","/docs/introduction/wag3s-as-solution","1.docs/2.introduction/3.wag3s-as-solution",false,{"title":23,"path":24,"stem":25,"children":26,"page":21},"Api Documentation","/docs/api-documentation","1.docs/3.api-documentation",[27],{"title":28,"path":29,"stem":30},"getting started","/docs/api-documentation/api","1.docs/3.api-documentation/1.api",{"id":32,"title":33,"body":34,"capabilities":76,"description":35,"extension":81,"faq":82,"hero":84,"integration":85,"meta":86,"navigation":87,"path":88,"related":89,"seo":92,"stem":93,"summary":50,"useCases":94,"workflow":94,"__hash__":95},"integrations/integrations/metamask.yml","Wag3s × MetaMask — EOA Wallet Accounting",{"title":33,"description":35,"seo":36,"integration":39,"hero":46,"summary":50,"capabilities":51,"faq":63,"related":67},"Connect MetaMask wallets read-only to Wag3s. Multi-chain EVM activity, history backfill, real-time updates.",{"title":37,"description":38},"MetaMask + Crypto Accounting — Wag3s Integration","Connect MetaMask wallets to Wag3s. Read-only, multi-chain EVM, history backfill, ENS resolution.",{"name":40,"slug":41,"category":42,"url":43,"direction":44,"sync":45},"MetaMask","metamask","wallet","https://metamask.io","read-only","Real-time",{"eyebrow":47,"title":48,"subtitle":49},"Wallet integration","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.\n",{"title":52,"items":53},"What MetaMask connection does",[54,57,60],{"title":55,"description":56},"Multi-chain EVM coverage","Same address across every EVM chain.",{"title":58,"description":59},"ENS resolution","Wallet labels, counterparty labels resolved via ENS where available.",{"title":61,"description":62},"History backfill + real-time","Past activity backfilled on connection; new transactions land in real time.",[64],{"question":65,"answer":66},"Do I need to connect via MetaMask Snap?","No — a wallet address is enough. Read-only ingest doesn't require any signing.",[68,72],{"to":69,"title":70,"description":71},"/chains/ethereum","Ethereum chain coverage","L1 EVM coverage.",{"to":73,"title":74,"description":75},"/integrations/walletconnect","WalletConnect integration","Multi-wallet protocol-level connection.",{"title":52,"items":77},[78,79,80],{"title":55,"description":56},{"title":58,"description":59},{"title":61,"description":62},"yml",[83],{"question":65,"answer":66},{"eyebrow":47,"title":48,"subtitle":49},{"name":40,"slug":41,"category":42,"url":43,"direction":44,"sync":45},{},true,"/integrations/metamask",[90,91],{"to":69,"title":70,"description":71},{"to":73,"title":74,"description":75},{"title":37,"description":38},"integrations/metamask",null,"B5QmX9o50BonwI3WnQnb_v1db6RXa80K9n4stJc6XsA",1778407990231]