_R_rlms·Jul 2, 2016
C++, stable on the network: https://github.com/PurpleI2P/i2pd
C++, active development: https://github.com/monero-project/kovri
Go, pretty new (my project!): https://github.com/hkparker/go-i2p
In I2P: Invisible Internet ProtocolPurpleI2P
i2pd
C++2015–2026
PurpleI2P / i2pd
i2pd
🛡 I2P: End-to-End encrypted and anonymous Internet
15Distinct people
18Mentions
0Explicit recommenders
4.3KGitHub stars
What to know before exploring
What it is
🛡 I2P: End-to-End encrypted and anonymous Internet
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- monero-project/kovri · linked in 4 of the same discussions
- hkparker/go-i2p · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 11:34:28 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year18 dated mentions
Observed mentions: 2015-04-01 20:14:02 UTC to 2026-02-06 04:00:34 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 6 | 1 | 5 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
6 sources> Thanks for contributing to I2P!
;) My contributions are relatively minor and I2P (as well as other crypto systems) is something I really believe in.
> Do you have any thoughts on HORNET? Could I2P benefit from a more stateless routing mechanism as opposed to tunnels in the far future?
It's been a while since I read the HORNET paper, but as I remember it, HORNET relied heavily on ISP level cooperation which is just not realistic.
However, the idea of reducing state is a very good one. Going forward I hope to see more cryptographic systems that aspire to reduce overall state.
> I'm working on Go implementation here: https://github.com/hkparker/go-i2p. Haven't made to irc2p to introduce myself yet but I will. Are there any devs who might be interested in contributing?
Currently there are 3 implementations of I2P apart from yours. The orig
Read the rest
inal java one, i2pd[1] and kovri[2]. We all cooperate and discuss specifications to maintain interoperability. However the alternative implementations are not maintained under the I2P project as the developers of them desire to be separate.
I was previously unaware of your Go implementation, but you should definitely head over to #i2p-dev and say hi. You can find me under the nick hottuna there.
> Privacy of developers seems a priority. Without any detail of course, can you comment on how necessary this has been. Is it irresponsible of me to work on an implementation in the clear?
About privacy, people have taken various stances. Some a truly anonymous, some are semi anonymous, and some like me are not anonymous. Maintaining privacy for a while might be a good idea. You can always get less anonymous, but going the other way is harder.
[1] https://github.com/PurpleI2P/i2pd
[2] https://github.com/monero-project/kovri
there is a c++ implementation of I2P[0].
0. https://github.com/PurpleI2P/i2pd
In Serverless Sync in Web Apps Using Bit TorrentIf you feel brave, you could try the C++ implementation of the i2p router, purplei2p[1] (aka i2pd[2]). Last time I tried, there were a few rough edges, but it is now over two years old, so it has probably improved (or you may even improve it yourself!).
[1] https://purplei2p.github.io/
[2] https://github.com/PurpleI2P/i2pd
In Serverless Sync in Web Apps Using Bit TorrentI2pd (I2P on C++) 2.7.0 released
1 points · Open discussionI wonder, why they have chosen Freenet? Not I2P [1] as much more modern alternative and active community, bigger and faster network, bigger dev crew.
Also I'd like to mention C++ implementation [2] of I2P client, since it's more important for bringing it on the microcontrollers, IoT, mobile devices, like Tor. It will produce smaller binary and less memory footprint.
[1] https://geti2p.net/en/
[2] https://github.com/PurpleI2P/i2pd
In Our 2016 Open Source Donations