Add PulseChain to MetaMask

MetaMask ships with Ethereum and a short list of popular networks, and PulseChain is not among them. It has to be added once, after which it sits in the network menu like any other chain and your PLS balance shows up. There are two ways to do it, and both end with the same entry in your wallet: the button below, which asks your wallet to add the network for you, or the five values in the table typed into MetaMask's own form.

Add PulseChain in one click

The button sends a wallet_addEthereumChain request to whichever wallet is installed in this browser. What happens next is your wallet's decision, not this page's: it opens its own approval dialog showing the network name, the RPC URL and the chain ID, and nothing is added until you approve it. Adding a network gives no access to your accounts and connects nothing to PulseSwap.

This button loads with the page. The manual steps below work either way.

MetaMask's reference marks the methods that sign or send with an explicit note saying eth_requestAccounts has to be granted first. This method carries no such note and lists no account-permission error, so a wallet with nothing connected should still show the dialog (MetaMask JSON-RPC reference). If your wallet disagrees and asks you to connect first, the manual route below needs no wallet permission at all.

PulseChain network details

These are the values PulseSwap itself runs PulseChain on. They are read out of the app's chain configuration when this page is built, so the table, the button above and the swap all quote one source. The left column is MetaMask's own field label, in the order the form asks for them.

Add PulseChain to MetaMask by hand

Six steps in the browser extension. The mobile app asks for the same five values in the same order, reached through its settings menu instead.

1. Open MetaMask and click the network name at the top of the window.
2. Choose "Add network" to open the list of networks MetaMask already knows.
3. Choose "Add a network manually" underneath that list.
4. Copy the five values from the table above into the matching fields.
5. Save. MetaMask calls the RPC URL you entered and refuses the form if the chain ID it answers with is not the one you typed.
6. Select PulseChain in the network menu. Your PLS balance appears once the network is active.

Troubleshooting

MetaMask rejects the chain ID. It compares what you typed against what the RPC returns from eth_chainId and refuses the pair when they differ. PulseChain answers 0x171, which is 369. Seeing this usually means the RPC URL points somewhere else, most often at a testnet.

The RPC does not answer. Replace the RPC URL with another public PulseChain endpoint and leave every other field alone. https://rpc-pulsechain.g4mm4.io and https://pulsechain-rpc.publicnode.com are both listed on the chain registry entry for 369, and both returned 0x171 when this page was written.

A token is missing. MetaMask shows PLS and nothing else on a fresh network. Every other token has to be imported once, by contract address, through Import tokens at the bottom of the token list. The address for any PulseChain token is on the token list.

Gas is charged in PLS, not ETH. PLS is PulseChain's native currency, so it is what transaction fees are paid in. A wallet holding tokens but no PLS cannot send anything at all, a swap included, until it has some.

What next

A new network starts empty. PLS and bridged assets come across from Ethereum through the official bridge at bridge.pulsechain.com, which PulseChain runs itself. Once there is a balance in the wallet, PulseSwap quotes the DEXes and aggregators on PulseChain together and settles the trade from your own wallet: how to swap on PulseChain walks through that trade step by step, what PulseSwap is covers how a quote is built and why nothing is ever held for you, and smart order routing covers the mechanism underneath it.