Home > Engineering > Infrastructure > P2P building blocks

P2P building blocks

The distributed-data and networking primitives at the heart of the stack — the Hypercore family for storage, plus the networking, crypto, and availability layers built around it. These are usable directly, on their own: many projects depend on them without ever touching Pear.

Storage

• Hypercore — append-only, secure log; the core primitive.
• Hyperbee — B-tree key-value store on a Hypercore.
• Hyperdrive — file system over Hypercores.
• Corestore — manages many Hypercores under one backend.
• Autobase — multi-writer log built from many Hypercores.
• Hyperblobs — blob storage on a Hypercore.

Networking & transport

• HyperDHT — the distributed hash table peers find each other through.
• Hyperswarm — topic-based peer discovery and connection.
• UDX — fast UDP-based transport.
• secret-stream — end-to-end encrypted Noise streams.
• protomux — multiplexed protocol channels over one stream.

Crypto & security

• The key model — keypairs, discovery keys, and encryption keys.
• The P2P security model — how trust and encryption work across the stack.

Availability & relays

• blind-peering — peers that replicate without reading content.
• seeders — always-on availability for cores.
• blind-relay — relays connections without seeing payloads.
• dht-relay — reach the DHT from environments that can’t speak it directly.

Sources

• Docs: docs.pears.com/building-blocks
• Repo: github.com/holepunchto