Hubert
P2P Infrastructure
Comunidade
Links
Detalhes
Licença BSD-2-Clause Plus Patent License — hubert-rust reference implementation
Status de Dev 🟢 Ativo
Detalhe do Status de Dev Released — alpha/early production; CLI tool (hubert-rust) and FROST-specific CLI demonstrated; reference implementation public
Proprietário Blockchain Commons LLC (not-for-profit benefit corporation founded by Christopher Allen, April 25, 2019; Berkeley, California). Specification author: Wolf McNally, Lead Researcher
País USA (Berkeley, California)
Ano de Início 2025
Stack Rust (hubert-rust); IPFS via Kubo daemon HTTP RPC; BitTorrent Mainline DHT via embedded BEP-44 client
Financiamento Blockchain Commons donations and patron sponsorships
Última Investigação 1 de jul. de 2026
P2P Infrastructure Atributos
Origins Blockchain Commons; designed to enable autonomous coordination of cryptographic objects (Gordian Clubs, FROST ceremonies) without trusted infrastructure
Database Backend-dependent — DHT (in-memory distributed), IPFS (Kubo daemon storage), Server (configurable centralized)
Data Formats Gordian Envelopes wrapped in GSTP (Gordian Sealed Transaction Protocol) encryption; CBOR (via dCBOR)
Mobile Support Library-level — Rust libraries (hubert-rust, frost-hubert-rust) cross-compile to mobile; mobile-friendly given small message size on the DHT backend; no first-party mobile app yet
Web Support Library-level — HTTP transport possible against IPFS Kubo and other backends; web bindings TBD
Native Apps CLI tools — hubert-cli, FROST ceremony CLI demos
Terms Open source, BSD-2-Clause Plus Patent License
Funds Unknown — funded under Blockchain Commons general operating budget; specific Hubert allocation not separately published
Based On Gordian Envelope; GSTP; ARIDs (Apparently Random Identifiers); HKDF (RFC 5869); BitTorrent Mainline DHT (BEP-44); IPFS / IPNS; Kubo
P2P Architecture Layered service over existing P2P infrastructure (Mainline DHT and IPFS); not a new node network but a coordination semantics layer above them
Overlay Network BitTorrent Mainline DHT; IPFS DHT; Hybrid (automatic backend selection by size)
Content Addressing ARID-derived storage keys (HKDF-derived from ARID; ARID never exposed to network); IPFS CIDs for large payloads with encrypted DHT references
Local-First Yes — Hubert nodes can run locally; supports air-gapped publication and retrieval
E2EE Yes — all payloads GSTP-encrypted; reference encryption hides IPFS ARIDs from DHT observers; storage backends see only encrypted blobs
Byzantine Fault Tolerance Inherits from underlying DHT/IPFS substrate; write-once semantics eliminate race conditions and ensure message immutability
Signature Per-payload cryptographic signing via Envelope + GSTP; integrates with FROST threshold signatures
Permissions ARID-based addressing — only parties knowing the ARID (out-of-band) can compute the storage location; permits in payload Envelopes provide further access control
Protocol Maturity / Standardization Alpha release Oct 2025; BCR-2025-006 specification; reference Rust implementation deployed
Infrastructure Function Asynchronous coordination service — write-once dead-drops for multi-party cryptographic protocol messages; query-addressable storage abstraction over diverse backends
Threat Model Untrusted storage networks; metadata privacy from DHT observers (ARIDs hidden via HKDF derivation; IPFS ARIDs hidden from DHT via reference encryption); does not provide forward secrecy for long-running conversations (would require ratcheting layered above)
Volunteer / Node Model Inherits from underlying substrates — BitTorrent Mainline DHT (volunteer global network), IPFS (volunteer + paid pinning); Hubert itself is a client/library, not a separate node network
Traffic Visibility Storage operators see encrypted blobs at HKDF-derived storage keys; ARIDs themselves never exposed; HTTPS for IPFS Kubo RPC
Active Deployment Scale Small — recently released; ecosystem in early adoption phase