Connect to compatible peers without making Paybyte.org a settlement dependency.
Paybyte.org can act as a public seed and reference node, but PBE payment proof lives in signed transactions on the chain. Nodes can synchronize and merchants can verify through any compatible node they trust.
Standalone listener split
| Service | Default standalone binding |
|---|---|
| Local UI / RPC | 127.0.0.1:8024 |
| P2P listener | 0.0.0.0:8025 |
The local interface and the peer listener are intentionally separate so operators can keep UI/RPC private while selectively exposing P2P through firewall/router configuration.
Verify peer identity
Mainnet peers must agree on protocol 1.0, network ID 1, chain ID PBE-MAINNET and the frozen genesis identity. Do not trust a peer merely because it claims the right network ID.
Peer hint safety
Public peer hints are untrusted input. PBE pins resolved public DNS addresses for outbound P2P requests, refuses redirects, caps responses and rejects private peer hints unless the operator explicitly enables network.allowPrivatePeers.
Failover and partitions
Read-only applications may maintain more than one compatible node URL. Before failing over, compare chain identity and synchronization state. PBE 0.0.1 uses deterministic fork choice and confirmation depth rather than hard finality, so deep alternate histories and long partitions remain protocol risks.
Wire-level endpoint behavior is documented separately in the P2P protocol reference.