app. If you find yourself writing "async connect() { ... request({ method:"

WHAT IT DOES

This tool scans the page to detect and display all wallet implementation patterns including async connect methods, request({ method: ... }) calls, and wallet RPC request patterns. It identifies common wallet implementation patterns including connect() async functions, request() calls with eth_requestAccounts, eth_chainId, personal_sign, eth_sendTransaction, eth_signTypedData, wallet_switchEthereumChain, wallet_addEthereumChain, and other wallet RPC methods. For each detected implementation, it shows the method signature, request parameters, and RPC method names. It detects wallet provider implementations in the page code, both in inline scripts and external script files, as well as in HTML attributes. A search filter lets you find specific implementation patterns by method name, RPC call, or script name. You can copy implementation details to your clipboard. The inspector mode lets you click any wallet-related element on the page to see a report of all detected wallet implementation patterns. This tool is essential for developers debugging wallet implementation issues, understanding wallet integration patterns, and detecting custom wallet RPC implementations.

WHERE IT RUNS

The script runs on every website and web application you visit. It works with all wallet implementations regardless of framework—React, Vue, Angular, Svelte, or plain HTML—and scans both inline script tags and external script sources for implementation patterns. It also checks HTML attributes for inline event handlers containing wallet code.

HOW TO USE

Upon installation, a floating panel appears with the tool interface. Click "Scan" to analyze the current page for wallet implementation patterns. The panel shows a summary of all detected patterns including the number of scripts with async connect, request(), and RPC methods. Each script entry displays the script name (or inline source), the number of patterns found, and the actual code snippets with their type badges (connect, request, rpc, function). Use the search box to filter by pattern type, RPC method name, or script name. Click "Copy" on any entry to copy its implementation details to your clipboard. Click "Copy All" to copy all detected patterns. Click "Inspect" to enter inspector mode, then click any wallet-related element on the page to see a report of all detected wallet implementation patterns. Click "Inspect" again or press Escape to exit inspector mode.

TECHNICAL MECHANISM: PATTERN-BASED SCRIPT SCANNING WITH RPC METHOD EXTRACTION

This tool performs comprehensive script scanning using pattern-based detection. It selects all script tags on the page, reads their text content (or fetches external scripts when accessible), and applies regex patterns to identify wallet implementation patterns. The detection patterns include: async connect function definitions, request({ method: ... }) calls, named RPC methods (eth_requestAccounts, eth_chainId, personal_sign, wallet_switchEthereumChain, etc.), and connect function declarations. Each pattern is categorized by type (connect, request, rpc, function) and displayed with surrounding code context. The tool also checks the HTML source for patterns in event handlers and inline code. RPC method names are extracted from request calls and displayed as badges. All detection is performed locally and does not modify any page objects.

THE PANEL

The panel is fully draggable and remembers its position per website using GM_setValue. It automatically snaps to the nearest screen edge when released for a clean workspace. Click the collapse button to minimize it to a small floating bubble that takes minimal space. Click the bubble to expand the panel back. The panel can be resized by dragging any edge or corner. Press the Escape key to close the panel temporarily, and click the extension icon to reopen it.

PLEASE NOTE

This script requires the free BotGentz extension to function. As websites frequently update their structure and wallet integration patterns, scripts may need occasional updates to maintain compatibility. All data processing happens locally in your browser—no information about your pages, implementations, or browsing habits is ever transmitted or stored externally. The tool accesses page scripts solely for the purpose of pattern detection and analysis, and does not modify or persist any page data. This tool is designed for debugging and development purposes only.