ENS Text Record Batch Setter

WHAT IT DOES

The ENS Text Record Batch Setter enables efficient batch configuration of ENS text records for domain names. It reads state from ENS registry and resolver contracts including ENS name, resolver address, text record keys and values, record status, record history, platform fees, ENS node, owner address, resolver version, and supported record keys. Users can set text records using multiple methods: batchSetText for standard batch setting, setTextRecords with default value, updateRecords with clear option, or configureENSRecords with full parameter control. The tool displays a preview of all records to be set, shows the total fee, and provides batch status updates. The resolver contract address is user-provided and never hardcoded.

HOW TO USE

Connect your Web3 wallet and select the target network. The tool automatically detects the BotGentz bulk sender contract for the current chain via the BULKSEND registry. Enter the ENS name (e.g., example.eth) and the resolver contract address. Enter text records in the format key,value per line (e.g., avatar,ipfs://..., description,My profile). Select the batch method, optionally set a default value, check "Approve token spending" if needed, "Force" to bypass checks, or "Clear existing records" to remove existing records before setting. Click "Preview records" to parse entries, calculate total fee, and display a preview of all key-value pairs. Review the preview carefully—batch setting updates multiple ENS text records in a single transaction. Click "Set batch records" to execute the batch operation. Transaction status, gas costs, and confirmation are displayed upon completion.

MECHANICAL ADVANTAGE: AUTOMATED REGISTRY LOOKUP WITH LIVE FEE FETCHING

Unlike hardcoded ENS tools that require manual contract address entry, this tool automatically looks up the BotGentz sender contract address from the BULKSEND registry using the current chain ID. It fetches the fee live from the sender contract on every submission—never hardcoding the fee, as it is settable by the owner and a stale value would cause revert due to underpayment. The tool calculates totals per sender and checks native balance before sending, avoiding partial failures. Records are parsed line-by-line with validation, and the batch preview shows the full list with keys and values. Gas estimation is approximated based on batch size, and the tool uses receipt.effectiveGasPrice post-transaction for accurate cost reporting rather than relying on pre-EIP-1559 gasPrice caps. The fee, owner, and sender contract address are displayed prominently before signing. ENS namehashing is handled automatically using ethers.utils.namehash.

WHAT IT CANNOT SEE

This tool cannot verify that the ENS registry contract or resolver contract is legitimate or has not been compromised. It cannot detect if the text record parameters have been manipulated or if the contracts have been upgraded or modified. Batch setting may not execute at optimal gas price due to network conditions or succeed if the contract is paused or frozen. The tool cannot recover funds if execution fails due to contract bugs or insufficient approval. It cannot verify that text record parameters are valid, predict gas prices during congestion, or detect if the batch setting has been front-run. The tool cannot ensure that all records will be set correctly, provide legal or identity advice, guarantee that the records will be resolvable, verify off-chain ENS data, ensure that all conditions for setting are met, or track record status outside of the tool. ENS records are only as reliable as the resolver contract—verify the resolver address independently.

PLEASE NOTE

This tool operates on EVM-compatible chains only. It uses shared BotGentz sender contracts from the BULKSEND registry—verified addresses are included for supported chains. Always verify the displayed sender contract address, owner, and fee before submitting. The tool does not automatically approve spending—you must explicitly check "Approve token spending" if the resolver contract requires approval. Gas costs vary by network conditions and record count; the tool estimates but cannot guarantee optimal pricing. Ensure you have sufficient native currency to cover both the fee and gas. ENS text records follow standard keys (avatar, description, url, etc.)—check ENS documentation for supported keys. Clearing existing records removes all current text records before setting new ones.