Vant8 plugs into the wallet you already use — MetaMask, Trust, Coinbase, Rabby, OKX, Brave, or anything that speaks WalletConnect v2. Use it to view balances and sign actions you initiate in the browser — limit orders on CoW Protocol, yield-farming approvals, manual swaps. For unattended auto-trading on chain (Hyperliquid perps, scheduled flows, strategy bots), see the separate Blockchain Wallet — a connected browser wallet cannot sign while you're away.
Wired against each chain's mainnet today. The chain switcher prompts your wallet to add or switch to the network if it isn't already configured.
Browser extensions through the standard EIP-1193 injected interface. Mobile and hardware-via-mobile wallets through WalletConnect v2.
Connect Wallet is exactly what it sounds like — your existing wallet, signing each action when you're there to approve it. Backend bots that need to keep working while you sleep cannot use a browser wallet; for that you use the Blockchain Wallet instead. Vant8 separates the two on purpose.
Your EOA — keys stay in your wallet, full stop. We do not see them, we do not store them. Every transaction signs through your wallet's confirmation prompt. Vant8 builds the call data; your wallet decides whether to sign it.
A connected browser wallet requires you to confirm each transaction. Strategy bots, Hyperliquid perp execution, scheduled DCA, and other on-chain automation cannot prompt you when you are not there — that work runs through the separate Blockchain Wallet, which is built for unattended signing.
If you initiated it from the browser, your wallet signs it. We never take a browser-initiated action and re-route it through a backend signer.
Derived-wallet key material is encrypted with AES-256-GCM. In production deployments, the unwrap path runs through cloud KMS so plaintext keys never live in the application database.
Every transaction creates the signer fresh from your wallet provider at call time — no cached signer reused after a chain switch or reconnect. The right account signs the right call, every time.
Vant8 reads the balances on your connected wallet across the supported chains so the dashboard reflects what you actually hold.
When you place a limit order on the CoW Protocol surface, your connected wallet provides the EIP-712 signature. Each order is consciously authorised by you — that's exactly what the connected EOA is for.
Approvals, deposits, claims, withdrawals, and removeLiquidity calls for yield farming are all signed by your connected wallet. Vant8 never holds your LP tokens or reward tokens.
WalletConnect v2 sessions persist for up to seven days so a refresh, tab switch, or short outage does not force you to reconnect for routine actions.
Native browser flow for desktop wallets; WalletConnect for everything else.
Scan a QR code in the desktop UI or tap a deep-link on mobile — sessions, signing, and chain switching all flow through WalletConnect v2.
Ledger and Trezor can connect through their mobile WalletConnect flow. Direct USB / desktop bridge is not currently supported.
A few operational details worth knowing so you can plan your workflow around what the connected wallet does — and where the wallet you already use handles the rest.
Vant8 connects a single wallet at a time. Switching accounts happens in your wallet provider; multi-account swap-in/swap-out is on the backlog.
Ledger and Trezor connect through their mobile apps over WalletConnect v2. A native desktop USB / WebHID flow isn't shipped yet.
Vant8 connects to six chains and executes on each. Moving funds between them (Arbitrum → Polygon, etc.) happens in the wallet of your choice — we don't operate a bridge.
If a WalletConnect session drops mid-flow, you reconnect and re-initiate. Signatures never get silently retried across sessions — every action is a fresh conscious approval.
Connect a wallet, see your balances, start signing. Vant8 never sees your private keys.