status.rst (4163B)
1 .. _status: 2 3 What works today 4 ================ 5 6 GNUnet is a research project that is still in an early (alpha) stage. Some 7 of its components are ready for early adopters, others are work in 8 progress. This page tells you which is which, so that you can decide where 9 to invest your time. 10 11 *Last reviewed for GNUnet 0.29 (November 2026).* 12 13 In short 14 -------- 15 16 - **Start with the GNU Name System (GNS).** It is the most mature 17 component, it is specified in :rfc:`9498`, and it is useful on its own. 18 See :doc:`gns/index`. 19 - **Everything else is under development.** The other applications work 20 to varying degrees and are worth exploring if you are curious or want to 21 help, but expect bugs, missing features and incompatible changes. 22 - **The network is small.** As a consequence it cannot yet provide strong 23 anonymity, and there is not much content to find. 24 - **Releases may be incompatible.** Peers of different major versions (for 25 example 0.28.x and 0.29.x) may not be able to communicate. Keep your 26 installation up to date. 27 - **There are known privacy issues**, in particular for mobile users. 28 29 Applications 30 ------------ 31 32 .. list-table:: 33 :header-rows: 1 34 :widths: 18 37 15 30 35 36 * - Application 37 - What it does 38 - Status 39 - Notes 40 * - :doc:`GNS <gns/index>` 41 - Decentralized, censorship-resistant name system 42 - **Most mature** 43 - Protocol specified in :rfc:`9498`; stable API. Lookups in 44 remote zones depend on the network and can be slow. 45 * - :doc:`re:claimID <users/reclaim>` 46 - Self-sovereign identity provider with OpenID Connect support 47 - In development 48 - Specified in LSD 0002. 49 * - :doc:`Messenger <users/messenger>` 50 - Decentralized, end-to-end encrypted group messaging 51 - In development 52 - Use the separate applications `messenger-gtk 53 <https://git.gnunet.org/messenger-gtk.git/>`__ or `messenger-cli 54 <https://git.gnunet.org/messenger-cli.git/>`__; the bundled 55 ``gnunet-messenger`` tool is meant for testing. 56 * - :doc:`File-sharing <users/fs>` 57 - Anonymous, censorship-resistant file-sharing 58 - In development 59 - Known moderate design issues that affect usability and 60 performance. 61 * - :doc:`VPN <users/vpn>` 62 - Tunnel IP traffic over GNUnet, with IPv4/IPv6 protocol translation 63 - In development 64 - GNU/Linux only. Provides no anonymity. 65 * - Conversation 66 - Decentralized voice calls 67 - Experimental 68 - 69 70 Network foundations 71 ------------------- 72 73 These subsystems carry all of the above. Their state determines how well 74 remote operations, such as looking up names in other people's zones, work 75 in practice. 76 77 .. list-table:: 78 :header-rows: 1 79 :widths: 25 40 35 80 81 * - Subsystem 82 - Role 83 - Status 84 * - TRANSPORT and communicators 85 - Connectivity between peers over UDP, TCP, QUIC, ... 86 - In development. GNUnet 0.29 fixed several regressions and 87 instabilities. 88 * - CORE 89 - Encrypted, authenticated links between neighbouring peers 90 - In development; incompatible changes expected. 91 * - CADET 92 - End-to-end encrypted channels across the network 93 - Known moderate implementation limitations that affect 94 performance. 95 * - DHT (R5N) 96 - Distributed hash table used by GNS and others 97 - Being specified in LSD 0004. 98 * - SET, SETU, SETI 99 - Set reconciliation and intersection 100 - Minor implementation limitations that create unnecessary attack 101 surface for availability. The original SET subsystem is deprecated 102 in favour of SETU and SETI. 103 * - RPS 104 - Random peer sampling 105 - Experimental. 106 107 For developers, :ref:`Subsystem-stability` lists the expected stability of 108 each subsystem's network protocol, IPC protocol and C API. The `bug tracker 109 <https://bugs.gnunet.org/>`__ lists the specific open issues. 110 111 How you can help 112 ---------------- 113 114 Running a peer is the simplest way to help: every additional peer makes the 115 network more useful and its anonymity stronger. Reporting bugs, testing 116 release candidates and improving this documentation help just as much. See 117 :doc:`developers/contributing`.