moves, BigNumber goes away. Do not mix them.

WHAT IT DOES

This tool detects and validates BigNumber usage on the page, specifically identifying whether the page uses ethers v5 BigNumber (which is deprecated and removed in v6) or native BigInt. It shows each detected BigNumber usage with its context, whether it's from ethers v5 (via window.BigNumber or ethers.BigNumber), and whether the code should be migrated to BigInt. It identifies common BigNumber patterns including BigNumber.from(), .toString(), .toNumber(), arithmetic operations (add, sub, mul, div), comparisons (eq, gt, lt, gte, lte), and formatting. For each detected pattern, it provides the specific BigInt equivalent (e.g., BigNumber.from() → BigInt() or Number(), .add() → +, .eq() → ===). A search filter lets you find specific BigNumber operations by method name or context. You can copy BigNumber detection details to your clipboard. The inspector mode lets you click any BigNumber-related element on the page to see a detailed report of detected BigNumber usage and migration recommendations. This tool is essential for developers migrating from ethers v5 to v6, helping identify all BigNumber usage that needs to be replaced with BigInt.

WHERE IT RUNS

The script runs on every website and web application you visit. It works with ethers.js loaded from any source—CDN, npm bundles, or local scripts. It scans both global BigNumber objects and script content for usage patterns, regardless of framework—React, Vue, Angular, Svelte, or plain HTML.

HOW TO USE

Upon installation, a floating panel appears with the tool interface. The panel shows a summary with BigNumber presence status and pattern count. Click "Scan" to analyze the current page for BigNumber usage. The panel shows three sections: Summary (overall status and counts), Sources (window.BigNumber or ethers.BigNumber with their methods), and Patterns (specific BigNumber usage patterns with occurrence counts, code contexts, and migration equivalents). Each pattern entry shows the pattern name, number of occurrences, code context snippets, and the BigInt equivalent. Use the search box to filter by pattern name, method, or migration equivalent. Click "Copy" on any entry to copy its details to your clipboard. Click "Copy Report" to copy the complete BigNumber detection report. Click "Inspect" to enter inspector mode, then click any BigNumber-related element on the page to see a detailed report of detected usage and recommendations. Click "Inspect" again or press Escape to exit inspector mode.

TECHNICAL MECHANISM: BIG NUMBER USAGE DETECTION WITH PATTERN MATCHING

This tool uses a multi-layered detection approach to identify BigNumber usage. It checks for global BigNumber objects (window.BigNumber and ethers.BigNumber) and extracts their available methods. It then scans all script tags on the page for usage patterns including BigNumber.from(), .toNumber(), .toString(), arithmetic operations (.add(), .sub(), .mul(), .div()), and comparisons (.eq(), .gt(), .lt(), .gte(), .lte()). For each detected pattern, it extracts surrounding code context and maps the BigNumber method to its BigInt equivalent. The detection is non-invasive and reads only property names and script text without modifying any 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, BigNumber usage, or browsing habits is ever transmitted or stored externally. The tool accesses page content solely for the purpose of BigNumber detection and migration analysis, and does not modify or persist any page data. This tool is designed for debugging and development purposes only. BigNumber is deprecated in ethers v6 and must be migrated to BigInt for compatibility.