What works today

GNUnet is a research project that is still in an early (alpha) stage. Some of its components are ready for early adopters, others are work in progress. This page tells you which is which, so that you can decide where to invest your time.

Last reviewed for GNUnet 0.29 (November 2026).

In short

  • Start with the GNU Name System (GNS). It is the most mature component, it is specified in RFC 9498, and it is useful on its own. See The GNU Name System.

  • Everything else is under development. The other applications work to varying degrees and are worth exploring if you are curious or want to help, but expect bugs, missing features and incompatible changes.

  • The network is small. As a consequence it cannot yet provide strong anonymity, and there is not much content to find.

  • Releases may be incompatible. Peers of different major versions (for example 0.28.x and 0.29.x) may not be able to communicate. Keep your installation up to date.

  • There are known privacy issues, in particular for mobile users.

Applications

Application

What it does

Status

Notes

GNS

Decentralized, censorship-resistant name system

Most mature

Protocol specified in RFC 9498; stable API. Lookups in remote zones depend on the network and can be slow.

re:claimID

Self-sovereign identity provider with OpenID Connect support

In development

Specified in LSD 0002.

Messenger

Decentralized, end-to-end encrypted group messaging

In development

Use the separate applications messenger-gtk or messenger-cli; the bundled gnunet-messenger tool is meant for testing.

File-sharing

Anonymous, censorship-resistant file-sharing

In development

Known moderate design issues that affect usability and performance.

VPN

Tunnel IP traffic over GNUnet, with IPv4/IPv6 protocol translation

In development

GNU/Linux only. Provides no anonymity.

Conversation

Decentralized voice calls

Experimental

Network foundations

These subsystems carry all of the above. Their state determines how well remote operations, such as looking up names in other people’s zones, work in practice.

Subsystem

Role

Status

TRANSPORT and communicators

Connectivity between peers over UDP, TCP, QUIC, …

In development. GNUnet 0.29 fixed several regressions and instabilities.

CORE

Encrypted, authenticated links between neighbouring peers

In development; incompatible changes expected.

CADET

End-to-end encrypted channels across the network

Known moderate implementation limitations that affect performance.

DHT (R5N)

Distributed hash table used by GNS and others

Being specified in LSD 0004.

SET, SETU, SETI

Set reconciliation and intersection

Minor implementation limitations that create unnecessary attack surface for availability. The original SET subsystem is deprecated in favour of SETU and SETI.

RPS

Random peer sampling

Experimental.

For developers, Subsystem stability lists the expected stability of each subsystem’s network protocol, IPC protocol and C API. The bug tracker lists the specific open issues.

How you can help

Running a peer is the simplest way to help: every additional peer makes the network more useful and its anonymity stronger. Reporting bugs, testing release candidates and improving this documentation help just as much. See Contributing.