Home / Playbooks / Pipe PoP node

Deploy a Pipe Network PoP Node (Post-TGE PIPE Rewards)

Docker-compose deployment for Pipe Network Points-of-Presence — license approval, compose file, and post-TGE economics worth knowing first.

Intermediate⏱ ~25 minutes (plus license wait)·Free on existing hardware; VPS rental rarely profitable post-TGE·Updated 2026-08-24
Contents
  1. Read before deploying: post-TGE math
  2. Request a node license
  3. Deploy via docker-compose
  4. Verify delivery & monitor epochs
  5. Ongoing operations

1. Read before deploying: post-TGE math

PIPE tokens are live and tradeable — rewards are real money now, which also means the pre-TGE gold rush is over. Rewards weight by location scarcity × uptime × delivered traffic. Saturated metros earn thin; unserved regions earn disproportionately.

Do not rent new VPS just for this unless you've secured a scarce location slot. Existing idle hardware or already-paid VPS = fine. Launch-era distribution disputes are documented public history — size expectations accordingly.

2. Request a node license

PoP nodes require approval — this is curated infrastructure, not permissionless mining:

1. Create an operator account at pipe.network's node portal

2. Submit your location + hardware specs (2+ vCPU, unmetered bandwidth preferred)

3. Wait for license approval — scarce locations approve faster

Approval email includes your node credentials/license key needed below.

3. Deploy via docker-compose

git clone https://github.com/preterag/pipe-pop.git && cd pipe-pop
# review the compose + env templates BEFORE running anything
cat docker-compose.yml docker-compose.env.example 2>/dev/null || ls

Configure environment with your license credentials:

services:
  pipe-pop:
    image: preterag/pipe-pop:latest
    container_name: pipe-pop
    restart: unless-stopped
    ports:
      - "7999:7999/tcp"
      - "7998:7998/udp"
    environment:
      - NODE_NAME=edge-myregion-01
      - LICENSE_KEY=***
      - OPERATOR_EMAIL=you@example.com
    volumes:
      - ./pipe-data:/data
    mem_limit: 2g
docker compose up -d
docker compose logs -f pipe-pop

4. Verify delivery & monitor epochs

Healthy logs show registration handshake, cache sync, and periodic heartbeat/epoch messages. Confirm your node appears online in the operator dashboard, then:

CheckFrequencyHealthy signal
Dashboard online statusDaily first weekGreen, uptime % climbing
Epoch rewards postingEach epochNon-zero PIPE accrual
Bandwidth graphsWeeklySpikes = real CDN traffic reaching you
Container restartsWeeklyZero unexplained loops
Bandwidth reality: a CDN node serves real content spikes. On metered connections this can get expensive fast — unmetered links only.

5. Ongoing operations

- Keep the node patched via Watchtower or scheduled pulls

- PIPE accrues per epoch; decide your conversion cadence (post-TGE volatility argues for regular selling vs accumulating)

- Watch the Jito restaking integration: staked PIPE delegated toward performing PoPs may become a second yield surface for operators who hold rather than sell

- If monthly reward value < hardware cost two cycles running, decommission — the spreadsheet decides, not sunk-cost feelings

Tools used in this playbook

This guide contains referral links to some of the services mentioned. They cost you nothing and fund more testing. See disclosure.