Waku
Protocolo P2P
Comunidad
Detalles
Licencia Permissive (Apache-2.0). https://github.com/logos-messaging/logos-delivery (Nim node, C library, CLI); the specifications are at https://github.com/logos-co/logos-lips
Estado de Desarrollo 🟢 Activo
Propietario Logos (the project's Logos Delivery and Logos Messaging repositories are under the logos-messaging organisation; the cited sources do not name the legal entity or steward)
Órgano de Gobierno Not described in the cited sources; the code and specifications sit under the Logos organisations on GitHub
País Not stated by the project.
Año de Inicio 2020
Stack Nim; libp2p; a C library and CLI; JavaScript client in a separate repository; specifications in the Logos LIPs repository
Financiamiento Not stated by the project.
Última Investigación 29 oct 2026
Protocolo P2P Atributos
Orígenes Private peer-to-peer communication for applications, built on libp2p; the implementation has since moved into the Logos programme's repositories
Base de Datos N/A
Lenguaje de Consulta N/A
Formatos de Datos Messages as defined in the specifications in the Logos LIPs repository, carried over libp2p
Edición Colaborativa en Vivo N/A
Edición de Texto Enriquecido N/A
Soporte Móvil Library-level: the C library allows embedding in mobile applications; no application
Soporte Web Through a separate JavaScript client (logos-delivery-js), which the README points to for browser testing
Aplicaciones Nativas Library-level (a node, a C library and examples)
Términos Free and open source (Apache-2.0)
Fondos Not stated by the project.
Basado En libp2p; the README says it implements the messaging specifications in the Logos LIPs repository
Arquitectura P2P libp2p peer-to-peer network: nodes join through bootstrap nodes; the cited sources do not describe message routing further
Red de Superposición Yes: a libp2p overlay with its own bootstrap and discovery
Direccionamiento por Contenido No.
Local-First Not a local-first data layer; it is a messaging transport that applications use
Cifrado de Extremo a Extremo (E2EE) Transport-level privacy is built in; end-to-end message encryption is provided by applications or companion protocols, per the specifications; the cited sources do not give details
Biblioteca de CRDTs No: not a CRDT library.
Tolerancia a Fallos Bizantinos Not stated by the project.
Firma Messages can be signed by senders in the specifications; the cited sources do not give details
Permisos Open relay network with application-level controls; the cited sources do not describe a built-in permission model
Compatibilidad con la Web Semántica N/A: no RDF, JSON-LD or SPARQL layer.
Contrato Inteligente N/A: no ledger or smart-contract component.
Posición en la Pila del Protocolo Application and messaging layer built on libp2p
Incorporación de Activos/Valor None: no token or value-transfer mechanism.
Madurez del Protocolo / Estandarización Specifications are published as LIPs (Logos Improvement Proposals) in a repository; the implementation is at 0.x with regular releases; no standards-body involvement