Stop-Loss Order Executor

WHAT IT DOES

Stop-Loss Order Executor connects to any EVM-based stop-loss order contract and enables you to execute sells when the price falls below your specified stop level. The tool reads comprehensive contract state including token balance, price feed/oracle data, stop price level, order status, current price, sell amount, token address, user address, current block timestamp, execution history, order type (market or limit), and slippage parameters. It then displays the current price, stop price, token balance, sell amount, order status, and execution status. When the price drops below the stop level and the order is triggered, the tool enables a one-click sell execution transaction. The tool handles multiple execution function signatures (executeStopLoss, triggerStopLoss, performOrderExecution) and automatically detects the correct function to call. After submission, the tool displays the transaction hash and refreshes the contract data to show the updated execution status. This is ideal for risk management, protecting profits, and limiting downside exposure in volatile markets.

HOW TO USE

Connect your Web3 wallet (MetaMask, WalletConnect, or any EIP-1193 provider). Select the correct network for your stop-loss contract — the tool supports Ethereum, Polygon, Arbitrum, Optimism, Base, Avalanche C-Chain, and BNB Chain. Paste your stop-loss order contract address into the input field. The tool reads the contract using a default ABI that covers standard stop-loss functions, but you can paste a custom ABI if your contract uses non-standard naming. Review the displayed data carefully: token address, token balance, current price from the oracle, your stop price level, sell amount, order type (Market or Limit), slippage parameters, order status (Active, Triggered, Executed, Cancelled), and execution status. The status indicator will show "Active" when the order is monitoring, "Executed" after sell execution, "Pending" while processing, or "Ready" when conditions are met. When the price has dropped below the stop level and the order is triggered, the "Execute stop-loss" button becomes enabled. Click it to submit the execution transaction — the tool will show a confirmation dialog with all details, submit the transaction, and wait for confirmation. After successful execution, the contract data refreshes automatically to show the updated execution status.

THE REAL MECHANISM

This tool does not assume a single execution interface — it adapts to the contract's actual implementation. It first detects the correct execution function by testing common names (executeStopLoss, triggerStopLoss, performOrderExecution) through static calls, falling back to the user-provided name if none are found. For stop-loss data, the tool reads currentPrice() from the oracle/feed, stopPrice() to show your trigger level, orderStatus() to determine if the order has been triggered (0=active, 1=triggered, 2=executed, 3=cancelled), tokenBalance() to check available tokens, sellAmount() to show how many tokens will be sold, orderType() to display market or limit, slippage() to show tolerance, and executionStatus() to check if already executed (0=active, 1=executed, 2=pending, 3=ready). The tool enables the execution button only when the order status is triggered and the execution hasn't already happened. When you execute, the tool calls the contract's execution function, which validates that the stop condition is still met and performs the sell. All transaction parameters are estimated using eth_estimateGas and sent with the wallet's preferred gas strategy. The tool monitors the transaction receipt and extracts the effectiveGasPrice to display actual gas cost, not the cap.

WHAT IT CANNOT SEE

Stop-Loss Order Executor cannot verify that the price feed is accurate, reliable, or free from manipulation. It cannot detect if the oracle has been compromised, delayed, or is returning incorrect data. It cannot guarantee that the order will execute at the exact stop price due to slippage, market volatility, or execution delays. It cannot ensure that the stop-loss contract has not been upgraded, modified, or paused by its owner. It cannot prevent the user from canceling or modifying the order. It cannot recover funds if the execution fails due to contract bugs, out-of-gas errors, or network conditions. It cannot verify that the user has sufficient tokens to sell or that the balance is accurately reported. It cannot detect if the contract is malicious, contains hidden fee structures, or has been deployed by an untrusted party. It cannot validate that the price comparison is correctly processed or that the slippage parameters are applied correctly. It cannot predict market movements, price gaps, flash crashes, or extreme volatility events. It cannot guarantee order execution during periods of high market stress or when the oracle is slow to update.

PLEASE NOTE — EVM CHAINS ONLY

This tool works exclusively with EVM-compatible blockchains. Non-EVM chains are not supported. The tool does not deploy contracts, manage private keys, or sign anything outside the connected wallet's secure environment. It is a read-and-execute interface that relies entirely on the stop-loss contract's implementation and the oracle data feed defined therein. Always verify the stop-loss contract address and stop price parameters directly on-chain before executing.