The PIPE roadmap outlines steps to increase the scalability, security, and speed of decentralized storage and data transfers.
Since the goal of PIPE is to solve real storage problems, our technical roadmap is closely tied to efforts to speed up market adoption. 


Things to make and do




*For now, only beta testers can access private GitHub repos.


PIPE Library, also functioning as the base for the core PIPE node (pipe-cli).



The Freighter Rust library is a decentralized messaging system for large-scale data units.


PIPE node

CLI that uses pipe-rs to run as a full node on desktops or servers.


WASM for browser nodes

WASM port for freighter-rs to run a node from a web browser.

One-pager PDF


Hybrid cryptography library

A cryptography library and protocol that allows the user or device to use any algorithm without changing their code.


Fast streaming commands

Sister project for PIPE to provide a high level command system that’s fast and flexible.



This repository contains a web application which demonstrates how PIPE can be used in an application.


Network visualizer

This visualizer shows how the PIPE network works and helps with analysis and debugging.

pipe-monorepo/Network Visualizer


Browser SSL


*For now, only beta testers can access private GitHub repos.

Connection system update

This ZeroSSL certbot wrapper adds DataChannels (a subset of WebRTC) to PIPE to make it easier and more decentralized for browsers with web-based nodes to connect through SSL.

Two-pager PDF


Smart contracts


Paid storage function

Smart contract to enable payments and network storage/receivability.

Status: Smart contracts have been written and are awaiting the IOTA/Shimmer EVM.

Conditional credits

Locking storage credit to a specific node, device or channel. This enables the prepay function, so that anyone can use PIPE without handling cryptocurrency.

Status: Behavior is defined, but implementation depends on specifics of SC integration.

Staking mechanism

Nodes that are expected to be online put up PIPE tokens as a guarantee that they will handle data correctly and meet uptime requirements.

Status: Behavior is defined, but implementation depends on specifics of SC integration.

Native token settlement

When settling smart contracts on IOTA/Shimmer, it is easier for users to pay fees with PIPE tokens. This is a huge improvement over Ethereum-based solutions that always require the ETH base token in a wallet for gas fees.

Status: Behavior is defined, but implementation depends on specifics of SC integration.

Reputation calculation

The calculation of reputation determines a node’s score on specific characteristics. This improves its properties for specific use cases and allows its storage to be properly priced. Uptime, node age, ping time, and retrieval score are examples of reputation factors.

Status: Behavior defined.

Clean exit strategy

A storage provider that is no longer able or willing to store chunks can transfer the commitment for the chunks they store to other parties of comparable quality and reputation. Nodes that have correctly transferred all of their chunks can walk away with all of their initial collateral intact.
This provides insurance for nodes to accept long-term contracts (say, 1 to 100 years), and guarantees users that there will be enough nodes in the future that store their data.

Status: Behavior defined.

Self-healing network

When a chunk goes missing, PIPE will not only slash a node, but will also recover the chunk using the slashed stake as an incentive and features from Erasure Coding. After restoring the data, it places the chunk with a new storage provider of comparable quality and reputation – all without user-intervention.

Status: Behavior defined.

Market adoption


Wallet API

Integrate existing desktop/mobile wallets into PIPE to manage private keys, storage and tokens.

PIPE is wallet agnostic, meaning it can integrate with any app’s key manager instead of requiring a separate wallet.


HUB makes it simple to manage thousands or millions of decentralized data channels. HUB modules organize, validate, and exchange data flowing through PIPE with ease.

About HUB

Onboard node partners

We incentivize solid storage providers to offer storage on the PIPE network to kickstart the storage network.

One of our tokenization design goals is to make it appealing to provide useful storage on PIPE. We’re talking to storage providers to figure out what the best incentives are.

Onboard data partners

PIPE is designed to store meaningful data for real-world use cases. We prioritize onboarding high volume, high value use cases in order to foster the growth of the PIPE ecosystem and demonstrate the real-world applicability of decentralized technology.

We’re discussing initial onboarding demands with a browser company, various data-oriented cryptocurrencies, and decentralized big data projects.


PIPE 2.0


Network optimization

PIPE 1.0 is built as a performant, highly scalable, affordable, and quantum-resistent decentralized network.
PIPE 2.0 is currently in research and will improve performance and affordability. It aims to reduce node-to-node overhead while maintaining plausible deniability by establishing neighbor connections on-demand. This will enable parallel downloads, greatly increasing download speeds for large amounts of chunks.