Hyphanet

P2P Protocols

Peer-to-peer platform for censorship-resistant, anonymous publishing and retrieval, continuously developed since 1999 under the name Freenet and renamed Hyphanet in June 2023. Operates as a decentralized distributed data store: each node contributes encrypted disk space, requests are routed across intermediaries using small-world network topology, and content is addressed by cryptographic keys (CHK for immutable data; SSK/USK for updatable namespaces). Supports two connection modes: darknet (trusted friends only — maximum anonymity) and opennet (random peers — easier bootstrapping). Neither inserters nor retrievers are exposed to the network. Plugin ecosystem supports freesites, forums (Freetalk), microblogging (Sone), and Web of Trust-based spam resistance.

Totalmente P2P Comunidade Risco de captura baixo

Links

Visitar Comunidade

Detalhes

Licença Open source

Status de Dev Released

Proprietário Hyphanet Project — independent community continuation of the original Freenet codebase, spun off from Freenet Project Inc. in March 2023; maintained by original Freenet developers. Ian Clarke (original architect, now with new Freenet); ongoing maintainers include community contributors.

País International

Ano de Início 1999

Stack Java

Financiamento Community, Donations

Última Investigação 15 de jan. de 2026

Domínios de Caso de Uso

Platform Evolution & Sovereignty

Affordances

Self-hostable Local-first storage

P2P Protocol Atributos

P2P Architecture Small-world DHT — nodes assigned locations 0–1; greedy routing toward nodes whose location is closest to target key; opennet (random peers) and darknet (trusted friends) modes

Overlay Network Small-world network overlay — routing draws on Kleinberg small-world phenomenon; requests traverse multiple intermediary hops

Content Addressing Yes — CHK is SHA-256 hash of encrypted content; SSK uses public key + descriptor hash; content addressing is foundational

Local-First Yes — each node stores data locally; network functions without any central servers

E2EE Yes — all stored blocks encrypted; node operators cannot identify content they store; multi-hop routing conceals both inserter and retriever identity

CRDTs Lib N/A — no CRDT library; SSK/USK key versioning provides a simpler update model for static content

Byzantine Fault Tolerance No formal BFT — probabilistic resistance through multi-hop routing and encryption; no consensus mechanism

Signature Yes — SSK uses DSA/ECDSA asymmetric signatures; CHK provides tamper-evident content-hash verification

Permissions Key-based (CHK ownership implicit in key knowledge; SSK requires private key to insert under a namespace)

Semantic Web Compatability No

Smart Contract No

Protocol Stack Position Application-layer (built on TCP/IP; operates as overlay network)

Asset / Value Embedding None — anonymized data storage only; no value or asset transmission

Protocol Maturity / Standardization Mature / Community Standard — 25+ years of continuous development; build 1506 (February 2025); academically influential; GPL v2+; not submitted to formal standards body