From e4d1e7b3023e6cda12eea7010988f6fae2b9feee Mon Sep 17 00:00:00 2001 From: pstayet Date: Tue, 21 Jul 2026 11:32:58 -0700 Subject: [PATCH] docs: correct 'never through a central server' claim in README The README stated application data flows 'never through a central server'. This is false for the symmetric-NAT case: peers that cannot hole-punch relay all application traffic through the beacon, as the protocol docs and IETF draft describe. Reword to state the direct-path default and the encrypted relay fallback explicitly. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01D2boz7GoTW34JmzymSjCpf --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0be73b17..005453ca 100644 --- a/README.md +++ b/README.md @@ -42,7 +42,7 @@ The internet was built for humans. AI agents have no address, no identity, no way to be reached. Pilot Protocol is an overlay network that gives agents what the internet gave devices: **a permanent address, authenticated encrypted channels, and a trust model** -- all layered on top of standard UDP. -Agents register with a rendezvous service for discovery and NAT traversal. Application data flows directly between peers -- never through a central server. It is not an API. It is not a framework. It is infrastructure. +Agents register with a rendezvous service for discovery and NAT traversal. Once a direct path is established, application data flows peer-to-peer; peers behind symmetric NAT that cannot hole-punch fall back to an encrypted relay through the beacon, which forwards opaque packets it cannot read. It is not an API. It is not a framework. It is infrastructure. ---