• This wallet does all the actual buying and selling on-chain.
• It must hold the Token A and Token B balances you want the bot to trade with.
• Use a unique, dedicated wallet for each bot instance trading on the same chain. Sharing a trading wallet across two bots on the same chain will cause conflicts.
• You may reuse the same Private Key Grid across bots on different chains, but a separate wallet per instance is always the safest approach.

• This wallet holds your license. The bot validates your license against this wallet's address every time it starts.
• This wallet also acts as the gas top-up source. When the trading wallet's gas balance drops below your configured threshold, the bot automatically transfers gas from this wallet to the trading wallet.
• The same Private Key 2 can be shared across all your bot instances — one license wallet serves all bots.
• Keep a healthy gas balance in this wallet at all times. If it runs dry, the auto top-up system fails and your trading wallet may stall.

• The bottom of your trading range. The bot will not place buy orders below this price.
• "Price" means the ratio of Token B per Token A — not a dollar amount, unless Token B is a stablecoin.
• Using a stablecoin as Token B (USDC, USDT, DAI) makes this behave like a normal dollar price and is strongly recommended for beginners.
• If the current market price is below this value when you start, the bot will have no active grids until price enters your range.
• For decimal prices, always include the leading zero: 0.0045 not .0045.

• The top of your trading range. The bot will not place sell orders above this price.
• Together with Low Price this defines the band the bot operates in. Make it wide enough to capture normal price movement, but not so wide that grids are too far apart to trigger regularly.
• Example: Low 60000, High 70000 → bot only trades WBTC between $60K–$70K.

• How many grid levels you want across your range. Treated as a suggestion — the bot calculates spacing and may adjust slightly.
• More grids = smaller profit per trade but more frequent trades. Fewer grids = larger profit per trade but less frequent.
• The bot shows you the calculated options and asks you to confirm before committing on first run.

• The minimum percentage price movement between two adjacent grid levels that you actually want enforced.
• Acts as a floor override — if the spacing calculated from your grid count is smaller than this, the bot offers to use this value instead.
• On first run the bot presents both options and lets you choose. Larger spacing = more profit per trade but fewer trades.

• The contract address of the native gas token for the chain you are trading on.
• On most chains (Ethereum, Polygon, Base, Arbitrum) this should be null.
• On BSC and PulseChain, you can use the Wrapped Gas token address here.
• The full list is in the Help tab under Known Gas Tokens (TXT).

• The contract address of the first token in your trading pair — the one you are accumulating.
• Example: for WBTC-USDC, Token A is WBTC.
• On V3, do not use the raw native gas token address. Use the wrapped version (WETH instead of ETH).
• Always copy/paste this address — never type it manually.

• The contract address of the second token — typically the stable or quote token.
• Example: for WBTC-USDC, Token B is USDC.
• The bot always calculates price as Token B per Token A, regardless of how Dexscreener displays the pair.
• Using a stablecoin as Token B makes price configuration and USD calculations much simpler.

• The contract address of the specific liquidity pool the bot will read prices from and route trades through.
• Must match your Token A, Token B, router version (V2/V3), and chain exactly.
• Best way to find it: paste your token address into Dexscreener and find the pair matching the DEX and version you want.

• Set to true if Token A's price in Token B is a large number (e.g. WBTC priced in USDC = ~65000).
• Set to false if the price is a small decimal (e.g. a low-cap token = ~0.0048).
• This affects how the bot rounds and formats price comparisons internally. Getting it wrong causes grid level mismatch issues.

• The hard ceiling on gas price the bot will pay per transaction. If network gas exceeds this, the bot skips the trade rather than overpay.
• Too low and the bot stops trading during gas spikes. Too high and you risk paying excessive fees.

• The priority fee added on top of base gas to get transactions included faster.
• Safe starting point: half the current chain Gwei. On Polygon, use a minimum of 25 Gwei.
• Higher = faster but costs more. Lower = saves fees but transactions may be slower.

• The minimum gas balance the trading wallet must maintain. If gas drops below this, the bot pauses trading and waits for a top-up from the Backup Wallet.
• Set this to cover several transactions worth of gas so the bot has a real buffer.

• A small additional buffer above the Low Gas Warning to handle edge cases where gas spikes between the warning check and the top-up arriving.
• Can be small — just enough to cover 1–2 extra transactions.

• When the trading wallet's gas drops to this level, the bot automatically requests a transfer from the Backup Wallet.
• Recommended: set to roughly half your Low Gas Token Balance Warning. This gives the bot time to receive the top-up before hitting the hard floor.

• How much gas the bot requests from the Backup Wallet on each top-up event.
• Recommended: set this equal to your Low Gas Token Balance value so the wallet refills to a healthy level each time.
• The Backup Wallet must have this amount available or the top-up will fail silently.

• As the bot profits, it accumulates unallocated Token A. Once this reaches the amount you set here, the bot automatically redistributes it back into the active grids.
• Compounding grows your position size over time, increasing the value of each grid level and therefore profit per trade.
• Lower values compound more often in smaller amounts. Higher values compound less often but add more at once.

• The contract address of the DEX router the bot sends swap transactions to.
• Must match the version (V2 or V3) and the chain you are trading on.
• A reference list is in the Help tab under Known Dex Routers (TXT).
• Using the wrong router address is one of the most common setup mistakes — verify carefully.

• When the bot distributes profits (the "sent" portion), they go to this wallet.
• Can be any wallet — your main personal wallet, a cold wallet, or a separate savings address.
• Triple-check this address. Sending to the wrong address is permanent and unrecoverable.

• When a profit distribution occurs, this is the percentage the bot retains for compounding back into the grids.
• Enter as a whole number. Example: 50 = bot keeps 50%, sends 50% to Profit Wallet.
• 100 = all profit stays in the bot for compounding. 0 = all profit sent to your wallet immediately.

• How often the bot's trading loop polls the chain for current price, balances, and grid status.
• Lower = more responsive but more RPC calls. Higher = less responsive but lighter on network load.
• 10–30 seconds is typical for most pairs. Adjust based on pair volatility and RPC capacity.

• For V2 pairs: the maximum price deviation you will accept on a swap. If execution slips more than this, the transaction reverts.
• For V3 pairs: each pool has its own fee tier built-in. You can set slippage to 0 for V3.
• V2 recommendation: 0.5–1% for stable pairs, 1–3% for volatile or low-liquidity pairs.

• The wrapped version of the chain's native gas token (WETH on Ethereum, WBNB on BSC, WPLS on PulseChain).
• Required for V3 on all chains.
• For V2 on chains where raw gas cannot be used in smart contracts (Ethereum, Polygon, Base, Arbitrum): enter the wrapped address.
• For V2 on chains that support raw gas in swaps (BSC, PulseChain): enter NA in capitals.

• A short string used to build the Dexscreener chart URL. Examples: bsc, ethereum, polygon, pulsechain.
• When you click the Dexscreener button on a bot card, the app opens dexscreener.com/{chainId}/{pairAddress} in your browser.
• Valid chain IDs are listed in the Known Gas Tokens file in the Help tab.

The USD value of all funds when the bot was first started, calculated from the first Start block in the calculation log. Written once and never changed — except when a compound occurs, at which point the newly added funds are added to the baseline.

The real-time USD value of all Token A and Token B currently held across the grids, calculated using the live on-chain price fetched directly from LP reserves via the blockchain.

Current Value minus Initial Balance. Your unrealized gain or loss — the difference between what you put in and what the bot currently holds. Does not include profits already sent to your Profit Wallet.

The total Token A sent to your Profit Wallet over the entire lifetime of this bot, expressed as a percentage of initial balance. This is your realized return — money that has actually left the bot and reached your wallet.

The Lifetime ROI annualized based on actual runtime. If the bot has been live for 30 days and achieved 5% ROI, the APY would be approximately 61% compounded annually. This is the most meaningful long-term performance indicator.

Based only on profit distributions in the last 24 hours, projected to a full year. This reflects very recent performance and can fluctuate significantly. A quiet market day shows a lower number; an active day shows higher. Use Performance APY for the true picture.

Your private keys and RPC URL. The most sensitive file in the entire application. Never share it, never commit it to version control, never send it to anyone. If this file is compromised, your wallets are compromised.

All configuration values — price range, grid count, token addresses, gas settings, profit settings. The bot reads this on every start.

The full saved state of the grid — every level, the Token A and Token B balance at each level, and the current position. This is what the bot loads when you answer y to the "load saved state" question. Do not edit while the bot is running.

A timestamped plain-text record of every meaningful event: bot start/stop, every trade, every profit distribution, every compound. The best file to review when you want to understand what the bot has been doing. Also what the Charts window reads to build profit graphs.

Records errors during trading — failed transactions, RPC timeouts, unexpected responses. Check this first if the bot appears to have stopped trading unexpectedly.

Detailed balance snapshots at Start, Updated (compound), and Distro events. Records Token A and Token B balances plus price at each event. This is what the UI reads to calculate ROI, and APY.

Stores the running USD value calculations — initial investment, current value, unrealized profit, and the stablecoin address used for conversion. The UI reads this to show dollar amounts on the bot card. See Section 11 for setup.

A simple file recording whether the bot is RUNNING or STOPPED. The UI reads this to show the correct status on the bot card.