Airdrop Gas Rebate Claim Tool

WHAT IT DOES

This tool enables users to claim gas rebate tokens from airdrop distributors that reward users for gas spent on specific transactions or activities. You provide the gas rebate contract address and optionally a beneficiary address, and the tool reads your rebate details—total rebate amount, already claimed amount, eligibility status, and gas usage recorded. It then executes a claim transaction to transfer your available rebate to your wallet. The tool supports multiple claim function signatures including claim(), claim(bytes32[] proof, uint256 amount), claimGasRebate(uint256 gasUsed, bytes32[] proof), and claim(address beneficiary, uint256 amount), accommodating various rebate distributor implementations.

HOW TO USE

Connect your EVM wallet to the network where the rebate contract is deployed. Enter the gas rebate contract address. Optionally specify a beneficiary address if you are claiming on behalf of someone else (leave blank to use your connected wallet). Select the token decimals (default 18) and choose the claim function signature that matches your contract. If using a proof-based claim, paste your Merkle proof as hex strings (one per line or comma-separated). If using claimWithGasProof, also enter the gas used amount. The tool will automatically load your rebate details: rebate amount, claimed amount, eligibility status, and recorded gas usage. Review the displayed information. If eligible and you have unclaimed rebate, click "Claim Gas Rebate" to submit the claim transaction. The tool will claim the full available rebate amount and display the transaction result with gas cost.

TECHNICAL MECHANISM

The tool uses ethers.js to interact with the rebate contract via the connected provider. It dynamically probes for common rebate view functions including rebateAmount(address), claimed(address), claimable(address), isEligible(address), gasUsed(address), and token() to gather comprehensive rebate data. The claimable amount is computed by the contract itself based on gas usage records and eligibility criteria. For claiming, the tool encodes the appropriate function call based on the selected signature: claim() for simple claims, claim(bytes32[] proof, uint256 amount) for proof-based claims, claimGasRebate(uint256 gasUsed, bytes32[] proof) for gas-proof claims, or claim(address beneficiary, uint256 amount) for multi-beneficiary contracts. The tool parses proof inputs by splitting on newlines and commas, filtering for valid 32-byte hex strings. It uses the signer's gas estimation and reports effectiveGasPrice from the receipt for accurate cost reporting (PLAYBOOK-C §5 rule 5). All transactions are submitted sequentially and waited for confirmation.

WHAT IT CANNOT SEE

This tool cannot verify off-chain gas usage or transaction history beyond what the contract accepts as proof—it trusts the contract's on-chain records. It cannot detect if the user is eligible for gas rebates from other programs beyond the provided contract. It cannot recover from a failed claim due to insufficient gas or network issues—you must retry manually. It cannot claim on behalf of others without their private key or signature, even when using claim(address) functions, because the transaction must be signed by the caller. It cannot guarantee that the rebate amount is fair or accurately calculated—it only reflects what the contract reports. It cannot adjust rebate amounts or modify eligibility criteria—these are fixed by the contract deployment. It also cannot detect if the rebate contract uses a different calculation method than expected; the displayed amounts are what the contract returns.

PLEASE NOTE

EVM chains only. This tool works with any EVM-compatible network that supports standard gas rebate distributor patterns. Only execute claims if you are the intended beneficiary or authorized to claim on behalf of the beneficiary. Ensure you have sufficient native currency for gas fees. The tool claims the full available rebate amount—if you want to claim a partial amount, use the appropriate claim function with a specified amount. Always test on testnet first with small amounts. The tool does not store any data; all state is read fresh from the blockchain. Gas costs vary by network and contract complexity. For contracts with custom rebate logic not covered by the standard view functions, the tool may not display all details correctly, but the claim function should still work if the signature matches.