AI Ingestion

Network Setup

The Parallel Ledger is designed for a Zero-Trust network posture. In air-gapped or high-security environments, we recommend a "Deny by Default" firewall policy, routing all external traffic through a dedicated Partner Gateway.

The Gateway & Security Boundary

To maintain state machine integrity, the protocol should not be exposed to public or untrusted networks. A middleware layer (the Gateway) should handle authentication and rate limiting before passing validated updates to the Ledger.

Service	Port	Protocol	Context
Ingestion (Primary)	50051	gRPC	Preferred for high-frequency witnessing.
Ingestion (Legacy)	4000	REST/JSON	Web GUI & Admin API.
Witness Relay	443	HTTPS/TLS	Outbound only.

Protocol Efficiency: gRPC binary serialization significantly reduces CPU overhead and latency during high-density block witnessing compared to standard JSON REST.

Administrative GUI: A read-only dashboard is available on port 4000 for auditors to navigate recent updates, source chain proofs, and Merkle roots.

Service Hardening

Reference ufw configuration

# Default posture
ufw default deny incoming
ufw default allow outgoing

# Inbound from Trusted Gateway
ufw allow from [GATEWAY_IP] to any port 50051 proto tcp
ufw allow from [GATEWAY_IP] to any port 4000 proto tcp

# Outbound to Partner Relay Node
ufw allow to [PARTNER_NODE_IP] port 443 proto tcp

ufw enable

For environments where TCP/IP exposure must be eliminated entirely, we are currently developing Unix Domain Socket support. This will allow the Gateway and Ledger to communicate via the filesystem, permitting the total disabling of inbound networking on the host.