WalletConnect — the protocol behind every wallet
WalletConnect connects 600+ wallets to dapps. We use it to identify your wallet address — then ingest read-only from there.
WalletConnect is the protocol the wallet ecosystem uses to communicate with dapps. For Wag3s, the simplest onboarding flow is: tap "Connect", scan a QR with your wallet of choice (Rainbow, Trust Wallet, OKX Wallet, Zerion, Argent, every WalletConnect-compatible option), and we read the wallet address. From there, ingest is read-only via the chain RPC — no signing, no key access, no transaction-broadcasting capability.
What WalletConnect connection does
600+ wallet support
Any WalletConnect v2-compatible wallet.
Address identification only
We use the connection to identify the address, then read on-chain.
Multi-chain
Every EVM chain, plus Solana, Bitcoin, and others where supported.
The connection in 4 steps
Initiate WalletConnect session in Wag3s
Click "Connect wallet" in Wag3s to generate a WalletConnect QR code or deep-link URI. This works with any WalletConnect v2-compatible wallet — Rainbow, Trust Wallet, OKX Wallet, Zerion, Argent, and 600+ others.
Scan QR or approve in mobile wallet
Open your wallet app and scan the QR code or tap the deep link. Approve the connection request — Wag3s requests read-only access to the wallet address only; no signing or transaction-broadcasting permissions are requested.
Wallet address identified and ingested
WalletConnect returns the wallet's public address. Wag3s uses this address to ingest on-chain transaction history across all supported chains via chain RPC — the WalletConnect session itself is not needed after address identification.
Full on-chain activity tracked read-only
From this point, Wag3s reads on-chain data directly from chain indexers and RPCs. No persistent WalletConnect connection is maintained; the wallet app does not need to remain open.
Common configurations
The user holds assets in a Rainbow wallet backed by a Ledger hardware device. Rather than manually copying addresses, they connect via WalletConnect in seconds. Wag3s identifies the address and begins ingesting cross-chain activity without any further interaction from the wallet app.
A contributor uses Trust Wallet for EVM activity, Phantom for Solana, and MetaMask for Ethereum mainnet. They connect each via WalletConnect (or address paste) to a single Wag3s workspace, producing a unified cross-chain portfolio view and tax report without switching between tools.
A Web3 accountant needs to onboard 10 client wallets during a discovery session. Using WalletConnect's QR code flow, each client connects their wallet in under a minute. Wag3s immediately begins backfilling transaction history for each address, cutting onboarding time from hours to minutes.
WalletConnect integration questions
Does Wag3s store the WalletConnect session persistently?
No. The WalletConnect session is used only to identify the wallet address. Once the address is confirmed, Wag3s reads on-chain data directly from chain indexers — the WalletConnect session is terminated and not stored. Your wallet app does not need to remain connected.
What if my wallet doesn't support WalletConnect v2?
WalletConnect v1 has been deprecated. If your wallet only supports v1, you can connect to Wag3s by pasting the public address directly — the result is identical since Wag3s only uses the address for on-chain data ingest.
Can I connect a hardware wallet (Ledger, Trezor) via WalletConnect?
Yes, if your hardware wallet is connected through a WalletConnect-compatible app (e.g. Ledger Live with WalletConnect enabled, or a software wallet paired with a hardware signer). Alternatively, you can paste the hardware wallet's public address directly into Wag3s — no WalletConnect session required.
Other connectors that pair with this one.
Connect WalletConnect in minutes
Free during Alpha. No credit card. Native sync, audit trail, no spreadsheets.