Pipe Network Documentation

Scope. This documentation covers Pipe Storage and Firestarter nodes only. It does not list or document other products.

These pages describe the current mainnet storage system and how independently operated Firestarter nodes participate. They run the lattice-node executable, configured with LATTICE_* settings. A compatible lattice-node source or binary is provided with the enrollment invite, by Pipe Network operations. This documentation set does not publish a clone URL.

Running a Firestarter node requires 10,000 PIPE staked through LovePIPE. Individual nodes receive no rewards or payouts. Operators contribute capacity and availability to support the protocol over the long term. Removing node reward obligations supports the protocol's long-term sustainability.

Enrollment is invite-only. There is no public waitlist and no self-serve enrollment form. To inquire about running a node, email hello@pipe.network. Compatible lattice-node software is supplied with the invite. Ordinary public admission also requires the 10,000 PIPE LovePIPE position and a complete UTC qualification month.

See Tokenomics for participation requirements and optional treasury policy.

Start Here

• Welcome: scope and participation.
• Introduction: overview of Pipe Storage and Firestarter nodes.
• Architecture: gateways, control plane, Firestarter nodes, and Solana integration.
• Quickstart: choose customer storage or Firestarter node participation.
• Pipe Storage: S3-compatible access, customer credits, and storage behavior.
• Storage API Quickstart: fund an account, create credentials, and upload an object.

Firestarter Nodes

• Mainnet Firestarter Nodes: invite-gated enrollment, identity helper, and qualification.
• Wallet and LovePIPE Setup: node identity and the 10,000 PIPE requirement.
• Node Operations: health, capacity, and troubleshooting.
• Eligibility Checklist: qualification and ongoing participation.
• LovePIPE: staking, wallet positions, and storage account access.

Protocol and Economics

• Tokenomics: no individual node rewards, LovePIPE staking, and optional treasury policy.
• Tokenomics Operations Spec: eligibility parameters and implementation boundaries.
• Performance and Integrity: storage verification and node eligibility.

Other Documentation

• Historical Whitepaper: dated publication, separate from current mainnet policy.
• Whitepaper to Current Mainnet: what changed versus the archived 2025 PDF.

Contributing

Submit documentation changes through a pull request. The wallet helper and its tests require Python's cryptography package. Run the same checks as CI from the repository root:

python3 docs/scripts/check_mainnet_docs.py
python3 docs/scripts/check_markdown_links.py
python3 docs/scripts/check_tokenomics_params_sync.py
python3 -m unittest discover -s tests -p 'test_*.py'
cargo fmt --check
cargo test

Run the documentation server locally with cargo run and open http://localhost:3000. Markdown is rendered under /docs/; PDF and JSON links return their original bytes. /static/ serves raw files from the public documentation tree. Maintainer notes in internal/ are outside that tree.

For production deployment and service management, see deploy/README.md in the source repository. Set BIND_ADDR to override the default 0.0.0.0:3000 listener.

Refer to the relevant Pipe Network repositories for license information.

Last updated: September 27, 2026.

← Back to Index