ERC-6551 Token-Bound Account Deployer

WHAT IT DOES

The ERC-6551 Token-Bound Account Deployer lets you deploy a smart account for any NFT, creating a token-bound account that is owned and controlled by the NFT itself. You specify the registry address, NFT contract, token ID, and an optional salt for deterministic deployment. The tool reads the NFT ownership, registry state, implementation address, and approval status. It then deploys the token-bound account in a single transaction, making the NFT the owner of a smart wallet that can hold assets and interact with dApps. This unlocks new capabilities for NFTs — they can now be active participants in DeFi, gaming, and other applications.

HOW TO USE

Connect your EVM wallet and select your network. Enter the ERC-6551 registry contract address, the NFT contract address, and the token ID you want to bind. Optionally provide a salt value for deterministic deployment — leave blank for a random salt. Click "Preview deployment" to see the NFT ownership, registry approval status, implementation address, and the predicted account address. If everything looks correct, click "Deploy account" to execute the deployment. The tool will verify ownership, check approvals, and deploy the token-bound account. Progress is shown in real-time, and gas costs are calculated accurately using effectiveGasPrice.

ONE TECHNICAL SECTION — THE REAL MECHANISM

The tool interacts with an ERC-6551 registry contract that implements the Token-Bound Account standard. The registry maintains the account implementation address, which is the logic contract for all token-bound accounts. The createAccount() function deploys a new account using CREATE2 with the provided implementation address, salt, NFT contract, and token ID. The account address is deterministic — the same salt, NFT, and chain produce the same address, enabling predictable interactions. The account() view function computes the address without deploying it, allowing for previews. The tool checks NFT ownership via ownerOf() and registry approvals via isApprovedForAll() and getApproved() to ensure the deployment will succeed. The salt parameter ensures deterministic deployment across chains and environments.

WHAT IT CANNOT SEE

The tool cannot verify off-chain identity or guarantee account compatibility with all dApps. It does not validate that the NFT is legitimate or that the registry implementation is safe. It cannot detect if the registry is malicious or if the account implementation has vulnerabilities. It does not provide financial advice or ensure that the token-bound account will function as expected. The tool also cannot recover funds sent to the account if the NFT is transferred — the account is bound to the NFT, and control moves with the token.

PLEASE NOTE

This tool is EVM-only and supports Ethereum, Goerli, Sepolia, Optimism, Arbitrum, Polygon, and Base. It does not support Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, or XRP. ERC-6551 is a new standard — ensure the registry and implementation are from trusted sources. Deploying a token-bound account does not transfer the NFT; the NFT remains in your wallet while the account becomes its smart wallet. The account is controlled by the NFT holder, not the NFT itself. The tool is provided free and as-is; users assume full responsibility for their deployment decisions.