BitTorrent Mainline DHT

Infraestructura P2P

The Kademlia-based distributed hash table (DHT) used by BitTorrent clients as a serverless, decentralized tracker for peer discovery. Defined by BEP-5 (peer-contact storage) and extended by BEP-44 (arbitrary mutable/immutable data storage). Every BitTorrent client embedding DHT becomes a node, collectively forming the largest volunteer DHT network on the internet. Used as a transport substrate by multiple unrelated systems including Hyperswarm, Hubert (Blockchain Commons), and other decentralized storage and coordination tools.

Comunidad
Enlaces
Visitar Sitio Web Ver esta herramienta en el grafo Sugerir una corrección

Detalles

Licencia Permissive (BEP specifications are open; reference implementations under various licenses; libtorrent reference: BSD-1-Clause; multiple open-source implementations in Go, Python, JavaScript, Rust)
Estado de Desarrollo 🏁 Final
Detalle del Estado de Desarrollo Released / Mature (BEP-5 Final standard; BEP-44 Accepted; actively deployed in all major BitTorrent clients; ongoing ecosystem implementations)
Propietario BitTorrent Community / TokTok / open standard (BEP process governed by BitTorrent.org; original Mainline DHT designed by BitTorrent Inc.; now effectively community-maintained)
Órgano de Gobierno BitTorrent.org BEP process (community-maintained; original Mainline DHT designed by BitTorrent Inc.)
País International (distributed volunteer network; BEP process historically managed by BitTorrent Inc., USA; now community-governed)
Año de Inicio 2005
Stack Language-agnostic (BEP-5 protocol spec over UDP; implementations in C++ (libtorrent), Go (anacrolix/torrent), JavaScript (webtorrent/bittorrent-dht), Python, Rust; BEP-44 adds ed25519 for mutable data)
Financiamiento None / Volunteer (DHT network is self-sustaining; nodes are volunteer; no central entity funds the network)
Última Investigación 1 jul 2026

Vista de topología

Esta herramienta en el centro y lo que se relaciona directamente con ella. Cada línea nombra el tipo de relación.

Vista de topología: BitTorrent Mainline DHTEsta herramienta en el centro y lo que se relaciona directamente con ella. Cada línea nombra el tipo de relación.BitTorrentMainline DHTHubert (Base de)HubertHyperswarm (Base de)HyperswarmPKARR (Base de)PKARRPubky Protocol (Base de)PubkyProtocol

Abrir en el Explorador de grafo

Dominios de Caso de Uso

Evolución de Plataformas y Soberanía

Capacidades

Almacenamiento local-first Autoalojable Funciona sin conexión / en malla

Infraestructura P2P Atributos

Orígenes Distributed peer tracking (designed to eliminate dependence on centralized BitTorrent trackers; "trackerless" torrent support enabling peer discovery without any central server)
Base de Datos N/A (DHT is a distributed key-value routing table, not a database; nodes store routing state and temporarily cache peer-contact records, not persistent data)
Formatos de Datos Bencoding (BEP-3 standard binary format for all DHT messages); compact peer info (6-byte IPv4 address+port records); BEP-44 values (arbitrary bytes up to 1000B; ed25519-signed for mutable data)
Soporte Móvil Yes (embedded in mobile BitTorrent clients; Tox and other mobile apps use DHT)
Soporte Web Partial (WebRTC-based DHT implementations for browser environments; not native to standard Mainline DHT which requires UDP)
Aplicaciones Nativas Yes (embedded in all major BitTorrent desktop clients: qBittorrent, Transmission, Deluge, libtorrent-based clients)
Términos Free (open protocol; no commercial terms; all node operation is volunteer)
Fondos None
Basado En Kademlia DHT (Maymounkov & Mazières 2002 paper); BEP-5 (peer-contact storage spec); BEP-44 (arbitrary data storage extension with ed25519 signing)
Arquitectura P2P Kademlia DHT (XOR metric for key-node distance; 160-bit node IDs; k-buckets routing table; iterative lookup converges in O(log n) hops)
Red de Superposición Global (single shared Mainline DHT network; all nodes participate in same overlay; estimated 16-28M concurrent nodes as of 2013 measurements)
Direccionamiento por Contenido Yes (BEP-44 mutable values addressed by ed25519 public key; immutable values by SHA-1/SHA-256 hash; torrent peers addressed by info_hash)
Local-First N/A (routing infrastructure; data transits or is stored ephemerally; not a local-first storage system)
Cifrado de Extremo a Extremo (E2EE) No (DHT messages are unencrypted at the protocol level; BEP-44 signed data is authenticated but not encrypted; application-layer encryption is separate)
Tolerancia a Fallos Bizantinos No (probabilistic resilience; no formal Byzantine consensus; vulnerable to Sybil and routing table poisoning attacks as documented in security assessments)
Firma Ed25519 (BEP-44 mutable data items; signatures bind value to public key; SHA-1 info_hashes for immutable lookups)
Permisos Open (any node may participate; BEP-44 mutable values writable only by holder of corresponding private key; immutable values content-addressed)
Madurez del Protocolo / Estandarización De Facto Standard (BEP-5 Final status; BEP-44 Accepted; implemented in all major BitTorrent clients and adopted by unrelated systems (Hyperswarm, Hubert); not submitted to IETF or other formal body; BEP process is community governance)
Función de Infraestructura Distributed key-value routing (peer discovery for BitTorrent; general-purpose DHT substrate for any application requiring decentralized key-value lookup or arbitrary data storage via BEP-44)
Modelo de Amenazas Sybil attacks; routing table poisoning; eclipse attacks; DHT crawling/enumeration; unencrypted metadata exposure
Modelo de Nodo Voluntario Embedded (every BitTorrent client with DHT enabled is automatically a node; no dedicated relay class; nodes self-organize without incentive)
Visibilidad del Tráfico Metadata visible (DHT messages are unencrypted; node IDs, info_hashes, and IP addresses of peers are observable by any participating node or network monitor)
Escala de Despliegue Activo ~16-28M concurrent nodes (2013 academic measurement; Mainline DHT is the largest publicly deployed DHT; exact current count untracked but embedded in hundreds of millions of BitTorrent client installations worldwide)

Relaciones

Cómo se conecta esta herramienta con otras herramientas y organizaciones, según relaciones revisadas por el responsable de datos de OpenHaven. Describen cómo se conectan los proyectos, no su calidad.

Base de