REQUIRED HELPERS, defined once at the top of the script:

WHAT IT DOES

This tool detects and validates the presence and quality of required helper functions at the top of scripts on the page. It specifically identifies whether scripts define necessary wallet helper functions (connect, disconnect, switchNetwork, subscribe, getState, isConnected, getAddress, getChainId) in a consistent, reusable way. For each required helper, it shows the function name, expected parameters, return type, and whether it follows best practices (defined once, not duplicated, properly documented). It identifies duplicate helper definitions (defined multiple times across scripts), missing required helpers (functions that should be defined but aren't), and helpers defined with incorrect signatures (wrong number of parameters, missing documentation). A search filter lets you find specific helper functions by name or status. You can copy helper detection details to your clipboard. The inspector mode lets you click any script-related element on the page to see a detailed report of the helper function detection results. This tool helps developers ensure that wallet helper functions are properly defined once at the top of scripts and meet the required API standards, preventing duplication, missing functionality, and signature mismatches.

WHERE IT RUNS

The script runs on every website and web application you visit. It scans all script tags on the page, both inline and external, for helper function definitions. It works regardless of framework—React, Vue, Angular, Svelte, or plain HTML—and detects helper functions defined using function declarations, function expressions, arrow functions, or async function syntax.

HOW TO USE

Upon installation, a floating panel appears with the tool interface. The panel shows a summary with total helpers, defined count, missing count, and duplicate count. Click "Scan" to analyze the current page for helper function definitions. The panel shows each required helper with its name, status badge (OK, Issues, Missing, Duplicate), parameter count, return type, async indicator, documentation badge, and any issues found. If a helper is defined, the panel shows its body preview and source location. Use the search box to filter by helper name or status. Click "Copy" on any entry to copy its details to your clipboard. Click "Copy Report" to copy the complete helper validation report. Click "Inspect" to enter inspector mode, then click any script-related element on the page to see a detailed report of the helper function detection results. Click "Inspect" again or press Escape to exit inspector mode.

TECHNICAL MECHANISM: HELPER FUNCTION DETECTION WITH PATTERN MATCHING

This tool uses a comprehensive pattern-matching engine to detect helper function definitions. It scans all script tags using multiple regex patterns that match common function definition styles: function declarations (function name() {}), function expressions (const name = function() {}), arrow functions (const name = () => {}), and async functions (async function name() {}). For each detected helper, it extracts the function name, parameters, and body. It then validates each definition against the expected API spec, checking parameter count, return type, and documentation presence. The tool tracks duplicates by function name across all scripts and reports any helper defined more than once. The detection is non-invasive and does not modify any page objects or code.

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, helper functions, or browsing habits is ever transmitted or stored externally. The tool accesses page scripts solely for the purpose of helper detection and validation, and does not modify or persist any page data. This tool is designed for debugging and development purposes only.