---
title: "NFT minter tutorial: how to create a full stack dApp"
description: "Unlock the world of NFTs with our comprehensive NFT Minter Tutorial. Learn to create a full-stack dApp effortlessly and start minting your digital assets now!"
---
# NFT minter tutorial: how to create a full stack dApp
In this tutorial, you’ll build an NFT minter and learn how to create a full stack dApp by connecting your smart contract to a React frontend using Metamask and Web3 tools.
Plus, be sure to check out the rest of our NFT tutorial series:
- 🌟 [How to mint an NFT using Web3.js](https://www.alchemy.com/blog/how-to-mint-an-nft-using-web3-js)
- 🪄 [How to mint an NFT with Ether.js](https://www.alchemy.com/blog/how-to-mint-an-nft-with-ethers-js)
- 👛 [How to view your NFT in your mobile wallet](https://www.alchemy.com/blog/how-to-view-your-nft-in-your-mobile-wallet)
- 💸 [How to set a price on an NFT](https://www.alchemy.com/blog/how-to-set-a-price-on-an-nft)
One of the greatest challenges for developers coming from a Web2 background is figuring out how to connect your smart contact to a frontend project and interact with it.
By building an NFT minter—a simple UI where you can input a link to your digital asset, a title, and a description —you'll learn how to:
- Connect to Metamask via your frontend project
- Call smart contract methods from your frontend
- Sign transactions using Metamask
In this tutorial, we will be using [React](https://reactjs.org/) as our frontend framework. Because this tutorial is primarily focused on [Web3 development](https://www.alchemy.com/overviews/how-to-learn-web3-development), we won't be spending much time breaking down React fundamentals. Instead, we'll be focusing on bringing functionality to our project
As a prerequisite, you should have a beginner-level understanding of React—know how components, props, useState/useEffect, and basic function calling works. If you've never heard of any of those terms before, you may want to check out this [Intro to React tutorial](https://reactjs.org/tutorial/tutorial.html). For the more visual learners, we highly recommend this excellent [Full Modern React Tutorial](https://www.youtube.com/playlist?list=PL4cUxeGkcC9gZD-Tvwfod2gaISzfRiP9d) video series by Net Ninja.
Without further ado, let's get started!
## Step 0: making NFTs 101
Before we even start looking at any code, it's important to understand how making an NFT works. It involves two steps:
1\) You publish an NFT smart contract on the Ethereum blockchain. Usually this is an [ERC-721](https://eips.ethereum.org/EIPS/eip-721) or [ERC-1155](https://eips.ethereum.org/EIPS/eip-1155) smart contract.
The biggest difference between the two NFT smart contact standards is that ERC-1155 is a multi-token standard and includes batch functionality, whereas with the ERC-721 is a single-token standard and therefore only supports transferring one token at a time.
2\) You call the minting function on that NFT smart contract to mint the NFT. _Minting_ is simply the act of publishing a unique instance of your non fungible token on the blockchain.
Usually, this minting function requires you to pass in two variables as parameters, first the recipient, which specifies the address that will receive your freshly minted NFT, and second the NFT's tokenURI , a string that resolves to a JSON document describing the NFT's metadata.
An NFT's metadata is really what brings it to life, allowing it to have properties, such as a name, description, image \(or different digital asset\), and other attributes. Here's [an example of a tokenURI](https://gateway.pinata.cloud/ipfs/QmSvBcb4tjdFpajGJhbFAWeK3JAxCdNQLQtr6ZdiSi42V2), which contains an NFT's metadata.
In this tutorial, we're going to focus on part 2, calling an existing NFT's smart contract minting function using our React UI.
[Here's a link](https://sepolia.etherscan.io/address/0x4C4a07F737Bf57F6632B6CAB089B78f62385aCaE) to the ERC-721 NFT smart contract we will be calling in this tutorial. If you'd like to learn how we made it, we highly recommend that you check out our other tutorial, "[How to Create an NFT](https://www.alchemy.com/blog/how-to-create-an-nft)."
Cool, now that we understand how making an NFT works, let's clone our starter files!
## Step 1: clone the starter files
First, go to the [nft-minter-tutorial](https://github.com/alchemyplatform/nft-minter-tutorial) github repository to get the starter files for this project. Clone this repository into your local environment.
Don't know how to clone a repository? Check out [this guide](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository) from Github.
When you open this cloned **nft-minter-tutorial** repository, you'll notice that it contains two folders: **minter-starter-files** and **nft-minter**.
- **minter-starter-files** contains the starter files \(essentially the React UI\) for this project. In this tutorial, **we will be working in this directory**, as you learn how to bring this UI to life by connecting it to your Ethereum wallet and an NFT smart contract.
- **nft-minter** contains the entire completed tutorial and is there for you as a **reference** **if you get stuck.**
Next open your copy of **minter-starter-files** in to your favorite code editor \(at Alchemy, we we're big fans of [VSCode](https://code.visualstudio.com/download)\), and then navigate into your **src** folder:
We will work inside the "src" folder
All of the code we'll write will live under the **src** folder. We'll be editing the **Minter.js** component and writing additional javascript files to give our project Web3 functionality.
## Step 2: check out our starter files
Before we start coding, it's important check out what's already provided for us in the starter files.
#### Get your react project running
Let's start by running the React project in our browser. The beauty of React is that once we have our project running in our browser, any changes we save will be updated live in our browser.
To get the project running, navigate to the root directory of the **minter-starter-files** folder, and the run `npm install` in your terminal to install the dependencies of the project:
Once those have finished installing, run `npm start` in your terminal:
Doing so should open [http://localhost:3000/](http://localhost:3000/) in your browser, where you'll see the frontend for our project. It should consist of 3 fields: a place to input a link to your NFT's asset, enter the name of your NFT, and provide a description.
If you try clicking "Connect Wallet" or "Mint NFT" buttons, you'll notice they don't work—that's because we still need to program their functionality! :\)
#### The minter.js component
**NOTE:** Make sure you're in the **minter-starter-files** folder and not the **nft-minter** folder!
Let's go back into the **src** folder in our editor and open the **Minter.js** file. It's super important that we understand everything in this file, as it is the primary React component we will be working on.
At the top of our this file, we have our state variables that we will update after specific events.
Never heard of React state variables or state hooks? Check out [these](https://reactjs.org/docs/hooks-state.html) docs.
Here's what each of the variables represent:
- **walletAddress** - a string that stores the user's wallet address
- **status** - a string that contains a message to display at the bottom of the UI
- **name** - a string that stores the NFT's name
- **description** - a string that stores the NFT's description
- **url** - a string that is a link to the NFT's digital asset
After the state variables, you'll see three un-implemented functions: `useEffect`, `connectWalletPressed`, and `onMintPressed`. You'll notice that all of these functions are **async**, that's because we will be making asynchronous API calls in them! Their names are eponymous with their functionalities:
- [**useEffect**](https://reactjs.org/docs/hooks-effect.html)- this is a React hook that is called after your component is rendered. Because it has an empty array **\[\]** prop passed into it \(see line 3\), it will only be called on the component's _first_ render. Here we'll call our wallet listener and another wallet function to update our UI to reflect whether a wallet is already connected.
- **connectWalletPressed** - this function will be called to connect the user's Metamask wallet to our dApp.
- **onMintPressed** - this function will be called to mint the user's NFT.
Near the end of this file, we have the UI of our component. If you scan this code carefully, you'll notice that we update our `url`, `name`, and `description` state variables when the input in their corresponding text fields change.
You'll also see that `connectWalletPressed` and `onMintPressed` are called when the buttons with IDs **mintButton** and **walletButton** are clicked respectively.
Finally, let's address where is this Minter component added.
If you go to the **App.js** file, which is the main component in React that acts as a container for all other components, you'll see that our Minter component is injected on line 7.
**In this tutorial, we'll only be editing the Minter.js file and adding files in our src folder.**
Now that we understand what we're working with, let's set up our Ethereum wallet!
## Step 3: set up your Ethereum wallet
For users to be able to interact with your smart contract they will need to connect their Ethereum wallet to your dApp.
#### Download MetaMask
For this tutorial, we’ll use Metamask, a virtual wallet in the browser used to manage your Ethereum account address. If you want to understand more about how transactions on Ethereum work, check out [this page](https://ethereum.org/en/developers/docs/transactions/) from the Ethereum foundation.
You can download and create a Metamask account for free [here](https://metamask.io/download.html). When you are creating an account, or if you already have an account, make sure to switch over to the “Ropsten Test Network” in the upper right \(so that we’re not dealing with real money\).
#### Add ether from a faucet
In order to mint our NFTs \(or sign any transactions on the Ethereum blockchain\), we’ll need some fake Eth. To get Eth you can go to the [Sepolia faucet](/faucets/ethereum-sepolia) and enter your Ropsten account address, then click “Send Ropsten Eth.” You should see Eth in your Metamask account soon after!
#### Check your balance
To double check our balance is there, let’s make an `eth_getBalance` request using [Alchemy’s composer tool](https://www.alchemy.com/composer/?composer_state=%7B%22network%22%3A0%2C%22methodName%22%3A%22eth_getBalance%22%2C%22paramValues%22%3A%5B%22%22%2C%22latest%22%5D%7D). This will return the amount of Eth in our wallet. After you input your Metamask account address and click “Send Request”, you should see a response like this:
**NOTE:** This result is in wei not eth. Wei is used as the smallest denomination of ether. The conversion from wei to eth is: 1 eth = 10¹⁸ wei. So if we convert 0xde0b6b3a7640000 to decimal we get 1\*10¹⁸ which equals 1 eth.
Phew! Our fake money is all there! 🤑
## Step 4: connect MetaMask to your UI
Now that our Metamask wallet is set up, let's connect our dApp to it!
Because we want to prescribe to the [M-V-C](https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller) paradigm, we're going to create a separate file that contains our functions to manage the logic, data, and rules of our dApp, and then pass those functions to our frontend \(our Minter.js component\).
#### The connectWallet function
To do so, let's create a new folder called **utils** in your **src** directory and add a file called **interact.js** inside it, which will contain all of our wallet and smart contract interaction functions.
In our **interact.js** file, we will write a `connectWallet` function, which we will then import and call in our **Minter.js** component.
In your **interact.js** file, add the following
Let's breakdown what this code does:
First, our function checks if it `window.ethereum` is enabled in your browser.
window.ethereum is a global API injected by Metamask and other wallet providers that allows websites to request users' Ethereum accounts. If approved, it can read data from the blockchains the user is connected to, and suggest that the user sign messages and transactions. Check out the [Metamask docs](https://docs.metamask.io/guide/ethereum-provider.html#table-of-contents) for more info!
If `window.ethereum` _is not_ present, then that means Metamask is not installed. This results in a JSON object being returned, where **address** returned is an empty string, and the **status** JSX object relays that the user must install Metamask.
**Most of the functions we write will be returning JSON objects that we can use to update our state variables and UI.**
Now if `window.ethereum `_is_ present, then that's when things get interesting.
Using a try/catch loop, we'll try to connect to Metamask by calling [`window.ethereum.request\(\{ method: "eth\_requestAccounts" \}\);`](https://docs.metamask.io/guide/rpc-api.html#eth-requestaccounts)` `Calling this function will open up Metamask in the browser, whereby the user will be prompted to connect their wallet to your dApp.
- If the user chooses to connect, `method: "eth_requestAccounts"` will return an array that contains all of the user's account addresses that connected to the dApp. Altogether, our `connectWallet` function will return a JSON object that contains the *first* `address` in this array \(see line 9\) and a `status` message that prompts the user to write a message to the smart contract.
- If the user rejects the connection, then the JSON object will contain an empty string for the `address` returned and a `status` message that reflects that the user rejected the connection.
#### Add connectWallet function to your minter.js UI component
Now that we've written this `connectWallet` function, let's connect it to our **Minter.js.** component.
First, we'll have to import our function into our **Minter.js** file by adding
`import \{ connectWallet \} from "./utils/interact.js"`**;** to the top of the Minter.js file. Your first 11 lines of **Minter.js** should now look like this:
Then, inside our `connectWalletPressed` function, we'll call our imported `connectWallet` function, like so:
Notice how most of our functionality is abstracted away from our **Minter.js** component from the **interact.js** file? This is so we comply with the M-V-C paradigm!
In `connectWalletPressed`, we simply make an await call to our imported `connectWallet` function, and using its response, we update our `status` and `walletAddress` variables via their state hooks.
Now, let's save both files \(**Minter.js** and **interact.js**\) and test out our UI so far.
Open your browser on the [http://localhost:3000/](http://localhost:3000/) page, and press the "Connect Wallet" button on the top right of the page.
If you have Metamask installed, you should be prompted to connect your wallet to your dApp. Accept the invitation to connect.
You should see that the wallet button now reflects that your address is connected! Yasssss 🔥
Next, try refreshing the page... this is strange. Our wallet button is prompting us to connect Metamask, even though it is already connected...
Don't worry though! We easily can fix that by implementing a function called `getCurrentWalletConnected`, which will check if an address is already connected to our dApp and update our UI accordingly!
#### The getCurrentWalletConnected function
In your **interact.js** file, add the following `getCurrentWalletConnected` function:
This code is _very_ similar to the `connectWallet` function we just wrote earlier.
The main difference is that instead of calling the method `eth_requestAccounts`, which opens Metamask for the user to connect their wallet, here we call the method `eth_accounts`, which simply returns an array containing the Metamask addresses currently connected to our dApp.
To see this function in action, let's call it in the `useEffect` function of our **Minter.js** component.
Like we did for `connectWallet`, we must import this function from our **interact.js** file into our **Minter.js** file like so:
Now, we simply call it in our `useEffect` function:
Notice, we use the response of our call to `getCurrentWalletConnected` to update our `walletAddress` and `status` state variables.
Once you've added this code, try refreshing our browser window. The button should say that you're connected, and show a preview of your connected wallet's address - even after you refresh! 😅
#### Implement addWalletListener
The final step in our dApp wallet setup is implementing the wallet listener so our UI updates when our wallet's state changes, such as when the user disconnects or switches accounts.
In your **Minter.js** file, add a function `addWalletListener` that looks like the following:
Let's quickly break down what's happening here:
First, our function checks if `window.ethereum` is enabled \(i.e. Metamask is installed\).
- If it's not, we simply set our `status` state variable to a JSX string that prompts the user to install Metamask.
- If it is enabled, we set up the listener `window.ethereum.on("accountsChanged")` on line 3 that listens for state changes in the Metamask wallet, which include when the user connects an additional account to the dApp, switches accounts, or disconnects an account. If there is at least one account connected, the `walletAddress` state variable is updated as the first account in the `accounts` array returned by the listener. Otherwise, `walletAddress` is set as an empty string.
Finally, we must call it in our `useEffect` function:
And voila! We've completed programming all of our wallet functionality! Now that our wallet is set up, let's figure out how to mint our NFT!
## Step 5: NFT metadata 101
So remember the NFT metadata we just talked about in Step 0 of this tutorial—it brings an NFT to life, allowing it to have properties, such as a digital asset, name, description, and other attributes.
We're going to need to configure this metadata as a JSON object and store it, so we can pass it in as the `tokenURI` parameter when calling our smart contract's `mintNFT` function.
The text in the "Link to Asset", "Name", "Description" fields will comprise the different properties of our NFT's metadata. We'll format this metadata as a JSON object, but there are a couple options for where we can store this JSON object:
- We could store it on the Ethereum blockchain; however, doing so would be SUPER expensive \(we're talking upwards of hundreds of dollars\) due to the nature of Ethereum. ❌
- We could store it on a centralized server, like AWS or Firebase. But that would defeat our decentralization ethos. ❌
- We could use IPFS, a decentralized protocol and peer-to-peer network for storing and sharing data in a distributed file system. As this protocol as decentralized and free, it is our best option! ✅
To store our metadata on IPFS, we will use [Pinata](https://pinata.cloud/), a convenient IPFS API and toolkit. In the next step, we'll explain exactly how to do this!
## Step 6: use Pinata to pin your metadata to IPFS
If you don't have a Pinata account, sign up for a free account [here](https://app.pinata.cloud/register) and complete the steps to verify your email and account.
#### Create your Pinata API key
Navigate to the [https://app.pinata.cloud/developers/api-keys](https://app.pinata.cloud/developers/api-keys) page, then select the "New Key" button at the top, set the Admin widget as enabled, and name your key.
You'll then be shown a popup with your API info. Make sure to put this somewhere safe.
Now that our key is set up, let's add it to our project so we can use it.
#### Create a .env file
We can safely store our Pinata key and secret in an environment file. Let's install the [dotenv package](https://www.npmjs.com/package/dotenv) in your project directory.
Open up a new tab in your terminal \(separate from the one running local host\) and make sure you are in the **minter-starter-files** folder, then run the following command in your terminal:
Next, create a **.env** file in the root directory of your **minter-starter-files** by entering the following on your command line:
This will pop open your **.env** file in vim \(a text editor\). To save it hit "esc" \+ ":" \+ "q" on your keyboard in that order.
Next, in VSCode, navigate to your .env file and add your Pinata API key and API secret to it, like so:
Save the file, and then you're ready to start writing the function to upload your JSON metadata to IPFS!
#### Implement pinJSONToIPFS
Fortunately for us, Pinata has an [API specifically for uploading JSON data to IPFS](https://docs.pinata.cloud#PinJSONToIPFS) and a convenient JavaScript with axios example that we can use, with some slight modifications.
In your utils folder, let's create another file called pinata.js and then import our Pinata secret and key from the .env file like so:
Next, paste the additional code from below into your pinata.js file. Don't worry, we'll break down what everything means!
So what does this code do exactly?
First, it imports [axios](https://www.npmjs.com/package/axios), a promise based HTTP client for the browser and node.js, which we will use to make a request to Pinata.
Then we have our asynchronous function `pinJSONToIPFS`, which takes a `JSONBody` as its input and the Pinata api key and secret in its header, all to make a POST request to their `pinJSONToIPFS` API.
- If this POST request is successful, then our function returns an JSON object with the `success`boolean as true and the`pinataUrl` where our metadata was pinned. We will use this `pinataUrl` returned as the `tokenURI` input to our smart contract's mint function.
- If this post request fails, then our function returns an JSON object with the `success`boolean as false and a`message` string that relays our error.
As with our `connectWallet` function return types, we're returning JSON objects so we can use their parameters to update our state variables and UI.
## Step 7: load your smart contract
Now that we have a way to upload our NFT metadata to IPFS via our pinJSONToIPFS function, we're going to need a way to load an instance of our smart contract so we can call its mintNFT function.
As we mentioned earlier, in this tutorial we will be using [this existing NFT smart contract](https://sepolia.etherscan.io/address/0x4C4a07F737Bf57F6632B6CAB089B78f62385aCaE); however, if you'd like to learn how we made it, or make one yourself, we highly recommend you check out our other tutorial, "[How to Create an NFT](https://www.alchemy.com/blog/how-to-create-an-nft)."
#### The contract ABI
If you examined our files closely, you'll have noticed that in our **src** directory, there's a **contract-abi.json** file. An ABI is necessary for specifying which function a contract will invoke as well ensuring that the function will return data in the format you're expecting.
We're also going to need an Alchemy API key and the Alchemy Web3 API to connect to the Ethereum blockchain and load our smart contract.
#### Create your Alchemy API key
If you don't already have an Alchemy account, [sign up for free here](https://alchemy.com/?r=affiliate:d8895272-924f-412b-b63c-60124deb9357).
Once you’ve created an Alchemy account, you can generate an API key by creating an app. This will allow us to make requests to the Ropsten test network.
Navigate to the “Create App” page in your Alchemy Dashboard by hovering over “Apps” in the nav bar and clicking “Create App”
Name your app \(we chose "My First NFT!"\), offer a short description, select “Staging” for the Environment \(used for your app bookkeeping\), and choose “Ropsten” for your network.
Click “Create app” and that’s it! Your app should appear in the table below.
Awesome so now that we've created our HTTP Alchemy API URL, copy it to your clipboard like so…
…and then let's add it to our **.env** file. Altogether, your .env file should look like this:
Now that we have our contract ABI and our Alchemy API key, we're ready to load our smart contract using[ Alchemy Web3](https://github.com/alchemyplatform/alchemy-web3).
#### Set up your Alchemy Web3 endpoint and contract
First, if you don't have it already, you'll need to install [Alchemy Web3](https://github.com/alchemyplatform/alchemy-web3) by navigating to the home directory: **nft-minter-tutorial** in the terminal:
Next let's go back to our **interact.js** file. At the top of the file, add the following code to import your Alchemy key from your .env file and set up your Alchemy Web3 endpoint:
[Alchemy Web3](https://github.com/alchemyplatform/alchemy-web3) is a wrapper around [Web3.js](https://web3js.readthedocs.io/en/v1.2.9/), providing enhanced API methods and other crucial benefits to make your life as a web3 developer easier. It is designed to require minimal configuration so you can start using it in your app right away!
Next, let's add our contract ABI and contract address to our file.
Once we have both of those, we're ready to start coding our mint function!
## Step 8: implement the mintNFT function
Inside your **interact.js** file, let's define our function, **mintNFT**, which eponymously will mint our NFT.
Because we will be making numerous asynchronous calls \(to Pinata to pin our metadata to IPFS, Alchemy Web3 to load our smart contract, and Metamask to sign our transactions\), our function will also be asynchronous.
The three inputs to our function will be the `url` of our digital asset, `name`, and `description`. Add the following function signature below the `connectWallet` function:
#### Input error handling
Naturally, it makes sense to have some sort of input error handling at the start of the function, so we exit this function if our input parameters aren't correct. Inside our function, let's add the following code:
Essentially, if any of the input parameters are an empty string, then we return a JSON object where the `success` boolean is false, and the `status` string relays that all fields in our UI must be complete.
#### Upload the metadata to IPFS
Once we know our metadata is formatted properly, the next step is to wrap it into a JSON object and upload it to IPFS via the `pinJSONToIPFS` we wrote!
To do so, we first we need to import the `pinJSONToIPFS` function into our **interact.js** file. At the very top of the **interact.js**, let's add:
Recall, that `pinJSONToIPFS`takes in a JSON body. So before we make a call to it, we're going to need to format our`url`, `name`, and `description` parameters into a JSON object.
Let's update our code to create a JSON object called `metadata` and then make a call to `pinJSONToIPFS` with this `metadata` parameter:
Notice, we store the response of our call to `pinJSONToIPFS(metadata)` in the `pinataResponse` object. Then, we parse this object for any errors.
If there's an error, we return a JSON object where the `success` boolean is false and our `status` string relays that our call failed. Otherwise, we extract the `pinataURL` from the `pinataResponse` and store it as our `tokenURIvariable`.
Now it's time to load our smart contract using the Alchemy Web3 API that we initialized at the top of our file. Add the following line of code to the bottom of the `mintNFT` function to set the contract at the `window.contract` global variable:
The last thing to add in our `mintNFT` function is our Ethereum transaction:
If you're already familiar with Ethereum transactions, you'll notice that the structure is pretty similar to what you've seen.
First, we set up our transactions parameters.
- `to` specifies the the recipient address \(our smart contract\)
- `from` specifies the signer of the transaction \(the user's connected address to Metamask: `window.ethereum.selectedAddress``\)`
- `data` contains the call to our smart contract `mintNFT` method, which receives our `tokenURI` and the user's wallet address, `window.ethereum.selectedAddress`, as inputs
Then, we make an await call, `window.ethereum.request`, where we ask Metamask to sign the transaction. Notice, in this request, we're specifying our eth method \(`eth\_SentTransaction`\) and passing in our `transactionParameters`. At this point, Metamask will open up in the browser, and prompt the user to sign or reject the transaction.
- If the transaction is successful, the function will return a JSON object where the boolean `success` is set to true and the `status` string prompts the user to check out Etherscan for more information about their transaction.
- If the transaction fails, the function will return a JSON object where the `success` boolean is set to false, and the `status` string relays the error message.
Altogether, our `mintNFT` function should look like this:
That's one giant function! Now, we just need to connect our `mintNFT` function to our **Minter.js** component...
## Step 9: connect mintNFT to our minter.js frontend
Open up your **Minter.js** file and update the `import \{ connectWallet \} from "./utils/interact.js"`; line at the top to be:
Finally, implement the `onMintPressed` function to make await call to your imported `mintNFT` function and update the `status` state variable to reflect whether our transaction succeeded or failed:
## Step 10: deploy your NFT to a live website
Ready to take your project live for users to interact with? Check out this[ tutorial](https://app.gitbook.com/@alchemyapi/s/alchemy/tutorials/nft-minter/how-do-i-deploy-nfts-online) for deploying your Minter to a live website:
## Step 11: take the blockchain world by storm 🚀
JK, you made it to the end of the tutorial! To recap, by building an NFT minter, you successfully learned how to:
- Connect to Metamask via your frontend project
- Call smart contract methods from your frontend
- Sign transactions using Metamask
Presumably, you'd like to be able to show off the NFTs minted via your dApp in your wallet — so be sure to check out our quick tutorial [How to View Your NFT in Your Wallet](/blog/how-to-view-your-nft-in-your-mobile-wallet)!
And, as always, if you have any questions, visit the [Alchemy support center](https://www.alchemy.com/support). We can't wait to see how you apply the concepts from this tutorial to your future projects! 🧙♂️