Hypercore
Protocolo de Dados Descentralizado
Comunidade
Detalhes
Licença Open source — MIT (github.com/holepunchto/hypercore)
Status de Dev 🟢 Ativo
Detalhe do Status de Dev Released / Mature (production-deployed in Beaker Browser, Pear runtime, Holepunch Keet app)
Proprietário Holepunch (formerly Hypercore Protocol / dat); core development by Mathias Buus and team; supported by Tether (commercial relationship since 2023 rebrand)
Proprietário - Lista
- Holepunch
- Tether Holdings
Órgão de Governança Company-controlled (Holepunch; commercial relationship with Tether since the 2023 rebrand)
Órgão de Governança - Lista
- Holepunch
País International (distributed team; Holepunch entity incorporated in connection with Tether)
Ano de Início 2013
Stack JavaScript / Node.js (primary reference implementation); also Rust bindings (hypercore-protocol-rs); WebAssembly builds for browser use; modular component architecture
Financiamento Tether Holdings (commercial backing since 2022–2023 rebrand to Holepunch); prior funding via dat project grants and various foundation support
Financiamento - Lista
- Tether Holdings
Última Investigação 1 de jul. de 2026
Protocolo de Dados Descentralizado Atributos
Proprietário - Lista
- Holepunch
- Tether Holdings
Origens Distributed data / Peer-to-peer file sharing (evolved from dat project for scientific dataset sharing; designed to enable verifiable partial replication without centralized servers)
Banco de Dados Append-only log (each Hypercore is itself the data structure; persistence via underlying storage adapter — typically random-access-file on disk, random-access-memory in tests, or random-access-idb in browsers)
Linguagem de Consulta N/A (Hypercore is a log structure with sequence-number access; higher-level structures like Hyperbee provide query semantics)
Formatos de Dados Arbitrary binary blocks (Hypercore stores opaque blocks; higher-level structures impose schemas); blocks indexed by sequence number; Merkle tree of block hashes for verification
Edição Colaborativa em Tempo Real Single-writer per Hypercore (collaborative editing requires Autobase or application-level CRDT layered on multiple Hypercores)
Edição de Texto Rico N/A (application-layer concern)
Suporte Móvel Yes (Holepunch ecosystem deploys to iOS and Android via Pear runtime; Keet messaging app published for both platforms)
Suporte Web Yes (browser builds via WebAssembly; historically deployed in Beaker Browser; WebRTC-based transport via Hyperswarm for browser peers)
Aplicativos Nativos Yes (Keet messaging app for desktop, iOS, Android; Pear runtime for building native P2P applications)
Termos Open Source / Free — MIT License; ecosystem includes commercial Tether-funded development
Financiamento - Lista
- Tether Holdings
Fundos Tether investment amount not publicly disclosed; Holepunch operates as Tether-affiliated entity since 2022
Baseado Em Merkle DAG concepts (cryptographic verification of partial replication); BitTorrent-style swarm replication; dat protocol predecessor (Hypercore is the successor specification)
Órgão de Governança - Lista
- Holepunch
Arquitetura P2P True P2P with hole-punching: peers connect directly after Hyperswarm DHT-based discovery; relays only used for NAT traversal hole-punching, not for data transit; no centralized infrastructure required for data movement
Rede de Sobreposição Hyperswarm (DHT-based peer discovery and connection management; built atop UDP with TCP fallback)
Endereçamento por Conteúdo Public-key addressing per Hypercore (each Hypercore identified by Ed25519 public key); blocks within a Hypercore addressed by sequence number; integrity via Merkle tree of block hashes
Local-First Yes — Hypercores can be created, written to, and read entirely offline; peer replication is opportunistic; data persists locally regardless of network state
Criptografia de Ponta a Ponta (E2EE) Transport encryption via Noise Protocol Framework (all peer-to-peer connections encrypted by default); content-layer encryption is application-level concern (Hypercore data is technically public to anyone who knows the public key)
Biblioteca de CRDTs Autobase (Holepunch's CRDT-like primitive for multi-writer scenarios built atop multiple Hypercores); external CRDT libraries can also be layered on top
Tolerância a Falhas Bizantinas Single-writer model (no consensus required within a Hypercore; signatures prevent tampering); multi-writer via Autobase uses convergent eventual consistency rather than Byzantine consensus
Assinatura Ed25519 signatures (each block signed by the Hypercore's owning key; Merkle tree provides incremental verifiability for partial replication)
Permissões Public-key gated (whoever holds the Hypercore public key can read; whoever holds the secret key can write); no native ACL; access control layered at application level
Compatibilidade com a Web Semântica N/A — Hypercore is content-agnostic at the protocol level; semantic-web-compatible data can be stored as block payloads but is not a protocol concern
Contrato Inteligente N/A (no smart contract capability)
Posição na Pilha de Protocolo L3.2 Data & Semantic (data primitive); often composed with L3.1 (Hyperswarm) for transport
Incorporação de Ativo / Valor None — Hypercore is a content-addressed data protocol with no native token or economic incentive layer. Tether's commercial backing of Holepunch is organizational, not protocol-level
Maturidade / Padronização do Protocolo Released / Production-deployed; not submitted to formal standards body; specification maintained at github.com/holepunchto; community-driven evolution
Relacionamentos
Como esta ferramenta se conecta a outras ferramentas e organizações, a partir de relacionamentos revisados pelo responsável pelos dados do OpenHaven. Descrevem como os projetos se conectam, não a qualidade deles.
- Administrado por
- Holepunch
- Baseado em
- Desenvolvido por
- Holepunch
- Tether Holdings
- Financiado por
- Tether Holdings
- Membro da suíte
- Holepunch Suite
- Compõe-se com
- Armazenamento para