I2P

Original author(s)	I2P Team [1]
Initial release	2003;21 years ago (2003)
Stable release	2.5.1 [2]   / 6 May 2024;7 days ago (6 May 2024)
Repository	github.com/i2p/i2p.i2p
Written in	Java
Operating system	Cross-platform: Unix-like (Android, Linux, BSD, macOS), Microsoft Windows
Available in	English, Spanish Incomplete translations: Russian, French, Romanian, German, Swedish, Italian, Portuguese, Chinese, Dutch, Polish, Hungarian, Arabic, Japanese, Estonian, Persian [3]
Type	Anonymity application, Overlay network, mix network, garlic router, peer-to-peer
License	Free/Open Source – different licenses for different parts [4] Public domain, BSD, GPL, MIT
Website	geti2p.net

The Invisible Internet Project (I2P) is an anonymous network layer (implemented as a mix network) that allows for censorship-resistant, peer-to-peer communication. Anonymous connections are achieved by encrypting the user's traffic (by using end-to-end encryption), and sending it through a volunteer-run network of roughly 55,000 computers distributed around the world. Given the high number of possible paths the traffic can transit, a third party watching a full connection is unlikely. The software that implements this layer is called an "I2P router", and a computer running I2P is called an "I2P node". I2P is free and open sourced, and is published under multiple licenses. ^[5]

Technical design

I2P has been beta software since it started in 2003 as a fork of Freenet. ^{[6] [7]} The software's developers emphasize that bugs are likely to occur in the beta version and that peer review has been insufficient to date, in 2013. ^[8] However, they believe the code is now reasonably stable and well-developed, and more exposure can help the development of I2P.^{[ citation needed ]}

The network is strictly message-based, like IP, but a library is available to allow reliable streaming communication on top of it (similar to Non-blocking IO-based TCP, although from version 0.6, a new Secure Semi-reliable UDP transport is used ^[9] ). All communication is end-to-end encrypted (in total, four layers of encryption are used when sending a message) through garlic routing, ^[10] and even the end points ("destinations") are cryptographic identifiers (essentially a pair of public keys), so that neither senders nor recipients of messages need to reveal their IP address to the other side or to third-party observers.

Although many developers had been a part of the Invisible IRC Project (IIP) ^[11] and Freenet communities, significant differences exist between their designs and concepts. IIP was an anonymous centralized IRC server. Freenet is a censorship-resistant distributed data store. I2P is an anonymous peer-to-peer distributed communication layer designed to run any traditional internet service (e.g. Usenet, email, IRC, file sharing, Web hosting and HTTP, or Telnet), as well as more traditional distributed applications (e.g. a distributed data store, a web proxy network using Squid, or DNS).

Many developers of I2P are known only under pseudonyms. While the previous main developer, jrandom , is currently on hiatus, ^[12] others, such as zzz, killyourtv, and Complication have continued to lead development efforts,^{[ citation needed ]} and are assisted by numerous contributors. ^[1]

I2P uses 2048bit ElGamal/AES256/SHA256+Session Tags encryption ^[13] and Ed25519 EdDSA/ECDSA signatures. ^[14]

Releases

I2P has had a stable release every six to eight weeks. Updates are distributed via I2P torrents and are signed by the release manager (generally zzz or str4d).

I2P Versions

Version Release date Release Notes Old version, no longer maintained: 0.9.11 2014-02-08 Support for outproxy plugins, improves lease set lookup security, and reduces memory usage. [15] Old version, no longer maintained: 0.9.12 2014-03-31 Support for ECDSA and updates to Jetty 8. [16] Old version, no longer maintained: 0.9.13 2014-05-22 SusiMail improvements and fixes for firewalled router. [17] Old version, no longer maintained: 0.9.14 2014-07-26 Critical fixes for XSS and remote execution vulnerabilities. [18] Old version, no longer maintained: 0.9.14.1 2014-08-09 I2PSnark and console fixes. [19] Old version, no longer maintained: 0.9.15 2014-09-20 Preliminary support for Ed25519 EdDSA signatures. [20] Old version, no longer maintained: 0.9.16 2014-11-01 Add support for stronger Router Info signatures. [21] Old version, no longer maintained: 0.9.17 2014-11-30 Signed news, ECDSA tunnels by default. [22] Old version, no longer maintained: 0.9.18 2015-02-22 Shortened the startup time, and reduced latency throughout our network protocols. [23] Old version, no longer maintained: 0.9.19 2015-04-12 Several fixes and improvements for floodfill performance. [24] Old version, no longer maintained: 0.9.20 2015-06-02 Important bug fixes, and several changes to increase floodfill capacity in the network. [25] Old version, no longer maintained: 0.9.21 2015-07-31 Contains several changes to add capacity to the network, increase the efficiency of the floodfills, and use bandwidth more effectively. [26] Old version, no longer maintained: 0.9.22 2015-09-12 Fixes for I2PSnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures. [27] Old version, no longer maintained: 0.9.23 2015-11-19 Accelerates the rekeying process. [28] Old version, no longer maintained: 0.9.24 2016-01-27 A new version of SAM (v3.2) and numerous bug fixes and efficiency improvements. The first release to require Java 7. [29] Old version, no longer maintained: 0.9.25 2016-03-22 A new version of SAM (v3.3), QR codes for sharing hidden services, identicons and router families. [30] Old version, no longer maintained: 0.9.26 2016-06-07 Major upgrade to the native crypto library, a new addressbook subscription protocol with signatures, and major improvements to the Debian/Ubuntu packaging. [31] Old version, no longer maintained: 0.9.27 2016-10-17 Improvements in IPv6 transports, SSU peer testing, and hidden mode. [32] Old version, no longer maintained: 0.9.28 2016-12-12 Updates for a number of bundled software, fixes for IPv6 peer testing, improvements to detect and block potentially malicious peers. Preliminary fixes for Java 9. [33] Old version, no longer maintained: 0.9.29 2017-02-27 Support for NTP over IPv6, preliminary Docker support, translated main pages. We now pass same-origin Referrer headers through the HTTP proxy. There are more fixes for Java 9, although we do not yet recommend Java 9 for general use. [34] Old version, no longer maintained: 0.9.30 2017-05-03 Support for Debian Stretch and Ubuntu Zesty, upgraded to Jetty 9 and Tomcat 8, support for the migration of old DSA-SHA1 hidden services to the EdDSA signature type. [35] Old version, no longer maintained: 0.9.31 2017-08-07 Refreshed the router console to improve readability, improved accessibility and cross-browser support, and general tidying up. [36] Old version, no longer maintained: 0.9.32 2017-11-07 0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail). We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS. Added some checks in the console to resist rebinding attacks. [37] Old version, no longer maintained: 0.9.33 2018-01-30 0.9.33 contains bug fixes for i2psnark, i2ptunnel, streaming, and SusiMail. Updates for reseed proxying, and default rate limiting. [38] Old version, no longer maintained: 0.9.34 2018-04-10 0.9.34 contains bug fixes for i2ptunnel, router console, SusiMail, routing and transport along with Changes to SusiMail and UPnP. [39] Old version, no longer maintained: 0.9.35 2018-06-26 0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website. [40] Old version, no longer maintained: 0.9.36 2018-08-23 0.9.36 implements a new, more secure transport protocol called NTCP2. It is disabled by default, but you may enable it for testing. NTCP2 will be enabled in the next release. [41] Old version, no longer maintained: 0.9.37 2018-10-04 0.9.37 enables the faster, more secure transport protocol called NTCP2. [42] Old version, no longer maintained: 0.9.38 2019-01-22 0.9.38 includes a new first-install wizard with a bandwidth tester. We've added support for the latest GeoIP database format. There's a new Firefox profile installer and a new, native Mac OSX installer on our website. Work continues on supporting the new "LS2" netdb format. [43] Old version, no longer maintained: 0.9.39 2019-03-21 0.9.39 includes extensive changes for the new network database types (proposal 123). We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications. There are numerous performance improvements and bug fixes. [44] Old version, no longer maintained: 0.9.40 2019-05-07 0.9.40 includes support for the new encrypted leaseset format. We disabled the old NTCP 1 transport protocol. There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections. [45] Old version, no longer maintained: 0.9.41 2019-07-02 0.9.41 continues the work to implement new features for proposal 123, including per-client authentication for encrypted leasesets. The console has an updated I2P logo and several new icons. We've updated the Linux installer. [46] Old version, no longer maintained: 0.9.42 2019-08-28 0.9.42 continues the work to make I2P faster and more reliable. It includes several changes to speed up our UDP transport. We have split up the configuration files to enable future work for more modular packaging. We continue work to implement new proposals for faster and more secure encryption. There are, of course, a lot of bug fixes also. [47] Old version, no longer maintained: 0.9.43 2019-10-22 0.9.43 release continues work on stronger security and privacy features and performance improvements. Our implementation of the new leaseset specification (LS2) is now complete. We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release. Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes. [48] Old version, no longer maintained: 0.9.44 2019-12-01 0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types. [49] Old version, no longer maintained: 0.9.45 2020-02-25 0.9.45 contains bug fixes. [50] Old version, no longer maintained: 0.9.46 2020-05-25 0.9.46 contains new ECIES Encryption. [51] Old version, no longer maintained: 0.9.47 2020-08-24 0.9.47 enables new encryption for some services, now requires Java 8 and Sybil analysis and blocking is now enabled by default. [52] Old version, no longer maintained: 0.9.48 2020-11-30 0.9.48 enables new encryption for most services, has significant performance improvements. [53] Old version, no longer maintained: 0.9.49 2021-02-17 0.9.49 improves SSU transport and begins transition to X25519 encryption for routers. [54] Old version, no longer maintained: 0.9.50 2021-05-17 0.9.50 continues transition to X25519 encryption for routers, enables DoH for reseeding and improves support for IPv6. [55] Old version, no longer maintained: 1.5.0 2021-08-23 1.5.0 adds short tunnel build messages, continues transition to X25519 encryption for routers and improves performance. [56] class="templateVersion c" style="background-color: #D4F4B4; " title="Current stable version" data-sort-value="1.6.1 [57] " | Current stable version:1.6.1 [58] 2021-11-29 1.6.1 further accelerates transition to X25519 for routers, enables short tunnel build messages and improves SSU performance. [59]

Funding

The website states that "funding for I2P comes entirely from donations". ^[60] Admins and managers of the project said that "the core project itself doesn't take donations". These should instead go to secondary applications or be spent on hiring others, to work on I2P. ^[61] Support for the onboarding for I2P came from the Open Technology Fund . ^{[62] [63]} In contrast to The Tor Project , I2P has "not the financial or legal infrastructure to support a network of exit nodes". ^[64] The reseed servers, ^[65] a sort of bootstrap nodes, ^[66] which connect the user with the initial set of peers to join the I2P-network, should be run by volunteers. ^[67]

Software

I2P 0.9.31-0 router console

Since I2P is an anonymizing network layer, it is designed so other software can use it for anonymous communication. As such, there are a variety of tools currently available for I2P or in development.

The I2P router is controlled through the router console, which is a web frontend accessed through a web browser.

General networking

• I2PTunnel is an application embedded into I2P that allows arbitrary TCP/IP applications to communicate over I2P by setting up "tunnels" which can be accessed by connecting to pre-determined ports on localhost.
• SAM (Simple Anonymous Messaging) is a protocol which allows a client application written in any programming language to communicate over I2P, by using a socket-based interface to the I2P router. ^[68]
• BOB (Basic Open Bridge) is a less complex app to router protocol similar to "SAM" ^[69]
• Orchid Outproxy Tor plugin ^[70]

Chat

• Any IRC client made for the Internet Relay Chat can work, once connected to the I2P IRC server (on localhost). I2P have the option to create tunnels that are specific for this usage, where certain commands that could de-anonymize the user are filtered out.

File sharing

• Several programs provide BitTorrent functionality for use within the I2P network. Users cannot connect to non-I2P torrents or peers from within I2P, nor can they connect to I2P torrents or peers from outside I2P. ^[71] I2PSnark, included in the I2P install package, is a port of the BitTorrent client named Snark. ^[72] Vuze , formerly known as Azureus, is a BitTorrent client that includes a plugin for I2P, allowing anonymous swarming through this network. ^[73] This plugin is still in an early stage of development, however it is already fairly stable. I2P-BT is a BitTorrent client for I2P that allows anonymous swarming for file sharing. This client is a modified version of the original BitTorrent 3.4.2 program which runs on MS Windows and most dialects of Unix in a GUI and command-line environment. It was developed by the individual known as 'duck' on I2P in cooperation with 'smeghead'. It is no longer being actively developed; however, there is a small effort to upgrade the I2P-BT client up to par with the BitTorrent 4.0 release. I2PRufus is an I2P port of the Rufus BitTorrent client. ^[74] Robert (P2P Software) is the most actively maintained I2PRufus fork. XD is a standalone BitTorrent client written in Go. ^[75] BiglyBT is a bittorrent client based on Vuze which also allows the use of i2p for downloading/seeding. Additionally, there exists a torrent index named Postman, ran by the individual with the same name, its rules says that it does not allow illegal content, but warez and piracy is accepted.
• Two Kad network clients exist for the I2P network, iMule and Nachtblitz. iMule (invisible Mule) is a port of eMule for I2P network. iMule has not been developed since 2013. iMule is made for anonymous file sharing. In contrast to other eDonkey clients, iMule only uses the Kademlia for proceeding to connect through I2P network, so no servers are needed. Nachtblitz ^[76] is a custom client built on the .NET Framework. The latest version is 1.4.27, released on March 23, 2016. Nachtblitz includes a time lock to disable the software one year after its release date.
• I2Phex is a port of the popular Gnutella client Phex to I2P. It is stable and fairly functional.
• Tahoe-LAFS has been ported to I2P. This allows for files to be anonymously stored in Tahoe-LAFS grids.
• MuWire is a file-sharing program inspired by the LimeWire Gnutella client that works atop the I2P network. ^[77] The development of MuWire halted on February 14th 2023 ^[78]

Bridging to clearnet

Currently, Vuze and BiglyBT are the torrent clients that make clearnet (connections not through I2P) torrents available on I2P and vice versa. Depending on the client settings, torrents from the internet can be made available on I2P (via announcements to I2P's DHT network) and torrents from I2P can be made available to the internet. For this reason, torrents previously published only on I2P can be made available to the entire Internet, and users of I2P can often download popular content from the Internet while maintaining the anonymity of I2P. As of August 2022, the default outproxy is exit.stormycloud.i2p which is run by StormyCloud Inc. ^{[79] [80] [81]}

Email

A screenshot of the inbox of I2P-Bote.

• I2P-Bote is a free, fully decentralized and distributed anonymous email system with a strong focus on security. ^[82] It supports multiple identities and does not expose email metadata. As of 2015 ^[update] , it is still considered beta software. I2P-Bote is accessible via the I2P web console interface or using standard email protocols (i.e. IMAP/SMTP). All bote-mails are transparently end-to-end encrypted and signed by the sender's private key, thus removing the need for PGP or other email encryption software. I2P-Bote offers additional anonymity by allowing for the use of mail relays with variable length delays. Since it is decentralized, there is no centralized email server that could correlate different email identities as communicating with each other (i.e. profiling). Even the nodes relaying the mails do not know the sender, and apart from sender and receiver, only the end of the high-latency mail route and the storing nodes will know to whom (which I2P-Bote address – the user's IP address is still hidden by I2P) the mail is destined. The original sender could have gone offline long before the email becomes available to the recipient. No account registration is necessary, all you have to do in order to use it is create a new identity. I2P-Bote can be installed as an I2P plugin .^{[ citation needed ]}
• I2P also has a free pseudonymous e-mail service run by an individual called Postman. Susimail is a web-based email client intended primarily for use with Postman's mail servers, and is designed with security and anonymity in mind. Susimail was created to address privacy concerns in using these servers directly using traditional email clients, such as leaking the user's hostname while communicating with the SMTP server. It is currently included in the default I2P distribution, and can be accessed through the I2P router console web interface. Mail.i2p can contact both I2P email users and public internet email users.
• Bitmessage.ch can be used over I2P^{[ citation needed ]}

Instant messaging

• I2P-Messenger is a simple Qt-based, serverless, end-to-end-encrypted instant messenger for I2P. ^[83] No servers can log the user's conversations. No ISP can log with whom the user chats, when, or for how long. As it is serverless, it can make use of I2P's end-to-end encryption, preventing any node between two parties from having access to the plain text. I2P-Messenger can be used for fully anonymous instant communication with persons the user doesn't even know, or, alternatively, to communicate securely and untraceably with friends, family members, or colleagues. In addition to messaging, file transfer is also supported.

• I2P-Talk is another simple instant messenger incompatible with I2P-Messenger, but having the same security properties

Publishing

• Syndie is a content distribution application, suitable for blogs, newsgroups, forums and small media attachments. Syndie is designed for network resilience. It supports connections to I2P, the Tor network (Syndie does not support Socks proxies, workaround needed for Tor access), Freenet and the regular internet. Server connections are intermittent, and support higher-latency communications. Connections can be made to any number of known servers. Content is spread efficiently using a Gossip protocol.
• Aktie is an anonymous file sharing and distributed Web of trust forums system. Aktie can connect to I2P with its internal router or use an external router. To fight spam, "hash payments" (proof of CPU work) is computed for every published item.

Routers

• I2PBerry is a Linux distribution which can be used as a router to encrypt and route network traffic through the I2P network.
• i2pd is a light-weight I2P router written in C++, stripping the excessive applications such as e-mail, torrents, and others that can be regarded as bloat. ^{[84] [85]} The I2PSnark standalone BitTorrent client by I2P+ Team can still be used with it.
• Kovri is an I2P router written in C++. ^[86] It was forked from i2pd following developer disagreements. ^[87] Kovri's primary purpose is to integrate with the cryptocurrency Monero to send new transaction information over I2P, making it much more difficult to find which node is the origin of a transaction request. ^[88] Those using the Kovri router will be running full I2P routers that contribute to the I2P network the same way the current Java router does. This project is expected to benefit both the Monero and I2P communities, since it will allow for greater privacy in Monero, and it should increase the number of nodes on the I2P network. ^[89]

The Privacy Solutions project

The Privacy Solutions project, ^[90] a new organization that develops and maintains I2P software, launched several new development efforts designed to enhance the privacy, security, and anonymity for users, based on I2P protocols and technology.

These efforts include: ^[91]

• The Abscond browser bundle.
• i2pd, ^[92] an alternate implementation of I2P, written in C++ (rather than Java).
• The "BigBrother" I2P network monitoring project.

The code repository and download sections for the i2pd and Abscond project is available for the public to review and download. ^[93] Effective January, 2015 i2pd is operating under PurpleI2P. ^[94]

Android

I2P running on Android.

• Release builds of an I2P Router application for Android can be found on the Google Play store under The Privacy Solutions Project's Google Play account or on an F-Droid repository hosted by the developers. ^[95]
• Nightweb is an Android application that utilizes I2P and Bittorrent to share blog posts, photos, and other similar content. It can also be run as a desktop application. It is no longer in development. ^[96]

Cryptocurrency

Some cryptocurrencies that support I2P are listed below.

• Bitcoin ^[97]
• Monero
• Verge

Terminology

I2P's mascot, itoopie, who is looking through a magnifying glass.

Eepsite

Eepsites are websites that are hosted anonymously within the I2P network. Eepsite names end in .i2p, such as ugha.i2p or forum.i2p. EepProxy can locate these sites through the cryptographic identifier keys stored in the hosts.txt file found within the I2P program directory. Typically, I2P is required to access these eepsites. ^[99]

.i2p

'I2p' is a pseudo-top-level domain which is only valid within the I2P overlay network scope. .i2p names are resolved by browsers by submitting requests to EepProxy which will resolve names to an I2P peer key and will handle data transfers over the I2P network while remaining transparent to the browser. ^[100]

EepProxy

The EepProxy program handles all communication between the browser and any eepsite. It functions as a proxy server that can be used by any web browser.

Peers, I2P nodes

Other machines using I2P that are connected to user's machine within the network. Each machine within the network shares the routing and forwarding of encrypted packets.

Tunnels

Every ten minutes, a connection is established between the user's machine and another peer. Data to and from the user, along with the data for other peers (routed through the user's machine), pass through these tunnels and are forwarded to their final destination (may include more jumps). ^[101]

netDb

The distributed hash table (DHT) database based on the Kademlia algorithm that holds information on I2P nodes and I2P eepsites. This database is split up among routers known as "floodfill routers". When a user wants to know how to contact an eepsite, or where more peers are, they query the database. ^{[102] [99]}

Vulnerabilities

Denial of service attacks are possible against websites hosted on the network, though a site operator may secure their site against certain versions of this type of attack to some extent. ^{[103] [104]}

A zero-day vulnerability was discovered for I2P in 2014, and was exploited to de-anonymize at least 30,000 users. This included users of the operating system Tails. ^[105] This vulnerability was later patched. ^{[106] [107]}

A 2017 study examining how forensic investigators might exploit vulnerabilities in I2P software to gather useful evidence indicated that a seized machine which had been running I2P router software may hold unencrypted local data that could be useful to law enforcement. Records of which eepsites a user of a later-seized machine was interested in may also be inferred. The study identified a "trusted" I2P domain registrar ("NO.i2p") which appeared to have been abandoned by its administrator, and which the study identified as a potential target for law enforcement takeover. It alternatively suggested waiting for NO.i2p's server to fail, only to social engineer the I2P community into moving to a phony replacement. Another suggestion the study proposed was to register a mirror version of a target website under an identical domain. ^[104]

I2PCon

David Dagon presenting at the first I2Pcon.

From August 15, 2015 to August 16, 2015 an I2P convention was held in Toronto, Ontario. ^[108] The conference was hosted by a local hackerspace, Hacklab. The conference featured presentations from I2P developers and security researchers.

See also

• Crypto-anarchism
• Deep web
• Darknet
• Garlic routing
• Key-based routing
• Public-key cryptography
• Rendezvous protocol
• Secure communication
• Threat model

Software

• Freenet
• Mixnet
• Retroshare
• Tor
• Tribler
• ZeroNet

References

1. "I2P Project Members". geti2p.net. Archived from the original on 26 February 2019. Retrieved 22 November 2015.
2. "Release I2P 2.5.1 Point Release · i2p/i2p.i2p" . Retrieved 7 May 2024.
3. I2P (project), Transifex, archived from the original on 2013-12-25, retrieved 2014-02-12.
4. "Licenses", Get involved, Get I2P, archived from the original on 2013-12-24, retrieved 2013-12-24.
5. Gallagher, Sean (2015-01-13). "Under the hood of I2P, the Tor alternative that reloaded Silk Road". Ars Technica . Archived from the original on 2019-07-12. Retrieved 2019-08-17.
6. "Anonymity Networks: VPNs, Tor, and I2P | Restore Privacy". 3 February 2020. Archived from the original on 28 January 2021.
7. Get I2P (blog), archived from the original on 2017-07-02, retrieved 2013-12-24.
8. "Benefits of Tor over I2P". I2P Dev Team. Archived from the original on 24 December 2013. Retrieved 23 December 2013.
9. "Secure Semireliable UDP (SSU)". geti2p.net. Archived from the original on 6 September 2023. Retrieved 18 May 2023.
10. "Garlic Routing – I2P". geti2p.net. Archived from the original on 2019-11-16. Retrieved 2017-12-12.
11. "IIP", Invisible IP, Source forge, archived from the original on 2009-05-18, retrieved 2012-02-11.
12. "Jrandom's Announcement – I2P". geti2p.net. Archived from the original on 2017-08-19. Retrieved 2017-07-15.
13. "ElGamal/AES + SessionTag Encryption – I2P". geti2p.net. Archived from the original on 2017-03-31. Retrieved 2017-03-30.
14. "Crypto/ECDSA – I2P Bugtracker". trac.i2p2.de. Archived from the original on 2015-05-20. Retrieved 2017-03-30.
15. zzz (8 February 2014). "0.9.11 Release". geti2p.net. Archived from the original on 2 September 2016. Retrieved 15 September 2015.
16. zzz (31 March 2014). "0.9.12 Release". geti2p.net. Archived from the original on 2 September 2016. Retrieved 15 September 2015.
17. zzz (22 May 2014). "0.9.13 Release". geti2p.net. Archived from the original on 2 August 2015. Retrieved 15 September 2015.
18. zzz (26 July 2014). "0.9.14 Release". geti2p.net. Archived from the original on 6 October 2015. Retrieved 15 September 2015.
19. zzz (9 August 2014). "0.9.14.1 Release". geti2p.net. Archived from the original on 2 September 2016. Retrieved 15 September 2015.
20. zzz (20 September 2014). "0.9.15 Release". geti2p.net. Archived from the original on 28 June 2017. Retrieved 15 September 2015.
21. zzz (1 November 2014). "0.9.16 Release". geti2p.net. Archived from the original on 3 March 2016. Retrieved 15 September 2015.
22. zzz (30 November 2014). "0.9.17 Release". geti2p.net. Archived from the original on 17 December 2015. Retrieved 15 September 2015.
23. zzz (22 February 2015). "0.9.18 Release". geti2p.net. Archived from the original on 11 September 2015. Retrieved 15 September 2015.
24. zzz (12 April 2015). "0.9.19 Release". geti2p.net. Archived from the original on 19 April 2015. Retrieved 4 May 2015.
25. zzz (2 June 2015). "0.9.20 Release". geti2p.net. Archived from the original on 11 September 2015. Retrieved 15 September 2015.
26. zzz (31 July 2015). "0.9.21 Release". geti2p.net. Archived from the original on 11 September 2015. Retrieved 2 August 2015.
27. zzz (12 December 2015). "0.9.22 Release". geti2p.net. Archived from the original on 4 March 2016. Retrieved 13 September 2015.
28. str4d (19 November 2015). "0.9.23 Release". geti2p.net. Archived from the original on 21 November 2015. Retrieved 20 November 2015.
29. zzz (27 January 2016). "0.9.24 Release". geti2p.net. Archived from the original on 2 February 2016. Retrieved 29 January 2016.
30. zzz (3 March 2016). "0.9.25 Release". geti2p.net. Archived from the original on 3 April 2016. Retrieved 23 March 2016.
31. zzz (7 June 2016). "0.9.26 Release". geti2p.net. Archived from the original on 2 September 2016. Retrieved 7 June 2016.
32. zzz (17 October 2016). "0.9.27 Release". geti2p.net. Archived from the original on 6 February 2017. Retrieved 6 January 2017.
33. zzz (12 December 2016). "0.9.28 Release". geti2p.net. Archived from the original on 29 August 2017. Retrieved 15 July 2017.
34. zzz (27 February 2017). "0.9.29 Release". geti2p.net. Archived from the original on 6 March 2017. Retrieved 5 March 2017.
35. zzz (3 May 2017). "0.9.30 Release". geti2p.net. Archived from the original on 3 October 2020. Retrieved 14 June 2017.
36. zzz (7 August 2017). "0.9.31 Release". geti2p.net. Archived from the original on 11 August 2017. Retrieved 11 August 2017.
37. zzz (11 November 2017). "0.9.32 Release". geti2p.net. Archived from the original on 15 November 2017. Retrieved 15 November 2017.
38. zzz (30 January 2018). "0.9.33 Release". geti2p.net. Archived from the original on 31 January 2018. Retrieved 30 January 2018.
39. zzz (10 April 2018). "0.9.34 Release". geti2p.net. Archived from the original on 12 April 2018. Retrieved 11 April 2018.
40. zzz (26 June 2018). "0.9.35 Release". geti2p.net. Archived from the original on 29 June 2018. Retrieved 29 June 2018.
41. zzz (23 August 2018). "0.9.36 Release". geti2p.net. Archived from the original on 27 March 2019. Retrieved 29 January 2019.
42. zzz (4 October 2018). "0.9.37 Release". geti2p.net. Archived from the original on 7 January 2019. Retrieved 29 January 2019.
43. zzz (22 January 2019). "0.9.38 Release". geti2p.net. Archived from the original on 29 January 2019. Retrieved 29 January 2019.
44. zzz (21 March 2019). "0.9.39 Release". geti2p.net. Archived from the original on 22 March 2019. Retrieved 22 March 2019.
45. zzz (7 May 2019). "0.9.40 Release". geti2p.net. Archived from the original on 2 August 2019. Retrieved 7 December 2019.
46. zzz (2 July 2019). "0.9.41 Release". geti2p.net. Archived from the original on 13 August 2019. Retrieved 13 August 2019.
47. zzz (28 August 2019). "0.9.42 Release". geti2p.net. Archived from the original on 3 October 2020. Retrieved 27 September 2020.
48. zzz (22 October 2019). "0.9.43 Release". geti2p.net. Archived from the original on 25 November 2019. Retrieved 23 November 2019.
49. zzz (1 December 2019). "0.9.44 Release". geti2p.net. Archived from the original on 5 December 2019. Retrieved 7 December 2019.
50. zzz (25 February 2020). "0.9.45 Release". geti2p.net. Archived from the original on 21 October 2020. Retrieved 3 October 2020.
51. zzz (25 May 2020). "0.9.46 Release". geti2p.net. Archived from the original on 20 September 2020. Retrieved 3 October 2020.
52. zzz (24 August 2020). "0.9.47 Release". geti2p.net. Archived from the original on 27 August 2020. Retrieved 9 September 2020.
53. zzz (30 November 2020). "0.9.48 Release". geti2p.net. Archived from the original on 20 January 2021. Retrieved 6 January 2021.
54. zzz (17 February 2021). "0.9.49 Release". geti2p.net. Archived from the original on 13 December 2021. Retrieved 13 December 2021.
55. zzz (17 May 2021). "0.9.50 Release". geti2p.net. Archived from the original on 26 May 2021. Retrieved 1 June 2021.
56. zzz (23 August 2021). "1.5.0 Release". geti2p.net. Archived from the original on 13 December 2021. Retrieved 13 December 2021.
57. 1.6.0 was tagged, but not released.
58. 1.6.0 was tagged, but not released.
59. zzz (29 September 2021). "1.6.1 Release". geti2p.net. Archived from the original on 13 December 2021. Retrieved 13 December 2021.
60. "I2P: A scalable framework for anonymous communication – Introduction". I2P Website. Archived from the original on 2022-03-14. Retrieved 2022-03-14.
61. idk aka. eyedeekay (2022-03-06). "Network privacy via i2p w/ idk and Sadie". Opt Out Podcast. 00:55:43. Archived from the original on 2022-03-07. Retrieved 2022-03-14.
62. Mascis, Sadie (2022-03-06). "Network privacy via i2p w/ idk and Sadie"". Opt Out Podcast. 00:54:20. Archived from the original on 2022-03-07. Retrieved 2022-03-13.
63. Open Technology Fund. "5G and Human Rights". Open Technology Fund Website. U.S. Agency for Global Media. Archived from the original on 2022-03-14. Retrieved 2022-03-14.
64. idk aka. eyedeekay (2022-03-06). "Network privacy via i2p w/ idk and Sadie". Opt Out Podcast. 00:34:20. Archived from the original on 2022-03-07. Retrieved 2022-03-13.
65. "How to Set up a Reseed Server". I2P Website. Archived from the original on 2022-03-14. Retrieved 2022-03-13.
66. "How to volunteer by helping I2P-Bote bootstrap – Blog". I2p Website. Archived from the original on 2022-04-07. Retrieved 2022-03-13.
67. idk aka. eyedeekay (2022-03-06). "Network privacy via i2p w/ idk and Sadie". Opt Out Podcast. 00:57:00. Archived from the original on 2022-03-07. Retrieved 2022-03-13.
68. "SAM", API, I2P, archived from the original on 2013-12-24, retrieved 2013-12-24.
69. "BOB", API, Get I2P, archived from the original on 2013-12-24, retrieved 2013-12-24.
70. "GitHub – subgraph/Orchid". 7 March 2019. Archived from the original on 9 August 2017. Retrieved 20 October 2017– via GitHub.
71. I2P Bittorrent FAQ (forum), DE: i2p2, archived from the original on 2011-11-03.
72. The Hunting of the Snark Project – BitTorrent Application Suite, Klomp, archived from the original on 2013-11-24, retrieved 2013-12-22.
73. "How To for I2P Network Plugin", I2PHelper (Howto) (setup tutorial), Vuze, archived from the original on 2015-02-25, retrieved 2015-02-23.
74. "Rufus – BitTorrent Client". Sourceforge. Archived from the original on 2010-01-07. Retrieved 2006-09-06..
75. "GitHub – majestrate/XD: i2p bittorrent client". 22 March 2019. Archived from the original on 29 July 2017. Retrieved 2 November 2017– via GitHub.
76. "Official Nachtblitz Resource". Archived from the original on 2022-11-01. Retrieved 2022-11-01.
77. "r/i2p – Introducing MuWire – a file-sharing application for I2P". reddit. 31 May 2019. Archived from the original on 2022-04-07. Retrieved 2019-12-17.
78. "Shutdown notice and Java I2P warning (#178) · zlatinb/muwire@8dbd094". GitHub. Retrieved 2024-05-03.
79. "Vuze Speeds Up Torrent Downloads Through "Swarm Merging"". TorrentFreak . 20 March 2015. Archived from the original on 17 October 2017. Retrieved 4 June 2016.
80. "I2PHelper HowTo". VuzeWiki. Archived from the original on 20 October 2017. Retrieved 4 June 2016.
81. "StormyCloud – I2P Outproxy | I2P Anonymous Network". stormycloud.org. Retrieved 2023-07-24.
82. i2p/i2p.i2p-bote, The I2P Project, 2024-03-06, retrieved 2024-03-08
83. Introducing I2P, Nov 10, 2015, archived from the original on November 25, 2015, retrieved November 11, 2015
84. "PurpleI2P/i2pd". GitHub. Archived from the original on 2018-10-04. Retrieved 2018-08-20.
85. "Invisible Internet Protocol Daemon". i2pd.website. Archived from the original on 2018-08-20. Retrieved 2018-08-20.
86. "Kovri". Archived from the original on 2017-11-07. Retrieved 2017-10-30.
87. "What is the difference between i2pd and Kovri?". StackExchange. Retrieved 4 March 2017.
88. "Kovri – Moneropedia". GetMonero. Archived from the original on 5 March 2017. Retrieved 4 March 2017.
89. "What use cases will Kovri have for Monero?". StackExchange. Archived from the original on 2023-01-17. Retrieved 2017-03-04.
90. Privacy Solutions project, archived from the original on 19 April 2018.
91. List of ongoing Privacy Solutions projects, archived from the original on 2021-05-07, retrieved 2022-08-27.
92. "Invisible Internet Protocol Daemon". i2pd.website. Archived from the original on 2018-08-20. Retrieved 2018-08-20.
93. Active development, The Privacy Solutions, 22 September 2022, archived from the original on 12 November 2014, retrieved 16 January 2015
94. Active development, Purple I2P, 22 September 2022, archived from the original on 4 February 2016, retrieved 7 February 2016
95. Android App Releases, archived from the original on 2014-12-15, retrieved 2014-12-15
96. Discontinued, Nightweb, archived from the original on 2017-07-04, retrieved 2015-04-26.
97. "Add I2P support using I2P SAM by vasild · Pull Request #20685 · bitcoin/bitcoin". GitHub. Archived from the original on 2021-03-03. Retrieved 2021-04-03.
98. "I2P con 2015 – Growing the Network, Spreading the Word, 03:41". YouTube. Archived from the original on 2022-04-07. Retrieved 2018-06-30.
99. "Intro". I2P. Archived from the original on 6 April 2016. Retrieved 4 June 2016.
100. "Naming and Addressbook – I2P". geti2p.net. Archived from the original on 29 March 2016. Retrieved 4 June 2016.
101. "Tunnel Routing". I2P. Archived from the original on 26 March 2016. Retrieved 4 June 2016.
102. "The Network Database". I2P. Archived from the original on 7 March 2016. Retrieved 4 June 2016.
103. Kack, Christopher (2012-09-11). "Layer 7 DOS against I2P darknet". Kejsarmakten:Development. Archived from the original on 2012-10-14. Retrieved 2021-03-13.
104. Bazli, Behnam; Wilson, Maxim; Hurst, William (2017-01-01). "The dark side of I2P, a forensic analysis case study". Systems Science & Control Engineering. 5 (1): 278–286. doi: 10.1080/21642583.2017.1331770 .
105. Storm, Darlene (2014-07-24). "Zero-day broker exploits vulnerability in I2P to de-anonymize Tails users". Computerworld . Archived from the original on 2020-09-29. Retrieved 2021-03-13.
106. "I2P patched against de-anonymizing 0-day, Tails integration still to follow". Help Net Security. 2014-07-29. Archived from the original on 2020-12-10. Retrieved 2021-03-13.
107. "0.9.14 Release – Blog – I2P". geti2p.net. Archived from the original on 2021-04-22. Retrieved 2021-03-13.
108. "I2PCon: Mission Accomplished – Blog". I2P. Archived from the original on 10 June 2016. Retrieved 4 June 2016.

External links

• Official website