Integration of MetaMask wallet in React application

Paulina Lewandowska

19 Dec 2022
Integration of MetaMask wallet in React application

Introduction

In decentralized applications, users typically need a crypto wallet to interact with the blockchain. To enable this, developers working on the frontend layer must integrate their application with users' wallet applications. This article is intended for developers using the React library who want to create user interfaces with the popular browser plugin, MetaMask. Here is a step-by-step guide on how to integrate a React application with MetaMask.

A basic application in React

The source code of the application written for this tutarial can be found at this link. I used the following libraries to create the application:

To work with this tutorial, you can use the application provided at the link above, or you can configure the application yourself in React with the help of, for example, create-react-app or vite.

Once our application is configured, you need to make sure that we have all the necessary dependencies installed, to do this, run the command

npm install wagmi ethers

To prepare the application, I also used a component library called Material-ui, if you also want to use it, install the following packages with the command:

npm install @mui/material @emotion/react @emotion/styled

Once the configuration is complete and all the necessary dependencies are installed, we can move on to the next point.

Wagmi Library

To integrate with the MetaMask wallet application, we will use a dedicated library for React called wagmi that contains a sizable number of hooks and functions needed for daily blockchain interactions in frontend applications.

The first step will be to configure the library, to do this we need to wrap our application in a WagmiConfig component passing a client variable with our configuration:

import { WagmiConfig, createClient } from "wagmi";
import { getDefaultProvider } from "ethers";
 
import { Home } from "./pages";
import "./styles.css";
 
const client = createClient({
 autoConnect: true,
 provider: getDefaultProvider()
});
 
export default function App() {
 return (
   <WagmiConfig client={client}>
     <Home />
   </WagmiConfig>
 );
}

All available configuration options can be found at this link in the official wagmi documentation

Connecting the MetaMask wallet

Once we have completed the configuration of the wagmi library, we can move on to creating the component responsible for connecting to our wallet. The hooks available in the blibliothek will be helpful in the implementation.

To access the function that will allow us to make a request to connect the wallet, use the useConnect() hooka. To indicate that the wallet we want to connect to is MetaMask, pass the created instance of the InjectedConnector class in the configuration object to the hooka under the connecter key

import { useConnect } from "wagmi";
import { InjectedConnector } from "wagmi/dist/connectors/injected";
 
 ...
 
 const { connect } = useConnect({
   connector: new InjectedConnector()
 });
 
 ...

Hook returns us a connect function that we can call, for example, when the button is clicked.

 ...
 
<Button onClick={() => connect()}>Connect</Button>
 
 ...

To get information about the connected wallet or its connection status, you can use the useAccount() hookup, which returns us such information as:

  • the address of the connected wallet
  • whether the wallet connection action is in progress
  • whether the user's wallet is currently connected in the application
...
 
 const { address, isConnected, isConnecting } = useAccount();
 
 ...

If the user of our application managed to connect the wallet we should also allow him to disconnect it, for this we need to use the disconnect function, which we can access with the help of the hookup useDisconnect()

 ...
 
 const { disconnect } = useDisconnect();
 
 ...

With the help of these three simple hooks, we are able to handle wallet connection. The full source code of the component that handles the connection from the sample application:

import { useConnect, useDisconnect, useAccount } from "wagmi";
import { InjectedConnector } from "wagmi/dist/connectors/injected";
import { Card, Button, Heading } from "../../components";
import Typography from "@mui/material/Typography";
import { WalletInfo } from "./WalletInfo";
 
export const WalletConnect = () => {
 const { isConnected, isConnecting } = useAccount();
 
 const { connect } = useConnect({
   connector: new InjectedConnector()
 });
 
 const { disconnect } = useDisconnect();
 
 return (
   <Card>
     <Heading sx={{ mb: 2 }}>
       {isConnected ? "Your connected wallet:" : "Connect your MetaMask"}
     </Heading>
 
     {isConnecting && <Typography>Connecting...</Typography>}
 
     {isConnected ? (
       <>
         <WalletInfo />
         <Button sx={{ mt: 2 }} onClick={() => disconnect()}>
           Disconnect
         </Button>
       </>
     ) : (
       <Button
         disabled={isConnecting}
         sx={{ mt: 2 }}
         onClick={() => connect()}
       >
         Connect
       </Button>
     )}
   </Card>
 );
};

In the above example there is a <WalletInfo /> component, which we will use to display information about the connected wallet, we will deal with its creation in the next step.

Displaying information about the connected wallet

The next step will display to the user information about the connected wallet such as:

  • Wallet address
  • The current ETH balance of the wallet

To do this, we will prepare two simple components <WalletAddress/> and <WalletBalance/> and , which we will then put into the <WalletInfo/> component:

The address of the currently connected wallet

import { WalletAddress } from "./WalletAddress";
import { WalletBalance } from "./WalletBalance";
 
export const WalletInfo = () => {
 return (
   <div>
     <WalletAddress />
     <WalletBalance />
   </div>
 );
};
import { useAccount } from "wagmi";
import Typography from "@mui/material/Typography";
 
export const WalletAddress = () => {
 const { address } = useAccount();
 return (
   <Typography>
     <strong>Address: </strong>
     {address}
   </Typography>
 );
};

In order to display the connected wallet, we will use the previously mentioned useAccount() hookup, which returns us the address variable. The implementation of a simple component to display the address looks like this:

import { useAccount } from "wagmi";
import Typography from "@mui/material/Typography";
 
export const WalletAddress = () => {
 const { address } = useAccount();
 return (
   <Typography>
     <strong>Address: </strong>
     {address}
   </Typography>
 );
};

Balance of the currently connected wallet

The wagmi library also has a useBalance() hook, which will make the process of retrieving the current wallet balance much easier for us. The process of fetching this value from the blockchain is asynchronous, so this hook returns on, among other things, such information in variables as:

  • isLoading - whether the balance download is in progress
  • isFetched - whether the wallet's balance has been downloaded
  • isError - whether an error occurred while downloading the data
  • data - object containing such fields as:
    • value - user balance in WEI units
    • formatted - user's balance formatted to ETH units
    • symbol - Symbol of the asset for which the balance was downloaded
    • decimals - the number of decimal places that the number describing the quantity of the asset can have

For a better understanding of what a WEI, ETH unit or decimals parameter is, I encourage you to read these articles:

To indicate for which wallet we want to retrieve the balance of funds, we need to pass the address of this wallet as a parameter when calling the hookah as follows, to do this we can use the useAccount() hookah again from the previous step:

 ...
 
 const { address } = useAccount();
 const { isLoading, isFetched, isError, data } = useBalance({ address });
 
 ...

With this information, we are able to implement an entire component with support for the data loading process:

import { useAccount, useBalance } from "wagmi";
import Typography from "@mui/material/Typography";
import Skeleton from "@mui/material/Skeleton";
 
export const WalletBalance = () => {
 const { address } = useAccount();
 const { isLoading, isFetched, isError, data } = useBalance({ address });
 
 return (
   <Typography>
     {isLoading && <Skeleton width={200} />}
     {isFetched && (
       <>
         <strong>Balance: </strong>
         {data?.formatted} {data?.symbol}
       </>
     )}
     {isError && "Fetching balance failed!"}
   </Typography>
 );
};

Summary

The application presented here is just an example, in production applications developers often have to deal with integrating multiple wallet applications, supporting connectivity on multiple blockchain networks, and interactions of connected wallets with smart contracts. All of these functionalities and much more are supported by the wagmi library presented in this turorial. Therefore, I encourage you to study the documentation of this library to see what capabilities it offers.

Tagi

Most viewed


Never miss a story

Stay updated about Nextrope news as it happens.

You are subscribed

Blockchain for Creators: Secure and Sustainable Infrastructure

Miłosz Mach

07 Nov 2025
Blockchain for Creators: Secure and Sustainable Infrastructure

In today’s digital creative space, where the lines between art and technology are constantly blurring, projects like MARMALADE mark the beginning of a new era - one where creators can protect their work and maintain ownership through blockchain technology.

For Nextrope, being part of MARMALADE goes far beyond implementing features like screenshot blocking or digital watermarking. It’s about building trust infrastructure - systems that empower creators to thrive in the digital world safely and sustainably.

A new kind of blockchain challenge

Cultural and educational projects come with a completely different set of challenges than typical DeFi systems. Here, the focus isn’t on returns or complex smart contracts - it’s on people: artists, illustrators, educators.

That’s why our biggest task was to design secure yet intuitive infrastructure - lightweight, energy-efficient, and accessible for non-technical users exploring Web3 for the first time.

“Our mission wasn’t to build another financial protocol. It was to create a layer of trust for digital creators.”
— Nextrope Team

Security that stays invisible

The best security is the kind you don’t notice.
Within MARMALADE, we focused on making creators' protection seamless:

  • Screenshot blocking safeguards artworks viewed in browsers.
  • Dynamic watermarking helps identify unauthorized copies.
  • Blockchain registry ensures every proof of ownership remains transparent and immutable

“Creators shouldn’t have to think about encryption or private keys - our job is to make security invisible.”

Sustainability by design

MARMALADE also answers a bigger question - how to innovate responsibly.
Nextrope’s infrastructure relies on low-emission blockchain networks and modular architecture that can easily be adapted for other creative or cultural initiatives.

This means the technology built here can support not only artists but also institutions, universities, and educators seeking to integrate blockchain in meaningful ways.

Beyond technology

For Nextrope, MARMALADE is more than a project — it’s proof that blockchain can empower culture and creators, not just finance. By building tools for digital artists, we’re helping them protect their creativity and discover how technology can amplify human expression.

Plasma blockchain. Architecture, Key Features & Why It Matters

Miłosz Mach

21 Oct 2025
Plasma blockchain. Architecture, Key Features & Why It Matters

What is Plasma?

Plasma is a Layer-1 blockchain built specifically for stablecoin infrastructure combining Bitcoin-level security with EVM compatibility and ultra-low fees for stablecoin transfers.

Why Plasma Blockchain Was Created?

Existing blockchains (Ethereum, L2s, etc.) weren’t originally designed around stablecoin payments at scale. As stablecoins grow, issues like congestion, gas cost, latency, and interoperability become constraints. Plasma addresses these by being purpose-built for stablecoin transfers, offering features not found elsewhere.

  • Zero-fee transfers (especially for USDT)
  • Custom gas tokens (separate from XPL, to reduce friction)
  • Trust-minimized Bitcoin bridge (to allow BTC collateral use)
  • Full EVM compatibility smart contracts can work with minimal modifications

Plasma’s Architecture & Core Mechanisms

EVM Compatibility + Smart Contracts

Developers familiar with Ethereum tooling (Solidity, Hardhat, etc.) can deploy contracts on Plasma with limited changes making it easy to port existing dApps or DeFi, similar to other EVM-compatible infrastructures discussed in the article „The Ultimate Web3 Backend Guide: Supercharge dApps with APIs".

Gas Model & Token Mechanism

Instead of forcing users always to hold XPL for gas, Plasma supports custom gas tokens. For stablecoin-native flows (e.g. USDT transfers), there is often zero fee usage, lowering UX friction.

Bitcoin Bridge & Collateral

Plasma supports a Bitcoin bridge that lets BTC become collateral inside smart contracts (like pBTC). This bridges the security of Bitcoin with DeFi use cases within Plasma.
This makes Plasma a “Bitcoin-secured blockchain for stablecoins".

Security & Finality

Plasma emphasizes finality and security, tuned to payment workloads. Its consensus and architecture aim for strong protection against reorgs and double spends while maintaining high throughput.
The network launched mainnet beta holding over $2B in stablecoin liquidity shortly after opening.

Plasma Blockchain vs Alternatives: What Makes It Stand Out?

FeaturePlasma (XPL)Other L1 / L2
Stablecoin native designusually second-class
Zero fees for stablecoin transfersrare, or subsidized
BTC bridge (collateral)only some chains
EVM compatibilityyes in many, but with trade-offs
High liquidity early✅ (>$2B TVL)many chains struggle to bootstrap

These distinctions make Plasma especially compelling for institutions, stablecoin issuers, and DeFi innovators looking for scalable, low-cost, secure payments infrastructure.

Use Cases: What You Can Build with Plasma Blockchain

  • Stablecoin native vaults / money markets
  • Payment rails & cross-border settlement
  • Treasury and cash management flows
  • Bridged BTC-backed stablecoin services
  • DeFi primitives (DEX, staking, yield aggregation) optimized for stablecoins

If you’re building any product reliant on stablecoin transfers or needing strong collateral backing from BTC, Plasma offers a compelling infrastructure foundation.

Get Started with Plasma Blockchain: Key Steps & Considerations

  1. Smart contract migration: assess if existing contracts can port with minimal changes.
  2. Gas token planning: decide whether to use USDT, separate gas tokens, or hybrid models.
  3. Security & audit: focus on bridge logic, reentrancy, oracle risks.
  4. Liquidity onboarding & market making: bootstrap stablecoin liquidity, incentives.
  5. Regulation & compliance: stablecoin issuance may attract legal scrutiny.
  6. Deploy MVP & scale: iterate fast, measure gas, slippage, UX, security.