In this tutorial, we will guide you through the step-by-step process of creating TokenBoundaccounts from your NFTs using ERC-6551.To help you begin quickly, we have already set everything up for you. Let's start by making a copy of the repository.<h2>Step 1: Cloning the Tutorial Repo</h2>1.1 Forking the Tutorial Repository:<ul><li>Visit our <a href="https://github.com/BuildBearLabs/Tutorials">Tutorial Repository</a> and click the "Fork" button to duplicate the repository into your own account. Please wait until the forking process is complete before proceeding.</li></ul>1.2 Cloning the repository locally:<ul><li>Go to your forked repository on GitHub.</li><li>Click the "Code" button and copy the URL provided (either HTTPS or SSH).</li><li>Open your terminal or Git Bash.</li><li>Navigate to the directory where you want to place the cloned repository.</li><li>Use the following command to clone the repository:</li></ul><pre><code class="language-plaintext">git clone &lt;paste the copied URL here&gt;
</code></pre><ul><li>Wait for the cloning process to finish. Once completed, you should see a new directory with the repository's name in the chosen directory.</li><li>To access the cloned repository, use the command <code>cd &lt;Name of the cloned Repo&gt;</code>, and then navigate to the ERC-6551 folder by executing <code>cd ERC-6551</code>.</li></ul>Step 2: Developing the smart contract2.1 ERC6551Registry Smart Contract.<figure class="image image_resized" style="width:46.85%;"><img src="https://strapi.buildbear.io/uploads/carbon_14_1_c73487257e.png" alt="carbon (14) (1).png" srcset="https://strapi.buildbear.io/uploads/thumbnail_carbon_14_1_c73487257e.png 116w,https://strapi.buildbear.io/uploads/small_carbon_14_1_c73487257e.png 370w,https://strapi.buildbear.io/uploads/medium_carbon_14_1_c73487257e.png 555w,https://strapi.buildbear.io/uploads/large_carbon_14_1_c73487257e.png 741w," sizes="100vw"></figure>Let's break it down:The contract makes use of two external libraries: IERC6551Registry and Create2 from the OpenZeppelin library. These libraries provide ready-made implementations for the ERC6551 standard. Additionally, CREATE2 is utilized to precompute the address where a smart contract will be deployed.Let's go through the functions in this contract:createAccount: This function is used to create an account. It takes the following parameters:<ul style="list-style-type:disc;"><li><code>implementation</code>: The address of the implementation contract for the account.</li><li><code>chainId</code>: The chain ID of the blockchain where the account will be created.</li><li><code>tokenContract</code>: The address of the token contract associated with the account.</li><li><code>tokenId</code>: The ID of the token associated with the account.</li><li><code>salt</code>: A unique identifier used to compute the account address.</li><li><code>initData</code>: Additional data that can be passed to initialize the account.</li></ul>account: This function is used to compute the account address without creating the account. It takes the same parameters as <code>createAccount</code> and returns the computed account address. It uses the <code>computeAddress</code> function from the Create2 contract to calculate the account address based on the <code>salt</code> and the hash of the bytecode generated using the <code>_creationCode</code> internal function._creationCode: This internal function generates the bytecode for the account creation. It takes the same parameters as <code>createAccount</code> except for <code>implementation_</code>. It returns a byte array that combines the fixed hexadecimal parts of the bytecode with the encoded values of <code>salt_</code>, <code>chainId_</code>, <code>tokenContract_</code>, and <code>tokenId_</code>.2.2 ERC6551Account Smart Contract<figure class="image image_resized" style="width:49.04%;"><img src="https://strapi.buildbear.io/uploads/carbon_15_1_b0fe95564a.png" alt="carbon (15) (1).png" srcset="https://strapi.buildbear.io/uploads/thumbnail_carbon_15_1_b0fe95564a.png 116w,https://strapi.buildbear.io/uploads/small_carbon_15_1_b0fe95564a.png 370w,https://strapi.buildbear.io/uploads/medium_carbon_15_1_b0fe95564a.png 555w,https://strapi.buildbear.io/uploads/large_carbon_15_1_b0fe95564a.png 741w," sizes="100vw"></figure>Let's go through the different parts of the contract:Contract Imports:This contract relies on multiple contracts and interfaces imported from the OpenZeppelin library to meet its requirements. Let's take a look at each of them:<ol style="list-style-type:decimal;"><li>IERC165: This is an interface contract that defines the standard for supporting contract-level queries using the ERC165 standard. It allows contracts to check whether another contract supports a specific interface.</li><li>IERC721: This is an interface contract that defines the standard for non-fungible tokens (NFTs) based on the ERC721 standard. It provides the required functions and events for managing ownership and transfer of unique tokens.</li><li>IERC1271: This is an interface contract that defines the standard for contracts that can provide cryptographic proofs of their authenticity. It specifies a function that allows external parties to verify the signature of a message generated by the contract.</li><li>SignatureChecker: This is a contract that provides helper functions for verifying cryptographic signatures. It includes functions for verifying ECDSA and EdDSA signatures.</li></ol>_nonce: The contract has a private variable <code>_nonce</code> that keeps track of the nonce value. It represents the number of times a call has been executed on the contract.Fallback Function: The contract includes a fallback function <code>receive()</code> declared as <code>external payable</code>. This function allows the contract to receive Ether when it is called with no specific function selector.executeCall: This function is used to execute external calls to other contracts. It takes the following parameters:<ul><li><code>to</code>: The address of the contract to call.</li><li><code>value</code>: The amount of Ether to send along with the call.</li><li><code>data</code>: The data to send as part of the call.</li></ul>token: This function returns information about the token associated with the contract. It retrieves the length of the contract's bytecode and uses the <code>codeAt</code> function from the <code>Bytecode</code> library to extract the relevant portion of the bytecode. The extracted bytecode is then decoded to obtain the chain ID, token contract address, and token ID.owner: This function returns the owner address of the token associated with the contract. It retrieves the chain ID, token contract address, and token ID using the <code>token</code> function. If the chain ID is not equal to the current blockchain's chain ID (<code>block.chainid</code>), it returns address(0). Otherwise, it calls the <code>ownerOf</code> function from the <code>IERC721</code> contract, passing in the token contract address and token ID to retrieve the owner address.nonce: This external function returns the current nonce value, which represents the number of calls executed on the contract.supportsInterface: This function checks whether the contract supports a given interface based on its interface ID. It returns true if the <code>interfaceId</code> matches either the <code>IERC165</code> or <code>IERC6551Account</code> interface IDs.isValidSignature: This function validates a signature for a given hash. It takes the following parameters:<ol style="list-style-type:decimal;"><li><code>hash</code>: The hash value to validate.</li><li><code>signature</code>: The signature to verify.</li></ol>The function uses the SignatureChecker library's isValidSignatureNow function to check the validity of the signature. If the signature is valid, it returns the selector of the isValidSignature function from the IERC1271 contract. Otherwise, it returns an empty bytes4 value ("").Step 3: Setting up the Infrastructure for Deploying and Testing the Smart Contract3.1. Visit the <a href="https://buildbear.io/">BuildBear App</a>. (Wondering why BuildBear? Check out the article <a href="https://medium.com/@thomas_90087/a-thank-you-to-buildbear-5873b8394da5">here</a>).3.2. Create your Private Testnet. You have the option to either fork from the Mainnets or create a new testnet from scratch, using Mainnet as the base. Forking from the Ethereum Mainnet allows us to conveniently utilize existing NFTs and tokens.<figure class="image image_resized" style="width:44.84%;"><img src="https://strapi.buildbear.io/uploads/image_2_6a42a5ed4d.png" alt="image (2).png" srcset="https://strapi.buildbear.io/uploads/thumbnail_image_2_6a42a5ed4d.png 245w,https://strapi.buildbear.io/uploads/small_image_2_6a42a5ed4d.png 500w,https://strapi.buildbear.io/uploads/medium_image_2_6a42a5ed4d.png 750w,https://strapi.buildbear.io/uploads/large_image_2_6a42a5ed4d.png 1000w," sizes="100vw"></figure>3.3. Add your Private Testnet to your MetaMask wallet by using the “Add to Metamask” button:<figure class="image image_resized" style="width:46.27%;"><img src="https://strapi.buildbear.io/uploads/image_3_9b696ebe65.png" alt="image (3).png" srcset="https://strapi.buildbear.io/uploads/thumbnail_image_3_9b696ebe65.png 245w,https://strapi.buildbear.io/uploads/small_image_3_9b696ebe65.png 500w,https://strapi.buildbear.io/uploads/medium_image_3_9b696ebe65.png 750w,https://strapi.buildbear.io/uploads/large_image_3_9b696ebe65.png 1000w," sizes="100vw"></figure><h3>Step 4: Deploying the Smart Contract</h3>To begin, execute the following command to install the necessary packages:<pre><code class="language-plaintext">npm install
</code></pre>4.1 Update the <code>hardhat.config.js</code> file:<ul><li>Go to your Dashboard and click on "verify contract".</li></ul><figure class="image image_resized" style="width:46.12%;"><img src="https://strapi.buildbear.io/uploads/image_4_84637c7d7c.png" alt="image (4).png" srcset="https://strapi.buildbear.io/uploads/thumbnail_image_4_84637c7d7c.png 245w,https://strapi.buildbear.io/uploads/small_image_4_84637c7d7c.png 500w,https://strapi.buildbear.io/uploads/medium_image_4_84637c7d7c.png 750w,https://strapi.buildbear.io/uploads/large_image_4_84637c7d7c.png 1000w," sizes="100vw"></figure><figure class="image image_resized" style="width:47.27%;"><img src="https://strapi.buildbear.io/uploads/image_5_3164db3a2f.png" alt="image (5).png" srcset="https://strapi.buildbear.io/uploads/thumbnail_image_5_3164db3a2f.png 185w,https://strapi.buildbear.io/uploads/small_image_5_3164db3a2f.png 500w,https://strapi.buildbear.io/uploads/medium_image_5_3164db3a2f.png 750w,https://strapi.buildbear.io/uploads/large_image_5_3164db3a2f.png 1000w," sizes="100vw"></figure><ul><li>Copy the BuildBear and Etherscan objects, and update the <code>hardhat.config.js</code> file with the new values.</li></ul>4.2 To deploy the <code>ERC6551Account.sol</code> and <code>ERC6551Registry.sol</code> smart contracts, run the following command: <code>npx hardhat deploy</code>. This will execute the deployment scripts located in the <code>deploy</code> folder and save the deployment details, including the ABI and Contract address, in the <code>deployments</code> folder.<figure class="image image_resized" style="width:75%;"><img src="https://strapi.buildbear.io/uploads/Untitled_54_0178b75781.png" alt="Untitled (54).png" srcset="https://strapi.buildbear.io/uploads/thumbnail_Untitled_54_0178b75781.png 245w,https://strapi.buildbear.io/uploads/small_Untitled_54_0178b75781.png 500w,https://strapi.buildbear.io/uploads/medium_Untitled_54_0178b75781.png 750w,https://strapi.buildbear.io/uploads/large_Untitled_54_0178b75781.png 1000w," sizes="100vw"></figure>Congratulations! 🎉🎉 The smart contract has been successfully deployed.4.3 Creating TokenBound Accounts from NFTs<figure class="image image_resized" style="width:50%;"><img src="https://strapi.buildbear.io/uploads/carbon_16_1_e14ec7c822.png" alt="carbon (16) (1).png" srcset="https://strapi.buildbear.io/uploads/thumbnail_carbon_16_1_e14ec7c822.png 181w,https://strapi.buildbear.io/uploads/small_carbon_16_1_e14ec7c822.png 500w,https://strapi.buildbear.io/uploads/medium_carbon_16_1_e14ec7c822.png 750w,https://strapi.buildbear.io/uploads/large_carbon_16_1_e14ec7c822.png 1000w," sizes="100vw"></figure>Here's a breakdown of the code:<ol style="list-style-type:decimal;"><li>The code fetches signers, <code>deployer</code>, and <code>account2</code>, representing Ethereum addresses that can interact with the blockchain.</li><li>Contracts for NFT, Registry, and ERC6551Account are obtained using <code>hre.ethers.getContractAt()</code>.</li><li>An NFT is minted by calling the <code>safeMint()</code> function and providing the <code>deployer</code> address and a content URL.</li><li>A token-bound account is created using the NFT by calling the <code>createAccount()</code> function on the <code>Registry</code> contract.</li><li>Ether is transferred to the newly created account using <code>deployer.sendTransaction()</code>.</li><li>The balance of the account is retrieved using <code>ethers.provider.getBalance()</code>.</li><li>USDC tokens are transferred to the Token Bound Account by calling the <code>transfer()</code> function on the USDC contract instance.</li></ol>To execute the script, run the following command:<pre><code class="language-plaintext">npx hardhat run scripts/Registry.js
</code></pre><figure class="image image_resized" style="width:52.73%;"><img src="https://strapi.buildbear.io/uploads/Untitled_55_a463bf0cc8.png" alt="Untitled (55).png" srcset="https://strapi.buildbear.io/uploads/thumbnail_Untitled_55_a463bf0cc8.png 245w,https://strapi.buildbear.io/uploads/small_Untitled_55_a463bf0cc8.png 500w,https://strapi.buildbear.io/uploads/medium_Untitled_55_a463bf0cc8.png 750w," sizes="100vw"></figure>Copy the TokenBoundAccount address from the terminal and search for it in the Explorer. You will be able to view the account's balance.<figure class="image image_resized" style="width:52.48%;"><img src="https://strapi.buildbear.io/uploads/Untitled_56_033ecdf724.png" alt="Untitled (56).png" srcset="https://strapi.buildbear.io/uploads/thumbnail_Untitled_56_033ecdf724.png 245w,https://strapi.buildbear.io/uploads/small_Untitled_56_033ecdf724.png 500w,https://strapi.buildbear.io/uploads/medium_Untitled_56_033ecdf724.png 750w,https://strapi.buildbear.io/uploads/large_Untitled_56_033ecdf724.png 1000w," sizes="100vw"></figure>🎉 Congratulations! We have successfully created TokenBoundAccounts using our NFTs! Enjoy exploring the possibilities! 🚀If you support our efforts, please consider following us on <a href="https://twitter.com/_BuildBear">Twitter</a> and <a href="https://www.linkedin.com/company/build-bear/">LinkedIn</a>. If you haven't already, we invite you to join our Telegram group by clicking <a href="https://t.me/+6mjOnBFUR9xjN2U1">here</a>.Github Repo :&nbsp;<a href="https://github.com/BuildBearLabs/Tutorials">Buildbear Tutorials</a>About BuildBear:BuildBear offers developers a convenient platform to create a customized Private Testnet network for testing their DApps. With the ability to fork EVM chains, developers can create a private network tailored to their needs.<blockquote>Use <a href="http://buildbear.io/">BuildBear.io</a> and create Your Private Testnet Now!</blockquote>Author: <a href="https://twitter.com/chandan1_">Chandan</a>

Twitter post - 23 (1).png

In this tutorial, we will guide you through the step-by-step process of creating TokenBoundaccounts from your NFTs using ERC-6551.


Creating Token Bound Accounts(TBA) Using ERC-6551

BUILDBEAR // TUTORIALS

Creating Token Bound Accounts(TBA) Using ERC-6551

Let’s get started then, Shall we?

Let’s get started then, Shall we?

Test DApps at Scale.