Nostr

Protocolo P2P

Open protocol for decentralized, censorship-resistant social networking using cryptographically signed messages distributed via relay servers

Comunidad
Enlaces
Visitar Comunidad

Detalles

Licencia Public Domain (unlicensed)
Estado de Desarrollo 🟢 Activo
Detalle del Estado de Desarrollo Released / Active — widely deployed open protocol defined by NIPs; 250+ client apps and relay implementations; NIP-01 core stable; active NIP development for extensions including private DMs (NIP-17), file storage (NIP-96), and remote signing (NIP-46)
Propietario fiatjaf (pseudonymous creator, identified as Giovanni Torres Parra) / Community-maintained
Órgano de Gobierno None (community NIP process; no formal standards body or legal entity)
País Brazil (creator location) / International
Año de Inicio 2020
Stack Multi-language (JavaScript, Rust, Go, C#, Python implementations)
Financiamiento Donations (Jack Dorsey $245k BTC in Dec 2022 direct to fiatjaf; $10M to OpenSats in May 2023)
Última Investigación 15 ene 2026

Dominios de Caso de Uso

Comunicación Identidad y Confianza

Capacidades

Cifrado de extremo a extremo Federación de protocolos Audiencias basadas en consentimiento Identidad soberana

Protocolo P2P Atributos

Orígenes Social networking / Microblogging
Base de Datos Relay-specific (typically SQLite, PostgreSQL)
Lenguaje de Consulta Custom (Nostr filters/subscriptions via WebSocket)
Formatos de Datos JSON (Nostr Events)
Edición Colaborativa en Vivo N/A (broadcast protocol, not collaborative editing)
Edición de Texto Enriquecido Application-level (clients can support Markdown, etc.)
Soporte Móvil Yes (Damus, Amethyst, etc.)
Soporte Web Yes (web clients available)
Aplicaciones Nativas Yes (mobile and desktop clients)
Términos Self-hosting (relays) + Free relays + Paid relays
Fondos $10.25M+ (cumulative: ~$245k BTC direct to fiatjaf Dec 2022 + $10M to OpenSats May 2023)
Basado En N/A (original protocol)
Arquitectura P2P Relay-based (WebSocket relays, not pure P2P)
Red de Superposición User-defined (clients choose which relays to use)
Direccionamiento por Contenido Event-based (events identified by hash)
Local-First N/A (relay-dependent, not local-first)
Cifrado de Extremo a Extremo (E2EE) Supported via NIPs (NIP-04, NIP-44 for encrypted DMs)
Biblioteca de CRDTs N/A (append-only event log, not CRDTs)
Tolerancia a Fallos Bizantinos Event signatures (prevents tampering, not consensus)
Firma Schnorr signatures (secp256k1, same as Bitcoin)
Permisos Relay-level (relays set their own acceptance rules)
Compatibilidad con la Web Semántica N/A (custom JSON schema)
Contrato Inteligente N/A (no smart contract capability)
Posición en la Pila del Protocolo Application-layer (built on TCP/IP)
Incorporación de Activos/Valor None — Nostr is a bare relay-and-client messaging protocol with no native token. Zaps (Lightning Network micropayments via NIP-57) are an optional application-layer convention layered on top of the protocol, not a protocol-native economic mechanism.
Madurez del Protocolo / Estandarización De Facto Standard (NIP process — community-driven specification via Nostr Implementation Possibilities; no formal standards body; wide adoption)