Add PulseChain to MetaMask
Last Verified: June 30, 2026
This guide covers adding the PulseChain network to MetaMask: the verified configuration values, the setup steps, and what to check if something does not work as expected. If you are deciding whether PulseChain is right for you before setting up a wallet, start at The PulseChain Hub.
On this page: Network Values · Step-by-Step Setup · Verify Your Connection · Security · Other Wallets · FAQ · What's Next
The Network Values
These are the values you need. Enter them exactly as shown.
Network Name: PulseChain RPC URL: https://rpc.pulsechain.com Chain ID: 369 Symbol: PLS Block Explorer: https://ipfs.scan.pulsechain.com
These values are sourced from official PulseChain documentation and should be verified against pulsechain.com if you are reading this page significantly after the last updated date shown above. The block explorer listed (https://ipfs.scan.pulsechain.com) is the IPFS-hosted version. For a current list of official explorer options, see scan.pulsechain.com.
Step-by-Step Setup
If your browser is compatible, the official PulseChain website (pulsechain.com) offers a one-click add option that populates these values automatically. If that option is available, use it. If not, follow the manual steps below.
Step 1: Open the network selector. In the MetaMask browser extension, click the network name at the top of the interface (it may show "Ethereum Mainnet" by default). Select "Add network" from the dropdown.
Step 2: Check if PulseChain is already in MetaMask's network list. In some MetaMask versions or third-party network lists, PulseChain may appear as an available custom network. If it appears in your interface, verify the RPC URL and Chain ID match the values above before using it. If it does not appear, add it manually using the values above and proceed to Step 3.
Step 3: If PulseChain is not in the default list, add a network manually. On the network search screen, select "Add a network manually" at the bottom of the page.
Step 4: Enter the configuration values. Fill in each field using the values from the table above. Enter them exactly: the Chain ID must be 369, the RPC URL must be https://rpc.pulsechain.com. A typo in either field will either fail silently or connect to the wrong network.
Step 5: Save and switch. Click Save. MetaMask will prompt you to switch to the PulseChain network. Confirm.
Step 6: Verify the RPC endpoint. Whether you added PulseChain via the default toggle or manually, verify which RPC endpoint is active. In MetaMask settings under Networks, check the RPC URL shown for PulseChain. It should read https://rpc.pulsechain.com. The manual entry method is the only way to confirm the endpoint has not been altered by a localized exploit targeting your device. If the RPC URL does not match, remove the network and add it manually using the verified values above.
These steps apply to the MetaMask browser extension. The mobile app follows a similar process but menu names and navigation may differ slightly by version.
Verify Your Connection
Once PulseChain is added, confirm the setup is correct before sending any funds.
Check the Chain ID. In MetaMask settings under Networks, verify PulseChain is listed with Chain ID 369. A different number means you are connected to a different network.
Check your balance on the explorer. Navigate to https://ipfs.scan.pulsechain.com and search your wallet address. If you have PLS, it should appear there. The explorer reads directly from the chain, independent of MetaMask's display. For a current list of official PulseChain explorer links, see scan.pulsechain.com.
Network added but balance shows zero. This is the most common post-setup issue. Work through these in order: confirm you are viewing the PulseChain network in MetaMask and not Ethereum mainnet; verify your address on the block explorer to confirm whether a balance exists on-chain; if you are checking PLS specifically and it does not appear, confirm the address you funded matches the address in MetaMask exactly. If you are checking for other tokens (ERC-20 equivalents), they will not appear automatically. See the next point.
Tokens are not showing. MetaMask does not automatically detect most tokens on PulseChain. To see a token, import it manually: in MetaMask on the PulseChain network, select "Import tokens" and enter the token's contract address. Find contract addresses on the official PulseChain explorer.
MetaMask Portfolio and PulseChain. MetaMask Portfolio does not currently list PulseChain among its supported networks. To view and interact with PulseChain assets, use the MetaMask browser extension directly and verify balances on the PulseChain explorer. The extension does not require Portfolio and gives full control without additional data infrastructure in the path.
Security: What to Watch for During Setup
The RPC endpoint is a trust assumption. The RPC URL tells MetaMask where to read blockchain data. A malicious RPC can return fabricated balances, make transactions appear to fail when they succeeded, or vice versa. This is why the official endpoint (https://rpc.pulsechain.com) matters: it is the officially documented source. Community RPC alternatives exist but introduce their own trust considerations. See the PulseChain Wallet Security guide for the broader context on RPC risk.
Verify the source of any "Add to MetaMask" button. Fake PulseChain configuration sites designed to inject malicious RPC endpoints are a documented attack vector. Only use the one-click add from pulsechain.com directly, navigated from a bookmark rather than a search result.
Never enter your seed phrase during network setup. Adding a network requires no seed phrase input. Any page or prompt asking for your seed phrase as part of network configuration is an attack.
FAQ
What is PulseChain's Chain ID? PulseChain's Chain ID is 369. This is the value that identifies PulseChain to MetaMask and other EVM-compatible wallets. Enter it exactly: not 1 (Ethereum), not any other number.
What RPC URL should I use for PulseChain? The official endpoint is https://rpc.pulsechain.com. Community alternatives are listed on chainlist.org/chain/369 but are not officially documented by PulseChain. If the official RPC is unreachable, a community alternative can serve as a temporary fallback, but verify the source before adding an unofficial endpoint to your wallet.
Why aren't my tokens showing after adding PulseChain? MetaMask does not auto-detect most tokens on PulseChain. Import them manually: select "Import tokens" in MetaMask on the PulseChain network and enter the token's verified contract address from the official block explorer.
My balance looks wrong: what do I check? First confirm you are on the PulseChain network, not Ethereum mainnet. Then check your address on https://ipfs.scan.pulsechain.com to see the actual on-chain balance. If the explorer and MetaMask disagree, trust the explorer: it reads directly from the chain.
Do I need MetaMask specifically, or will another wallet work?
MetaMask is the most widely used option, but Internet Money Wallet and Brave Wallet are both listed on the official PulseChain website as recommended wallets. ZKX Wallet also offers native PulseChain support with additional privacy-focused features. The choice depends on your priorities, but the network values in this guide apply to any EVM-compatible wallet that supports custom network configuration.
Is the official RPC endpoint safe to use? It is the officially documented endpoint and the appropriate default. As a general principle, any RPC endpoint is a trust assumption: the operator of the endpoint can see your requests and could theoretically return manipulated data. The official endpoint is the lowest-risk option for PulseChain. Avoid adding RPC endpoints from unknown sources.
Why should I use the MetaMask extension instead of MetaMask Portfolio for PulseChain? MetaMask Portfolio does not currently list PulseChain among its supported networks. Use the MetaMask browser extension directly to interact with PulseChain assets. For balance verification, use the PulseChain explorer at https://ipfs.scan.pulsechain.com.
Other Wallets That Support PulseChain
MetaMask is not the only option. The following wallets have verified PulseChain support:
Internet Money Wallet: PulseChain-native EVM wallet that includes PulseChain by default, reducing manual network-setup friction. Open-source and audited (two audits, 2023). Confirm current documentation before use.
Brave Wallet: officially listed on pulsechain.com as a recommended wallet for PulseChain.
ZKX Wallet: Third-party wallet with native PulseChain support and privacy-oriented features including Railgun shielding and stealth addresses. Review disclosed gaps (audit pending, source code pending full open-sourcing) before use. Available at the Chrome Web Store.
What's Next
With PulseChain added to your wallet, the next step for most users is acquiring PLS. The How to Buy PLS guide covers where PLS is available, how the process works, and what to verify before sending funds.
If you already hold assets on Ethereum and want to move them to PulseChain, the PulseChain Bridge Guide covers how the bridge works and what to verify before moving assets.
For an overview of the full PulseChain ecosystem, return to The PulseChain Hub.
The Nexus publishes verified, sourced crypto intelligence weekly: no hype, no cheerleading, just verified reporting, structural analysis, and the incentives shaping the system.
Trust nothing. Verify everything.