Polygon PoS Full Node: Complete Guide

What is a Polygon PoS full node?

A Polygon PoS full node syncs an execution client (and, where applicable, the L1/L2 stack behind it), verifies blocks, and serves standard Ethereum JSON-RPC: eth_blockNumber, eth_getBalance, eth_call, eth_getLogs, and eth_sendRawTransaction.

RpcNode offers managed Polygon PoS Full Node RPC over HTTPS so applications can read POL balances, simulate contracts, and submit signed transactions without self-hosting Erigon/Geth and companion services.

Why Polygon PoS full nodes matter

Every wallet balance, payment confirmation, and contract read ultimately depends on nodes that agree on Polygon PoS state. Public endpoints rate-limit and flake; your product’s reliability tracks the quality of the full nodes behind your RPC URL.

Polygon PoS in the RpcNode catalog: Polygon PoS.

• Native asset: POL
• Environments: Mainnet, Amoy Testnet
• API family: EVM JSON-RPC
• Listed in the RpcNode network catalog

When to run your own Polygon PoS node

Self-hosting a Polygon PoS full node makes sense when you need custom indexing, ultra-low latency next to your app, or compliance constraints that forbid third-party RPC. For most product teams, managed Full Node RPC is faster to ship and cheaper to operate.

• Building wallets, payments, or address watchers that need reliable Polygon PoS reads and writes
• Avoiding multi-terabyte disks, peer tuning, and 24/7 pager duty for chain upgrades
• Preferring HTTPS JSON-RPC with allowlists, keys, and usage metering
• Evaluating Polygon PoS before dedicating hardware — start on RpcNode, or self-host with Toolkit in a few clicks

Polygon PoS full node server requirements

Polygon PoS (matic) full node server requirements for a simple Full Node RPC host usually mean Erigon with `--chain=bor-mainnet`. The classic Bor + Heimdall path is heavier operationally.

Budget 2+ TB NVMe and 32 GB+ RAM. Lite/minimal prune profiles are not the primary path for gateway-grade RPC.

Looking up "Polygon PoS server requirements", "Polygon PoS hardware requirements", or "Polygon PoS minimum specs"? Use the checklist below as the planning baseline for a self-hosted full node.

If you mainly need HTTPS Polygon PoS RPC for wallets or backends, prefer RpcNode managed Full Node RPC instead of sizing and babysitting this hardware yourself.

• CPU: 8+ cores
• RAM: 32 GB+
• Disk: 2+ TB NVMe
• Bandwidth: 1 Gbps; P2P 30303 (+ Heimdall 26656 if you run the classic stack)
• OS: Ubuntu 24.04 LTS
• Preferred RPC path: Erigon all-in-one; Bor+Heimdall for full official/validator setups

Self-host Polygon PoS with RpcNode Toolkit

RpcNode Toolkit is a free self-hosted panel: install a Linux host agent, add the server, then add a node in a few clicks (network → environment → server). The node page walks install, sync, logs, and RPC.

Polygon PoS may already be in the Add node catalog, or you can use managed Full Node RPC on RpcNode while you wait. Hardware requirements in this guide still apply — Toolkit automates the install, not the disks.

1. Install the host agent on Linux, then Add server in the panel.
2. Add node: pick the network, environment, and server.
3. Open the node page for ports, install, sync, and the fullnode RPC endpoint.

Open Toolkit

How to run a Polygon PoS full node

How to run a Polygon PoS full node for RPC: the simple path is Erigon with `--chain=bor-mainnet`. Bor + Heimdall remains the classic full official stack.

If you mainly need HTTPS Polygon PoS RPC for wallets or backends, prefer RpcNode managed Full Node RPC instead of sizing and babysitting this hardware yourself.

1. Provision Ubuntu 24.04 LTS (or the OS your client documents) on bare metal or a dedicated VM. Create a system user such as `nodeop` — do not run the node as root.
2. Attach 2+ TB NVMe for Erigon datadir. Mount it away from the root filesystem and give ownership to the operator user.
3. Apply OS hygiene: unattended-upgrades or a patch cadence, fail2ban/SSH keys, and raise file-descriptor limits if the client docs require it.
4. Install Erigon and start with `--chain=bor-mainnet`, HTTP on `127.0.0.1:8545`, and P2P `30303`.
5. Create systemd for the Erigon process; monitor disk and tip lag.
6. If you choose Bor + Heimdall instead, follow Polygon’s current docs for both services and open Heimdall P2P `26656` when required.
7. Whitelist JSON-RPC only; keep admin/debug APIs local.
8. Verify with `eth_syncing` / `eth_blockNumber` on `http://127.0.0.1:8545`.

• Preferred RPC path: Erigon all-in-one on bor-mainnet
• Ports: 30303 P2P; 8545 RPC whitelist (+ 26656 if Heimdall)

Using Polygon PoS RPC without self-hosting

RpcNode exposes managed EVM JSON-RPC for Polygon PoS. Create an endpoint in the cabinet, restrict IPs if needed, and call the same methods your stack already uses.

Catalog environments for Polygon PoS: Mainnet, Amoy Testnet. Create an endpoint in the RpcNode cabinet for the environment you need, or use this guide to plan a self-hosted deployment.

Typical methods teams start with: eth_blockNumber, eth_getBalance, eth_call, eth_getLogs, eth_sendRawTransaction.

Self-hosting vs managed Full Node RPC

Self-hosting gives maximum control and can reduce per-request cost at huge scale, but you own upgrades, peers, disk growth, and incident response. RpcNode Toolkit cuts the install to a few clicks (agent → Add server → Add node → node page) while you still run the hardware.

Managed RpcNode Full Node RPC trades that ops burden for a stable HTTPS endpoint, usage visibility, and the same method surface your SDK already speaks. If you are comparing providers, also see RpcNode’s comparison page.

Polygon PoS integration checklist

Use this short checklist when wiring Polygon PoS into production.

• Pick the correct environment (Mainnet, Amoy Testnet) — never mix testnet keys with mainnet funds
• Store RPC URLs and keys in secrets management; rotate on staff changes
• Add IP allowlisting for server-side backends
• Alert on tip lag / getHealth (or equivalent) failures
• Load-test eth_getLogs / getProgramAccounts-style heavy calls before launch
• Decide full vs archive needs early — RpcNode is Full Node oriented
• Confirm Polygon PoS server requirements (CPU/RAM/disk) before self-hosting
• Or install with RpcNode Toolkit in a few clicks — free self-hosted panel

Polygon PoS full node FAQ