From 1c03f5a4d00c1a63febb4dd53dc0bf859b2c31b2 Mon Sep 17 00:00:00 2001 From: pstayet Date: Tue, 21 Jul 2026 11:32:02 -0700 Subject: [PATCH] fix: disclose registry/beacon dependency and relay fallback in P2P copy MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The homepage 'how it works' lede claimed 'No external dependencies' and the /for/p2p page claimed a universal zero-hop path ('No relay, no gateway') and 'the only long-running service is the daemon'. All three claims contradict the documented architecture: every node depends on the hosted registry (address assignment, key storage, trust relay) and beacon (STUN, hole-punching), and symmetric-NAT peers relay all traffic through the beacon — as this same page's NAT section and FAQ already state. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01D2boz7GoTW34JmzymSjCpf --- src/pages/for/p2p.astro | 4 ++-- src/pages/index.astro | 2 +- src/pages/plain/p2p.astro | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/src/pages/for/p2p.astro b/src/pages/for/p2p.astro index da0e4b1d..8b40ff38 100644 --- a/src/pages/for/p2p.astro +++ b/src/pages/for/p2p.astro @@ -62,7 +62,7 @@ const canonicalUrl = "https://pilotprotocol.network/for/p2p";
Latency
Zero-hop data path
-
Packets travel the exact network RTT between the two machines. No relay, no gateway, no broker queue sitting in between adding tens of milliseconds.
+
On a direct path, packets travel the exact network RTT between the two machines — no gateway, no broker queue sitting in between adding tens of milliseconds. Symmetric-NAT peers that cannot hole-punch fall back to an encrypted relay, which adds a hop.
Security
@@ -72,7 +72,7 @@ const canonicalUrl = "https://pilotprotocol.network/for/p2p";
Ops
No servers to run
-
No message broker to scale. No gateway fleet to patch. The only long-running service is the daemon on each agent machine.
+
No message broker to scale. No gateway fleet to patch. The only service you run is the daemon on each agent machine — discovery and NAT traversal use the Pilot-operated registry and beacon.
Scale
diff --git a/src/pages/index.astro b/src/pages/index.astro index 72caadce..676bba20 100644 --- a/src/pages/index.astro +++ b/src/pages/index.astro @@ -527,7 +527,7 @@ try {
- Peer-to-peer encrypted tunnels at the UDP layer. A thin registry for discovery, then data flows directly between peers. No external dependencies. + Peer-to-peer encrypted tunnels at the UDP layer. A hosted registry and beacon handle discovery and NAT traversal, then data flows directly between peers — with an encrypted relay fallback when symmetric NAT blocks a direct path.
    diff --git a/src/pages/plain/p2p.astro b/src/pages/plain/p2p.astro index 588af468..3920612c 100644 --- a/src/pages/plain/p2p.astro +++ b/src/pages/plain/p2p.astro @@ -12,9 +12,9 @@ import PlainLayout from '../../layouts/PlainLayout.astro';

    Hub-and-spoke is a bottleneck

      -
    • Latency: Packets travel the network RTT between two machines. There is no relay, gateway, or message broker queue.
      • +
    • Latency: On a direct path, packets travel the network RTT between two machines with no gateway or message broker queue. Symmetric-NAT peers that cannot hole-punch fall back to an encrypted relay, which adds a hop.
    • Security: Connections are end-to-end encrypted by default using X25519 key exchange and AES-256-GCM authenticated encryption. This can be disabled with the `--no-encrypt` flag.
      • -
    • Ops: The only long-running service is the daemon on each agent machine. No message broker or gateway fleet is required.
      • +
    • Ops: The only service you run is the daemon on each agent machine. No message broker or gateway fleet is required. Discovery and NAT traversal use the Pilot-operated registry and beacon.
    • Scale: The network grows with the number of agents. Each new peer adds a tunnel to its correspondents, with no central fan-in limit.