Hyperdrive

Decentralized Data Protocol

POSIX-like filesystem abstraction built atop Hypercore and Hyperbee, providing files, directories, and path-based access semantics with the same cryptographic verifiability and peer-to-peer replication properties. Member of the Holepunch suite.

Comunidade

Links

Visitar Comunidade

Detalhes

Licença

Open source — MIT (github.com/holepunchto/hyperdrive)

Status de Dev 🟢 Ativo

Detalhe do Status de Dev

Released / Active (production use in Holepunch ecosystem)

Proprietário

Holepunch (same team as Hypercore and Hyperbee)

País

International (distributed team)

Ano de Início 2016

Stack

JavaScript / Node.js (reference implementation); WebAssembly builds for browser

Financiamento

Tether-backed via Holepunch

Última Investigação 1 de jul. de 2026

Domínios de Caso de Uso

Platform Evolution & Sovereignty

Decentralized Data Protocol Atributos

Origins

Distributed file sharing (originated in dat project for scientific dataset distribution)

Database

Hyperbee-indexed file metadata plus Hypercore-backed file content blocks

Query Language

POSIX-like filesystem API (read, write, stat, readdir, glob); supports streaming reads for large files

Data Formats

Arbitrary file content (binary or text); path-keyed metadata in Hyperbee

Collaborative Live Editing

Single-writer (multi-writer scenarios require Autobase)

Rich Text Editing

N/A (filesystem library, not editor)

Mobile Support

Yes (via Pear runtime)

Web Support

Yes (WebAssembly builds)

Native Apps

Yes (consumed by Beaker Browser historically, Pear runtime applications today)

Terms

Open Source / Free — MIT License

Funds

Not separately disclosed

Based On

Hypercore (block storage); Hyperbee (metadata index); POSIX filesystem semantics

P2P Architecture

Inherits Hypercore's P2P model with hole-punching peer discovery via Hyperswarm

Overlay Network

Inherits from Hypercore (Hyperswarm-based)

Content Addressing

Public-key addressing per Hyperdrive; file paths are keys in the underlying Hyperbee

Local-First

Yes — files accessible offline; replication is opportunistic

E2EE

Transport encryption via Noise; content-layer encryption application-level

CRDTs Lib

N/A (single-writer; Autobase for multi-writer)

Byzantine Fault Tolerance

Single-writer signature model (no consensus)

Signature

Inherits Hypercore Ed25519 signatures

Permissions

Public-key gated (Hyperdrive-level); no per-file ACL natively

Semantic Web Compatibility

N/A (filesystem abstraction; content-agnostic)

Smart Contract

N/A

Protocol Stack Position

L4 Data & Semantic

Asset / Value Embedding

None — filesystem abstraction with no native token

Protocol Maturity / Standardization

Released / Production library; no formal standardization; community-driven evolution