Whitelist Manager

WHAT IT DOES

Whitelist Manager lets you deploy a new whitelist contract or update an existing one with a list of addresses or a merkle root. You provide the addresses to include, and the tool prepares, signs, and broadcasts a transaction to deploy a whitelist contract or update an existing whitelist. The contract follows a simple whitelist pattern, allowing only approved addresses to interact with your dApp or participate in token sales, minting, or other restricted actions. It reads the current network chain ID and gas price from your wallet provider to ensure the transaction is submitted correctly. This is the fastest way to manage access control for your project without writing any Solidity.

HOW TO USE

Connect your wallet using the "Connect" button. Select the target network (Ethereum Mainnet, Sepolia, Polygon, BSC, Arbitrum, Optimism, and testnets are supported). Choose the mode: "Deploy new whitelist" or "Update existing whitelist" (if updating, enter the existing contract address). Add addresses to the list using the input fields. Optionally, provide a merkle root to use instead of the address list for more efficient storage. The review panel shows a preview of the whitelist configuration. Click "Execute" — your wallet will prompt you to confirm the transaction. Once mined, the contract address is displayed, and you can start using the whitelist in your application.

TECHNICAL MECHANISM

The tool uses a precompiled, minimal whitelist bytecode that stores a list of addresses or a merkle root in the contract storage. For address-based whitelists, the contract stores a mapping of addresses to booleans. For merkle-based whitelists, it stores the root hash, and the contract verifies proofs against it. The tool encodes the constructor arguments (address list or merkle root) and combines them with the bytecode to form the complete deployment payload. The transaction is sent via the wallet's signer with a gas limit of 3,000,000, which is sufficient for whitelist deployment on all major EVM chains. The tool does not rely on any external API or contract factory — the entire bytecode is embedded and signed locally, so no third-party service handles your deployment data. After the transaction is sent, it waits for the receipt and extracts the contract address from the transaction receipt's contractAddress field. The tool does not verify the contract on block explorers; that step is left to the user.

WHAT IT CANNOT SEE

The generated contract is a basic whitelist only. It does not include features such as role-based access, tiered whitelists, expiration times, or multi-sig controls. The tool cannot verify the correctness of the whitelist data or prevent duplicate entries — you must ensure your list is unique and valid. It cannot validate that the addresses are valid or active. The tool cannot verify the security of the generated contract beyond basic whitelist logic. It cannot deploy on non-EVM chains (e.g., Solana, Bitcoin). Deployment is limited by your wallet's native token balance (to pay gas fees) and the availability of the RPC provider. The tool does not monitor the contract after deployment, nor does it provide a management interface for adding or removing addresses after deployment.

PLEASE NOTE

This tool is for educational and rapid prototyping purposes. Always review the contract code and verify it on a block explorer before using it with real value. Only use on networks you trust. The tool does not persist any data; all state is lost on page reload. EVM chains only.