Unknown author · Functionality & UI
5 items
Locks Binance, Bybit, Bitget, and Gate futures leverage so it can never be raised above your initial setting. Leverage Limiter is a self-control (commitment device) extension for crypto futures traders. Set your maximum leverage once — it can never be raised above that limit again, on any of the supported exchanges. WHY THIS EXISTS Impulsive leverage increases are one of the fastest ways to blow up a futures account. This extension adds friction between you and that decision by locking your leverage ceiling at the browser level. SUPPORTED EXCHANGES - Binance Futures - Bybit Futures - Bitget Futures - Gate Futures (gate.com and gate.io) HOW IT WORKS 1. Click the extension icon and set your maximum leverage (e.g. 10x). 2. This limit applies across all four supported exchanges. 3. If you try to set leverage above your limit on any exchange: • The slider/input automatically resets to your maximum • The confirm button is disabled • The underlying network request is blocked as a second layer of protection 4. You can only lower your limit afterward, never raise it, directly from the popup. TWO LAYERS OF PROTECTION - UI layer: watches leverage dialogs on the page and corrects sliders, inputs, and confirm buttons. - Network layer: inspects outgoing leverage-related requests and blocks any that exceed your locked maximum, even if the UI layer is bypassed. MULTI-LANGUAGE SUPPORT Available in Korean, English, Japanese, and Chinese. The popup and on-page warning toast follow your selected language. PRIVACY This extension does not collect, transmit, or sell any personal or trading data. Your leverage limit is stored locally using chrome.storage and never leaves your browser. No analytics, no external servers. IMPORTANT LIMITATIONS This is a friction tool, not an unbreakable lock. It can be bypassed by disabling/removing the extension, editing extension storage via DevTools, or trading through another device, browser profile, or API key. It is designed to stop impulsive in-browser leverage changes, not to provide absolute enforcement. Feedback and exchange-specific bug reports are welcome — exchanges frequently update their UI and API field names.
rating_count is the Chrome Web Store ratings count, not a written-review count.