I2P
P2P Infrastructure
Comunidade
Links
Detalhes
Licença Public Domain + BSD-style licenses (majority public domain; some cryptographic routines BSD-licensed; GPL for some bundled apps)
Status de Dev 🟢 Ativo
Detalhe do Status de Dev Released (production; current stable version 0.9.67 as of 2025)
Proprietário I2P Project (volunteer collective, largely pseudonymous developers) / StormyCloud Inc. (supporting infrastructure since 2025)
País International (distributed, pseudonymous developer team; no single country)
Ano de Início 2003
Stack Java (primary I2P router implementation); C++ (i2pd lightweight implementation); multiple language bindings
Financiamento Donations only; OTF (onboarding support); StormyCloud Inc. (infrastructure support 2025)
Última Investigação 9 de mar. de 2026
P2P Infrastructure Atributos
Origins Freenet/Hyphanet (fork); IIP (Invisible IRC Project); mix network research; Kademlia DHT
Database Kademlia-based distributed network database (netDb) for routing metadata; no application-layer data store
Data Formats I2NP (I2P Network Protocol) messages; arbitrary application data encapsulated in garlic messages
Mobile Support No (desktop daemon; web console at localhost:7657)
Web Support Yes (web console interface accessible locally)
Native Apps Yes (Java router for Linux/macOS/Windows; i2pd C++ variant; Android via i2pd-android)
Terms Free (donation-funded; core project does not solicit donations directly)
Funds Unknown (donation amounts not publicly disclosed; OTF support amount undisclosed)
Based On Freenet (censorship-resistant storage concept); Kademlia DHT; mix network research; garlic routing extends onion routing
P2P Architecture Garlic routing (unidirectional tunnel pairs; packet-switched; multiple messages bundled per garlic); Kademlia DHT for peer discovery
Overlay Network Global (self-organizing network database; no central directory servers; rotating floodfill routers maintain netDb)
Content Addressing No (router-identity-addressed, not content-addressed; application-layer content addressing possible)
Local-First N/A (routing infrastructure; data transits encrypted tunnels, not stored at network layer)
E2EE Yes — three layers: garlic encryption (message delivery verification), tunnel encryption, inter-router transport encryption
Byzantine Fault Tolerance No (reputation-based peer selection; no Byzantine fault tolerant consensus)
Signature ElGamal/ECIES (encryption); Ed25519/DSA (signatures); X25519 (key exchange in ECIES-X25519 mode)
Permissions N/A (open routing; all I2P routers contribute to network)
Protocol Maturity / Standardization Community Standard (open specification, published protocol docs; no formal standards body)
Infrastructure Function Anonymous routing; Censorship circumvention (internal darknet focus)
Threat Model Mass surveillance; Traffic analysis; Targeted surveillance; Metadata exposure
Volunteer / Node Model Volunteer-operated (every I2P router automatically routes for others; no dedicated relay class)
Traffic Visibility No content (three-layer encryption); No metadata (unidirectional tunnels mean each router sees only previous/next hop)
Active Deployment Scale ~55,000 router nodes worldwide (Wikipedia/research, as of 2024-2025)