Chain ID 369 · PLS

PulseChain

Public RPC endpoints and wallet configuration for PulseChain.

Website ↗

Network endpoints

EndpointLatencyAdd
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
01

What is a PulseChain RPC?

An RPC endpoint connects wallets and applications to PulseChain. Use the endpoints above for JSON-RPC requests, and keep alternatives available for regional endpoint failures or rate limits.

02

Add PulseChain to MetaMask

Use “Add to wallet” to request the network configuration. Always verify chain ID 369, currency PLS, and the selected RPC before approving.

03

Public RPC safety

Public endpoints are third-party infrastructure. They may log requests, enforce limits, or become unavailable. Never place private keys, seed phrases, or secrets in an RPC request.

04

Common RPC errors

Rate limits, browser CORS rules, network mismatch, and temporary provider failures are common. Try another listed endpoint and verify the returned chain ID.

Common questions

PulseChain RPC FAQ

What is the RPC URL for PulseChain?+

https://rpc.pulsechain.com is the recommended endpoint in this directory. Multiple alternatives are listed above in case an endpoint is unavailable from your region.

What is the PulseChain chain ID?+

PulseChain uses chain ID 369 (0x171 in hexadecimal).

How do I add PulseChain to my wallet?+

Use the Add to wallet button above. Your wallet will ask you to review and approve the network details.

Are public RPC endpoints safe?+

Treat public RPCs as infrastructure operated by third parties. They can observe requests, rate-limit traffic, or be unavailable. Never send private keys or seed phrases to an RPC.

Found an issue?

Help keep network data current through a community contribution.

Report a broken RPC →