Wallet Signature Format Compatibility Tester

WHAT IT DOES

This tool tests wallet signature format compatibility by analyzing contract support for EIP-191 (personal sign), EIP-712 (typed data), and eth_sign (legacy) signature formats. It performs a comprehensive suite of read-only checks against a target contract to verify that it correctly handles signatures from various wallet formats. The tool checks for wallet connection status, contract deployment verification, chain ID support, and format-specific verification patterns. Results are presented as a detailed test report with pass/fail/warn statuses for each format, along with signature-format-specific recommendations. This is essential for developers implementing wallet authentication, auditors verifying signature verification logic, and teams ensuring dApp compatibility with different wallet signing standards.

HOW TO USE

Connect your wallet (read-only, no transaction required) and select the target network. Enter the contract name and address that implements signature verification, select the signature format to test (EIP-191, EIP-712, eth_sign, or All Formats), and set the lookback blocks for signature analysis. Click "test signature compatibility" and the tool will verify the contract, analyze its bytecode and ABI for signature format 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 format compatibility gaps, verify signature verification logic, and ensure your contract supports the signature formats your users need.

TECHNICAL MECHANISM

The analyzer uses ethers.js v5.7.2 and the BGWallet bridge to perform a multi-stage signature format 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 signature format patterns—specifically looking for EIP-191 prefix handling (0x19 prefixed messages), EIP-712 structured data verification (domain separator and typed data hashing), and eth_sign legacy verification patterns. The tool also scans historical logs using eth_getLogs across the specified block range to identify signature verification events. For each format, the tool checks for the presence of the appropriate verification logic: ecrecover implementation, hash construction patterns (keccak256), and specific format indicators. Results are compiled into a structured report with detailed diagnostic information and format-specific recommendations.

WHAT IT CANNOT SEE

This tool cannot actually test signature generation from different wallets—it performs analysis and verification only. It is limited to the specific wallet instance accessible via BGWallet. 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 signature data; unverified contracts or incomplete ABIs may produce incomplete results. It cannot analyze contracts that are not verified or have opaque implementation details where signature format patterns are not clearly distinguishable. The tool cannot test signature format 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 signature verification logic correctly implements the signature format specifications without manual review and actual signing tests with different wallets.

PLEASE NOTE

This is a read‑only analytics tool—it never submits transactions or initiates wallet signing operations. It is designed for EVM‑compatible chains and works best with contracts that implement standard signature verification patterns. The test results are for informational and audit purposes only and should not be considered a comprehensive security audit. Always manually test signature verification with actual wallet signatures before deploying to production. The tool's pattern detection is heuristic and may miss custom signature format implementations or wallet-specific features. The eth_sign format is considered legacy and has security considerations—review its use carefully.