Pear by Holepunch

Pear loads applications remotely from peers and allows anyone to create and share applications with peers.

Pear by Holepunch is a combined Peer-to-Peer (P2P) Runtime, Development & Deployment tool.

Pear makes it possible to build, share and extend P2P applications using common Web and Mobile technology.

Herein is everything needed to create unstoppable, zero-infrastructure P2P applications for Desktop, Terminal & Mobile (soon).

Welcome to the Internet of Peers

  – Holepunch, the P2P Company

Table of Contents

References

• Command-Line-Interface (CLI)
• Application-Programming-Interface (API)
• Application Configuration

Guides

• Getting Started
• Starting a Pear Desktop Project
• Making a Pear Desktop Application
• Starting a Pear Terminal Project
• Making a Pear Terminal Application
• Sharing a Pear Application
• Marking a Release

Building blocks

The following structural components form the backbone of the Pear Ecosystem.

1. hypercore: A distributed, secure append-only log for creating fast and scalable applications without a backend, as it is entirely peer-to-peer.
2. hyperbee: An append-only B-tree running on a Hypercore that provides key-value store API, with methods for inserting and getting key/value pairs, atomic batch insertions, and creation of sorted iterators.
3. hyperdrive: A secure, real-time distributed file system that simplifies P2P file sharing that provides an efficient way to store and access data across multiple connected devices in a decentralized manner.
4. autobase: An experimental module used to automatically rebase multiple causally-linked Hypercores into a single, linearized Hypercore for multi-user collaboration.
5. hyperdht: A DHT powering Hyperswarm. Through this DHT, each server is bound to a unique key pair, with the client connecting to the server using the server's public key.
6. hyperswarm: A high-level API for finding and connecting to peers who are interested in a "topic."

Helpers

Helper modules can be used together with the building blocks to create cutting-edge P2P tools and applications.

1. corestore: A Hypercore factory designed to facilitate the management of sizable named Hypercore collections.
2. localdrive: A file system interoperable with Hyperdrive.
3. mirrordrive: Mirror a hyperdrive or a localdrive into another one.
4. secretstream: SecretStream is used to securely create connections between two peers in Hyperswarm.
5. compact-encoding: A series of binary encoding schemes for building fast and small parsers and serializers. We use this in Keet to store chat messages and in Hypercore's replication protocol.
6. protomux: Multiplex multiple message oriented protocols over a stream.

Tools

The following tools are used extensively employed in the day-to-day development and operation of applications built on Pear

Tools	Description
Hypershell	A CLI to create and connect to P2P E2E encrypted shells..
Hypertele	A swiss-knife proxy powered by HyperDHT.
Hyperbeam	A one-to-one and end-to-end encrypted internet pipe.
Hyperssh	A CLI to run SSH over the HyperDHT.
Drives	CLI to download, seed, and mirror a hyperdrive or a localdrive.

Hypercore

• The session and snapshot methods for providing multiple views over the same underlying Hypercore, which simplifies resource management.
• A truncate method for intentionally creating a new fork, starting at a given length. We use this method extensively in autobase, as described below.
• An improved fork detection in the replication protocol, to improve resilience.
• Optional on-disk encryption for blocks (in addition to the existing transport encryption).
• The storage layer now uses a write-ahead log to ensure that power loss or unexpected shutdown cannot lead to data corruption.

Hyperswarm

• An improved UDP holepunching algorithm that uses arbitrary DHT nodes (optionally selected by the connecting peers) to proxy necessary metadata while being maximally privacy-preserving.
• A custom-built transport protocol, UDX, that takes advantage of the holepunching algorithm to avoid unnecessary overhead (it doesn't include handshaking since holepunching takes care of that, for example). It's blazing fast.
• A simplified DHT API that closely resembles NodeJS's net module, but using public keys instead of IP addresses.

Hyperdrive

• Uses Hyperbee internally for storing file metadata
• Major API simplification. Instead of mirroring POSIX APIs, the new API better captures the core requirements of P2P file transfer.
• Auxiliary tools, localdrive and mirrordrive, that streamline import/export flows and make it easy to mirror drives to and from the local filesystem. We use these every day when deploying Keet.

Autobase (experimental)

Hypercores are single-writer data structures, but collaboration is crucial. autobase is an experimental module that allows to turn many Hypercores, owned by different people, into a single 'virtual' Hypercore. In Keet, every member of a room has their input Hypercore where they write chat messages, and Autobase merges these into the linear view members see on the screen.

As Autobase's output shares the familiar Hypercore API, it is possible to plug it into higher-level modules like Hyperbee and Hyperdrive, getting a multi-user collaboration with little additional effort.

Autobase is still experimental and is likely to change significantly in the near future.

Stability indexing

Throughout the documentation, indications of a module's stability are provided. Some modules are well-established and used widely, making them highly unlikely to ever change. Other modules may be new, experimental, or known to have risks associated with their use.

The following stability indices have been used:

Stability	Description
stable	Unlikely to change or be removed in the foreseeable future.
experimental	New, untested, or have known issues.
deprecated	Being removed or replaced in the future.
unstable	May change or be removed without warning.

Stability overview

Module	Stability
hypercore	stable
hyperbee	stable
hyperdrive	stable
autobase	experimental
hyperswarm	stable
hyperdht	stable

Any part of a module (method, event, or property) that is not documented as part of that module's public API is subject to change at any time.