Multi-Wallet Compatibility Test Suite

WHAT IT DOES

This tool tests contract compatibility across multiple wallet providers by analyzing wallet state, signature verification, and authentication patterns. It performs a comprehensive suite of read-only checks against a target contract to verify that it correctly handles signature verification and authentication from various wallet types (MetaMask, WalletConnect, Coinbase Wallet, Trust Wallet, Rainbow, and custom wallets). The tool checks for wallet connection status, contract deployment verification, chain ID support, wallet-type-specific compatibility, signature verification, message encoding, replay protection, and authentication events. Results are presented as a detailed test report with pass/fail/warn statuses for each test, along with wallet-specific compatibility recommendations. This is essential for developers building dApps with broad wallet support, auditors verifying multi-wallet integration, and teams ensuring seamless user experience across different wallet providers.

HOW TO USE

Connect your wallet (read-only, no transaction required) and select the target network. Enter the contract name and address that implements wallet-compatible signature verification, select the wallet type for reference (MetaMask, WalletConnect, Coinbase, Trust, Rainbow, or Custom), and set the lookback blocks for log analysis. Click "test wallet compatibility" and the tool will verify the contract, analyze its bytecode and ABI for wallet-compatible patterns, check wallet connectivity, and run a comprehensive test suite. Results display a summary with pass/fail/warn counts and an overall status, detailed test cards showing each test's outcome with supporting data, and a table of all tests. Use the report to identify compatibility gaps, verify multi-wallet support, and ensure your contract's authentication logic works across different wallet providers.

TECHNICAL MECHANISM

The analyzer uses ethers.js v5.7.2 and the BGWallet bridge to perform a multi-stage wallet compatibility test. First, it calls eth_getCode to verify the contract is deployed and uses block explorer APIs to fetch verification status and source code. The tool then reads the current wallet state via BGWallet, capturing the connected address, chain ID, and connection status. It analyzes the contract bytecode and ABI to detect wallet-compatible patterns—specifically looking for ECDSA signature verification using ecrecover, standard message encoding (EIP-191 and EIP-712 support), replay protection mechanisms (nonce, chainId checks), and wallet authentication event emissions. The tool also scans historical logs using eth_getLogs across the specified block range to identify signature verification events and authentication patterns. Each test in the suite evaluates a specific aspect of wallet compatibility: wallet connection, contract deployment, chain ID support, wallet-type-specific compatibility (based on the selected wallet type), signature verification, message encoding standards, replay protection, and authentication events. Results are compiled into a structured report with detailed diagnostic information and wallet-specific recommendations.

WHAT IT CANNOT SEE

This tool cannot actually test wallet compatibility with all wallet providers—it performs analysis and verification only. It is limited to the specific wallet instance accessible via BGWallet at the time of testing. It cannot access wallet keys or signing capabilities beyond BGWallet's exposed methods. The tool is limited by the RPC provider's rate limits and block range availability for historical log queries. It cannot verify signatures that are not on-chain or have been generated outside the analyzed scope. The analysis relies on the accuracy and completeness of contract verification and wallet state data; unverified contracts or incomplete ABIs may produce incomplete results. It cannot analyze contracts that are not verified or have opaque implementation details where wallet integration is not clearly distinguishable. The tool cannot test wallet compatibility with off-chain systems or external signing devices beyond the contract's on-chain logic. It is limited to the specific wallet instance and contract integrations that are accessible via BGWallet and RPC. The tool cannot guarantee that the contract's wallet integration matches the actual wallet provider's specifications without manual review and testing with multiple wallet providers.

PLEASE NOTE

This is a read‑only analytics tool—it never submits transactions or initiates wallet operations. It is designed for EVM‑compatible chains and works best with contracts that implement standard signature verification patterns compatible with multiple wallets. The test results are for informational and audit purposes only and should not be considered a comprehensive compatibility audit. Always manually test wallet compatibility with multiple wallet providers before deploying to production. The tool's pattern detection is heuristic and may miss custom wallet implementations or provider-specific features.