Arbitrum One GMX Token Batch Sender

WHAT IT DOES

This tool enables the batch distribution of GMX (the native utility and governance token of the GMX decentralized exchange) to multiple recipient addresses in a single atomic transaction on Arbitrum One. It connects to your wallet via BGWallet, reads the GMX contract bytecode and verified source, fetches your current balance and allowance, and constructs a batched transfer that sends GMX tokens to each address with specified amounts. The batch executes through the BotGentz sender contract, ensuring all recipients receive their tokens simultaneously or the entire transaction reverts. This is ideal for GMX ecosystem rewards, liquidity provider incentives, contributor payments, community grants, or any scenario requiring efficient multi-recipient distribution of the core token powering the GMX protocol.

HOW TO USE

1. Connect your wallet using the "Connect" button (BGWallet integration).

2. Ensure you are on Arbitrum One (chain ID 42161) — the tool will prompt you to switch if needed.

3. Enter the GMX token contract address (defaults to the official GMX token: 0xfc5A1A6EB076a2C7aD06eD22C90d7E710E35ad0a).

4. Click "Load token details" to automatically detect the token's symbol and decimals (18 on Arbitrum).

5. Paste your recipient list — one address and GMX amount per line, separated by space or comma.

6. Click "Parse & preview" to validate addresses and see a summary table.

7. Review the sender information: your address, GMX balance, required total (including network fee), current allowance, and the batch sender contract details.

8. If allowance is insufficient, click "Approve" to authorize the sender contract to spend your GMX tokens.

9. Click "Send batch" to execute the atomic transfer. The progress bar will show transaction status.

TECHNICAL MECHANISM

The tool leverages the BotGentz multisender contract (BULKSEND registry) which implements a batched ERC-20 transfer function. It dynamically fetches the current fee and owner address from the contract (never hardcoding stale values). The approval process grants exactly the required total amount — not an unlimited allowance — enhancing security. The contract uses the `sendERC20` method, which takes arrays of recipient addresses and amounts, processes each transfer in a loop, and ensures all succeed before finalizing. The transaction includes the protocol fee as `msg.value`. The tool automatically detects GMX's 18 decimals on Arbitrum (standard ERC-20 precision), ensuring precise amount parsing and display. It validates total required funds against the sender's balance before submission, catching underfunding early. Arbitrum L2 gas mechanics are handled through the provider, with the tool estimating gas using the contract's `estimateGas` function and applying a 20% safety margin.

WHAT IT CANNOT SEE

This tool cannot guarantee recipient addresses are valid beyond basic Ethereum address format validation (0x + 40 hex characters). It does not verify if recipients are contracts, if they can receive GMX, or if they have been blacklisted by the GMX contract. The tool cannot recover from a failed batch — due to the atomic nature of the transaction, if any single transfer fails (e.g., blacklisted recipient, insufficient gas, contract revert), the entire batch reverts and no GMX is sent to anyone. It cannot send to zero addresses or self, or exceed the block gas limit (which limits batch size). The tool does not simulate the transaction beforehand, so unexpected reverts may occur during execution. It relies entirely on the GMX contract behaving as expected — any changes to the GMX contract's logic (e.g., upgrades, pausing) could cause the batch to fail. GMX's 18 decimal precision means amounts must be entered with appropriate precision — amounts smaller than 0.000000000000000001 GMX cannot be represented. The tool cannot detect if recipients are blacklisted by the GMX contract or if they have custom hooks that would reject transfers. It cannot account for GMX-specific mechanics such as staking, vesting, or esGMX (escrowed GMX) which may affect token value or transferability. The tool cannot guarantee that recipients will accept GMX if they have custom hooks. Arbitrum-specific considerations include sequencer dependencies and varying gas prices that may affect transaction propagation.

PLEASE NOTE

This tool is designed exclusively for Arbitrum One (chain ID 42161). It reads the chain ID and uses the BULKSEND registry to locate the appropriate sender contract (the registry includes Arbitrum at 0x956D760F8665358Ea1a9F11b82913020e5479376). The sender contract charges a fee in ETH (native gas token on Arbitrum), which is displayed before signing. Always review the fee, contract address, and owner before approving or sending. This tool is provided as-is — verify all transactions carefully, especially when dealing with GMX which has a complex tokenomics model including staking, vesting, and governance mechanisms. Transactions on Arbitrum may have different confirmation times and gas costs compared to Ethereum L1. Always ensure you are using the correct GMX contract address for Arbitrum One.