Within this guide, you’ll learn how to use Universal Accounts alongside browser-injected EVM wallets —such as MetaMask or other providers. You’ll learn how to:
  • Initialize a Universal Account from a connected EOA.
  • Create and sign a transaction with MetaMask.
  • Send the transaction through the Universal Accounts SDK.
This guide uses window.ethereum as the provider used via ethers.js.

​
Getting Started

To start, ensure you have an app set up with a browser-injected EVM wallet like MetaMask installed. Then, follow the steps below:
You can find a repository with a working example of this integration on GitHub.
1

Install the Universal Accounts SDK

Install the required dependencies in your project:
npm install ethers @particle-network/universal-account-sdk
2

Set Environment Variables

Add your Universal Accounts project ID to .env.local:
.env
NEXT_PUBLIC_PROJECT_ID="YOUR_PROJECT_ID"
NEXT_PUBLIC_CLIENT_KEY="YOUR_CLIENT_KEY"
NEXT_PUBLIC_APP_ID="YOUR_APP_ID"
Get your Universal project keys from the Particle Dashboard.Find a full rundown of the process on the Universal Accounts SDK reference page.

​
Set Up a Browser Wallet

To interact with Universal Accounts using window.ethereum, you first need to connect to an EVM-compatible browser wallet like MetaMask. Here’s a simple example using ethers.js: 
import { ethers } from "ethers";

// Ensure MetaMask (or another injected provider) is available
if (!window.ethereum) {
  throw new Error("MetaMask is not installed");
}

const provider = new ethers.BrowserProvider(window.ethereum);

// Prompt user to connect their wallet
await provider.send("eth_requestAccounts", []);

// Retrieve the connected account
const accounts = await provider.listAccounts();
const walletAddress = accounts[0].address;
setWalletAddress(walletAddress);
This example uses ethers.BrowserProvider, available in ethers v6.
This wallet address can now be passed into the Universal Account SDK as the ownerAddress.

​
Initializing a Universal Account

Once the user connects their wallet and you obtain their EOA address, create a new Universal Account instance: 
import { UniversalAccount } from "@particle-network/universal-account-sdk";

const universalAccount = new UniversalAccount({
  projectId: process.env.NEXT_PUBLIC_PROJECT_ID!,
  projectClientKey: process.env.NEXT_PUBLIC_CLIENT_KEY!,
  projectAppUuid: process.env.NEXT_PUBLIC_APP_ID!,
  ownerAddress: address,
  // If not set it will use auto-slippage
  tradeConfig: {
    slippageBps: 100, // 1% slippage tolerance
    //usePrimaryTokens: [SUPPORTED_TOKEN_TYPE.SOL], // Specify token to use as source (only for swaps)
  },
});
You only need the EOA wallet address to initialize a Universal Account.

​
Sending a Transaction with a Browser Wallet

Once you have a Universal Account instance, you can use it to send transactions. The code below shows how to set up a custom transaction using the user’s browser-injected EVM wallet as a signer. In this case, the funds will be automatically sourced from the user’s Primary Assets and converted into 1 USDT on Avalanche. 
import { ethers } from "ethers";
import { CHAIN_ID, SUPPORTED_TOKEN_TYPE } from "@particle-network/universal-account-sdk";

const transaction = await universalAccount.createUniversalTransaction({
  chainId: CHAIN_ID.AVALANCHE_MAINNET,
  expectTokens: [
    {
      type: SUPPORTED_TOKEN_TYPE.USDT,
      amount: "1",
    },
  ],
  transactions: [],
});

if (!window.ethereum) {
  throw new Error("Wallet not found");
}

const provider = new ethers.BrowserProvider(window.ethereum);
const signer = await provider.getSigner();
const signature = await signer.signMessage(transaction.rootHash);

const result = await universalAccount.sendTransaction(transaction, signature);

console.log(`View on Explorer: https://universalx.app/activity/details?id=${result.transactionId}`);
This pattern works for all transaction types supported by the SDK.

More Transaction Examples

Check our SDK reference for more transaction examples.

​
What’s Next?

Explore the SDK reference for more advanced capabilities.

SDK Reference

Learn more about the SDK APIs.

Supported Chains

See which chains are supported.