Port 8444 – Chia Node

TCP

Port 8444 is the Chia blockchain full node P2P port. Chia nodes communicate on port 8444 to synchronize the blockchain, propagate transactions, and participate in consensus (proof-of-space-and-time). Port 8444 exposure is required for farming. The Chia RPC/wallet interface runs on port 8555 (localhost only).

Port Number

8444

Protocol

TCP

Service

Chia Blockchain Full Node

Range

IANA Registered (1024–49151)

Description

Chia Network full nodes listen on port 8444 for peer-to-peer communication on the Chia blockchain mainnet. The node syncs the blockchain (currently ~100 GB), relays transactions, validates blocks, and participates in the proof-of-space-and-time consensus if the operator is farming. Like Bitcoin's port 8333, Chia's port 8444 is designed to be public – open nodes strengthen the network. The security-sensitive ports are 8555 (full node RPC) and 9256 (wallet RPC), which should remain bound to localhost. Port 8444 only serves the P2P gossip protocol and does not expose keys, wallet balances, or farming rewards.

Security risks

1RPC/wallet port confusion: port 8555 (full node RPC) and port 9256 (wallet RPC) provide programmatic access to farming operations and fund transfers. Accidentally exposing these instead of 8444 gives attackers control of your farming rewards and wallet. Verify with: chia show -s (shows only P2P connections, not RPC exposure).
2Eclipse attacks: similar to Bitcoin, an attacker who fills all your P2P peer slots on port 8444 can isolate your farmer from the real chain, causing you to farm on a fork (wasted proofs) or withholding blocks from you.
3Resource exhaustion: Chia full nodes maintain a mempool and respond to peer requests. A flood of connections on port 8444 can exhaust memory or file descriptors, causing your farmer to miss signage points and lose potential rewards.
4Certificate/key leakage: Chia uses TLS for P2P connections with auto-generated certificates stored in ~/.chia/mainnet/config/ssl/. If these files are exposed (backup leak, Docker volume mount), an attacker can impersonate your node.

Firewall guidance

Port 8444 SHOULD be open inbound for a healthy full node – open nodes strengthen the network and improve your sync speed. Only the P2P protocol is served; no wallet/key operations are possible through 8444. Ports 8555 (RPC) and 9256 (wallet) must remain bound to 127.0.0.1. In Docker: expose only 8444, never 8555 or 9256. Use 'chia configure --set-node-introducer' if you need to restrict peer discovery.

Diagnosis commands

Show sync status and connected peers on port 8444

shell

chia show -s -c

Verify port 8444 is active for P2P

shell

chia show -s | grep 'Full Node Port'

Verify RPC port binds to 127.0.0.1 (should NOT be 0.0.0.0)

shell

ss -tnlp sport = :8555

Audit: only 8444 should be reachable from outside

shell

nmap -p 8444,8555,9256 target

Usage examples

Port 8444 – Chia Node

shell

chia show -s -c (shows connections on port 8444)
chia configure --set-farmer-peer host:8444
ufw allow 8444/tcp

Common services on this port

Chia Network full nodeChia farmerChia harvesterFlexPool/SpacePool (farming pools)

Related ports

8555

Chia full node RPC (NEVER expose)

9256

Chia wallet RPC (NEVER expose)

8447

Chia data layer P2P

8333

Bitcoin P2P (same exposure model)

History

Chia Network was founded by Bram Cohen (BitTorrent creator) in 2017 and launched mainnet in March 2021. Port 8444 was chosen as the P2P port. Chia uses proof-of-space-and-time instead of proof-of-work, storing cryptographic plots on hard drives rather than running GPUs. The blockchain uses a custom CLVM (Chialisp Virtual Machine) for smart contracts. Network peaked at 35 EiB of storage committed to farming.

FAQ

Do I need port 8444 open to farm Chia?

Not strictly – your node can farm with only outbound connections. But opening port 8444 inbound means more peers connect to you (up to 40 inbound), improving sync speed, reducing missed signage points, and strengthening the network. For optimal farming rewards, port 8444 should be forwarded through your router/firewall.

Port 8444 vs 8555 – which is dangerous?

Port 8444 (P2P): safe to expose, serves only blockchain gossip protocol. Port 8555 (RPC): dangerous, provides full node control including block farming settings. Port 9256 (wallet RPC): critical, controls fund transfers, key export, and transaction signing. The rule is identical to Bitcoin: P2P port = public, RPC/wallet ports = localhost only.