IslandChat, a free chat site with roulette now supports I2P!

You can access it with this link: http://ji34zyv5j526gflnyw5jym45zt6uvk7x6x2vq3ccjyaq7ntjt4ka.b32.i2p

Be aware, HTTPS is required for video chat to work in browsers, so this link will redirect you to the actual address with HTTPS enabled. Once there, your address book will have 2 addresses; one is the HTTP with redirect, and the other is the real address. If you try accessing the real address without HTTPS, it won't work.

Javascript is also required for the site to function.

Happy chatting!

Ihr könnt jetzt @artixlinux via @i2p herunterladen.

https://forum.artixlinux.org/index.php/topic,9687.msg57989.html#msg57989

I installed I2P on a Linux laptop. For the moment I'd prefer not to have I2P to start automatically as system service. The installation guide says that after installation I can simply run i2prouter start, which starts the service and opens the router console on my browser; I've configured the router.

Question 1: what's the best way to shut down router and service, when I need to? The guide above says I can use the command i2prouter stop; but I also see buttons on the browser console and on the tray on the taskbar.

Question 2: I've also noticed that sometimes after i2prouter start I get asked again to configure the router. How do I make sure the configuration is saved once and for all?

Unfortunately I didn't find anything about these specific points in guides or FAQs.

Thanks for helping!

This update focuses on critical stability improvements, memory management, and the initial infrastructure for I2P integration. We've also addressed several UI bugs and search logic inconsistencies to provide a smoother user experience.

New Features

• I2P Integration: Added the foundational configuration infrastructure for I2P, including a dedicated UI settings panel and registration within the options dialog
• JDK 26: Updated to JDK 26 bundled runtime
• Telluride Build 44: Latest Telluride Video Downloader improvements

🛠️ Bug Fixes & Stability

• Memory Leak Prevention: Implemented bounds on previously unbounded image and icon caches to stop excessive memory consumption
• Crash Fix: Resolved a specific crash that occurred when users pasted non-video URLs into the search bar
• Linux Improvements: Fixed persistent tray icon issues specifically for users on KDE Plasma (#845)
• Search Logic: Fixed the "Search Tools" filter and overhauled the logic to ensure all search filters now work independently and accurately
• I2P Configuration: Fixed I2PPaneItem return value for applyOptions to ensure settings are saved correctly

📈 UI/UX Refinements

• Speed Accuracy: Fixed a calculation error in the Peers Tab; download/upload speeds are now correctly converted from bytes/s to KB/s for easier reading

I've finally installed the I2P (java) software, and even though I'm not actively using I2P yet, I'm very happy to contribute bandwidth to the network.

I'd like to understand more the difference between I2P and I2Pd. Is it just different software for the same purpose? So it seems from the FAQ here: "I2Pd is a C++ implementation of the I2P protocol. When using I2Pd you will need to edit configuration files, with Java I2P you can do it all within a user interface."

I'd be happy to hear about user experiences on both. Was I2Pd much more difficult to set up? Is it more than just a software difference? Has anyone noticed better stability or other differences with either one?

Thanks for everone's help! 🙏

Warning: AI slop, but might be somewhat interesting to anyone wanting an overview.

Hey guys,

I am running an I2Pd-Node on my raspberry pi somewhere in Germany and I am loving it so far.

About the ethical implications I am at peace with me, because I know, that it's not possible to allow good things without allowing the bad things too.

Sometimes I am a little bit concerned about, what a paranoid government could do. Technically - I don't know what I am forwarding. And since we're not talking about providing an exit-node (to clear-net) like we usually do with Tor, the risk should be greatly reduced as well.

As far as I know, theoretically this scenario could be possible: A large marketplace for illegal stuff appears within the I2P-Network. Law enforcement connects to it and tries to identify the "hops" between them and the marketplace (one by one) and my node is one of it. I know how crazy this sounds. Not very likely, but not impossible as well.

How do you think about this? Are there any recommended precautions you could take to prove you're not the criminal, if LE surprisingly knocks at your door?

~sp3ctre

People's websites get pummeled by LLM companies scraping the web. I bet they don't use nor scrape I2P though. Would using eepsites be a remedy?

/etc/i2pd/i2pd.conf contains number of listening ports configuration (actually 10 or more when you look for "port"). Which ones should I open in firewall so other people can connect my node? Excluding ones that are meant for management of my node. I manage the node only locally.

So far I have only open/forwarded one port, one that is set a few lines below the line "## Port to listen for connections" that certainly allows relaying traffic for other I2P peers per the http://127.0.0.1:7070/ traffic stats.

Services HTTP Proxy	Enabled
SOCKS Proxy	Enabled
BOB	Disabled
SAM	Enabled
I2CP	Enabled
I2PControl	Disabled

From that other site...

‐-----------

Hi everyone,

I’ve been working on a project called OTRv4+ – an OTRv4 client that adds post‑quantum cryptography to every layer of the protocol. It’s a single‑file Python app (with three small C extensions) that runs on IRC, supports I2P/Tor, and even runs on a phone via Termux.

Why post‑quantum?

If a quantum computer breaks X448 tomorrow, your past and future messages are still protected. The key exchange uses Triple X448 + ML‑KEM‑1024, authentication uses Ed448 ring signatures + ML‑DSA‑87, and the ratchet brace key rotates via fresh ML‑KEM‑1024 at every DH epoch. All symmetric crypto uses SHA‑3 / AES‑256‑GCM, which are quantum‑resistant at the symmetric level.

What makes it different?

· No liboqs – I used OpenSSL 3.5+ native FIPS 203/204 providers for ML‑KEM and ML‑DSA.

· Single‑file Python (~12k lines) – the whole protocol is in one file to make auditing easier.

· 224 tests – covering ratchet torture, state forks, wire format fuzzing, and everything in between.

· Runs on Termux – I tested it on my phone with I2P on Libera.Chat.

Comparison with Signal PQXDH

Signal’s PQXDH adds ML‑KEM to the handshake but explicitly says “Authentication in PQXDH is not quantum‑secure”. OTRv4+ uses ML‑DSA‑87 to make authentication post‑quantum as well – at the cost of losing PQ deniability (a known open problem). I think it’s a worthwhile trade‑off for IRC where deniability is less critical.

If you want to try it:

· Git clone: https://github.com/muc111/OTRv4Plus

· Requires Python 3.9+, OpenSSL 3.5+, and a C compiler.

· Works on Termux, Linux, probably other Unix‑likes.

· Supports I2P, Tor, and clearnet with auto‑detection from the hostname.

Feedback / Contributions

I’d love to get your thoughts – issues, pull requests, or just a “hey, this works on my setup”. If you’re interested in a commercial license for proprietary use, please open an issue with the label commercial-license.

Cheers!

From that other site.

‐-------------------------------

Hey guys, I've been building open-source launcher for i2pd that makes getting started with I2P as simple as possible.

What it does:

• Bundles a forked i2pd build with a preconfigured browser

• One-click start — no manual configuration needed

• Native .gn TLD support (custom domain resolution built into the i2pd fork. .gn and .i2p sites working in i2p network)

• Auto-downloads browser

Current state:

First public beta (v0.1.0 "Ronin"), Windows only for now. It works but expect rough edges — bug reports are very welcome.

GitHub: https://github.com/vialolis/GrayNet

Linux and Android ports are planned. Feedback appreciated.

Hey folks!

I just learned about I2P and already tested it successfully with I2Pd on my debian PC.

But I want to support the network 24/7 so I need to set it up on my raspberry pi 4 and I plan to use it from LAN.

So I installed it like described in the documentation for debian (https://docs.i2pd.website/en/latest/user-guide/install/#linux).

I changed my config via sudo nano /etc/i2pd/i2pd.conf and edited some things like this:

[http]
enabled = true
address = 0.0.0.0
port = 7070

[httpproxy]
enabled = true
address = 0.0.0.0
port = 4444

and I restarted with sudo systemctl restart i2pd

I am using the I2Pd-Firefox-Bundle and I changed the Firefox-settings (Settings -> Network Settings) to this:

(pointing to my raspberry pi)

.i2p-Sites are working well so far, but I am not able to open the webconsole with this configuration. I try to open it with http://192.168.178.26:7070/ but I only get host mismatch.

What am I doing wrong?

Thanks in advance!

~sp3ctre

Edit:

A solution has been found with nginx:

On the Pi:

sudo apt update
sudo apt install nginx

Followed by:

sudo nano /etc/nginx/sites-available/i2pd

Edit to:

server {
    listen 8080;
    server_name _;

    location / {
        proxy_pass http://127.0.0.1:7070/;
        proxy_set_header Host localhost;
    }
}

Enable the file:

sudo ln -s /etc/nginx/sites-available/i2pd /etc/nginx/sites-enabled/

Deleted the nginx-default-site

sudo rm /etc/nginx/sites-enabled/default

In this video I show you how to use Linux in an "ungovernable" way by fetching packages and distro iso's over the I2P darknet.

It's been going on for awhile now. Most of the times sites won't load. Reseting i2p doesn't solve the issue.

Domain Transition

After several years, the I2P project has re-acquired the i2p.net domain and has begun transitioning from geti2p.net to i2p.net.

A custom redirector script ensures that geti2p.net links automatically resolve to their equivalent pages on i2p.net.

Built for Reliability and Speed

The new site runs on Hugo as a fully static build. Every page is pre-rendered HTML no databases, no runtime rendering, and no unnecessary overhead.

Pages load instantly and can be mirrored anywhere with ease.

That matters for a project like I2P. Static architecture makes redundancy simple. Mirrors can be deployed quickly, and the site remains resilient across clearnet, I2P, and Tor.

JavaScript-Free by Default

With the exception of the donate page (which requires a third-party payment widget), the site runs without JavaScript.

• Dark/light mode is handled server-side
• Navigation is pure CSS
• Documentation feedback and banner controls function without client-side scripts

If something could be implemented without JavaScript, we chose that route.

Documentation and Search Improvements

We’ve expanded and reorganized the documentation with full search across specs, guides, and overview content.

Documentation pages now include a lightweight feedback system so users can vote on whether a page was helpful.

Community-Driven Features

We’ve added a feature request system where users can submit ideas and vote on priorities. Development direction should reflect the needs of the people using the network.

There is also a lightweight polling system for gathering community input. It works across clearnet, I2P, and Tor with appropriate endpoints for each.

Expanded Guides and Localization

A new guides section launches with platform-specific installation instructions for Windows, macOS, and Linux.

We are actively looking for community-contributed guides to expand it further.

The entire site is available in 13 languages:

English, Spanish, Korean, Chinese, Russian, Czech, German, French, Turkish, Vietnamese, Hindi, Arabic, and Portuguese.

Supporting the Project

I2P is free and open for everyone to use, but operating the project involves real-world expenses infrastructure, hosting, development, and ongoing maintenance.

We are now accepting donations. Support is available through cryptocurrency as well as credit, debit, and bank transactions.

All donations are tax-deductible in the United States.

If you rely on I2P and want to help ensure its continued development and availability, financial support makes a direct impact.

Downloads Overhaul

The downloads page has been rebuilt to reduce confusion and improve verification:

• Automatic OS detection highlights the recommended installer
• Direct, mirror, I2P-native, and Tor download options
• GPG signatures and SHA256 checksums provided inline
• Clear “Coming Soon” indicators when releases lag

What’s Next

This rebuild is only the foundation. The next step is expanding practical, real-world documentation especially step-by-step guides for different environments, use cases, and troubleshooting scenarios.

We’ve launched a dedicated guides section with installation coverage for Windows, macOS, and Linux. But we know the community has knowledge that goes far beyond basic setup.

If you’ve written a guide, solved a niche issue, deployed I2P in an interesting environment, or documented a workflow others could benefit from, we’d like to include it.

Community-driven guides will make this site significantly more useful than anything we can produce alone.

If you’re interested in contributing a guide, let us know.

Feedback, bug reports, and contributions are welcome.

Support your anonymous network.

[2.59.0] - 2026-02-09

Added

• Post-quantum NTCP2 crypto(ML-KEM-512, ML-KEM-768, ML-KEM-1024) support if openssl >= 3.5.0
• UDP associate for SOCKS5 proxy
• Trusted routers list for first hop per tunnel
• "i2p.streaming.maxConnsPerMinute" and "i2p.streaming.maxResends" params
• Limited connectivity mode
• *.b32.i2p addresses for SAM datagrams
• Limiting the number of datagrams sent to maintain the consistency of session encryption through UDP tunnels
• Desktop app mode for Haiku
• Ability to suppress X-I2P-* headers for HTTP server tunnel
• Multi cloves garlic message for datagrams
• Network error and testing metrics for I2PControl
• Handle reseed address redirection
• Throttle excessive number of tunnel build message from the same peer
• Localization to Esperanto, Filipino and Finnish

Changed

• Return base64 of ident instead full address for Datagram3 in SAM
• Send ratchet session response for unidirectional traffic for I2CP
• Set default number of generated tags to 800 for a datagram destination
• Check ML-KEM encaps_key section length before decryption
• Create new stream only if bandwidth is available. Close non-responding streams
• Use Datagram3 by default in UDP tunnels
• Floodfills are not introducers
• Disable ipv6 if global ipv6 interface not found
• Network congestion detection algorithm in streaming
• Reply with relay tag only if accept tunnels
• Case-insensitive Content-Length header in I2PControl
• Increase PID string length
• Don't communicate with routers of version < 0.9.58
• Webconsole layout improvements
• Localization to Hebrew
• Reseeds list

Fixed

• Incorrect params length calculation for SAM streams
• Unexpected index in SymmetricKeyTagSet
• Incorrect preferred crypto type if i2cp.leaseSetEncType is not specified
• Decoding %00 in url
• Thread-unsafe localtime()
• NetDb crash on stop
• Peer test result OK in case of another recent peer test
• Published port if full-cone NAT
• Missing trailing newline in I2PControl JSON response
• Language selection in webconsole

The I2P network is currently experiencing an attack by unknown actor(s). Tens of thousands of malicious routers have been introduced to the network that are not actually routing any traffic. This is causing:

• Extremely low tunnel build success rates
• Overall network congestion
• Degraded performance for legitimate users

The I2P development team is aware of this situation and actively investigating mitigations.

We will post updates to this thread as the situation develops. Thank you for your patience.

Update: 2/4/2026 11AM CST - Fixes are being tested now.

Update: 2/4/2026 7pm EST - Some changes were implemented in a new build to help combat the issue. Right now I only have the binaries for apple silicon.

IRC is semi alive, if you update your IRC config to use irc.echelon.i2p:6667 you should be able to connect.

https://files.i2p.net/I2P-2.10.0-5.dmg

2.10.0-5 i2pupdate.zip

https://files.i2p.net/i2pupdate-2.10.0-5.zip

As of 2025 the P2P System Tixati has full I2P support.

How to configure it for use with I2P: https://support.tixati.com/i2p

Full changelog here: https://tixati.com/news

Sadly not OSS, so "Caveat Emptor".

Edit: Forgot that it's 2026 now.

I just installed and started i2pd following the Arch Wiki at https://wiki.archlinux.org/title/I2P

I opened up the welcome page at 127.0.0.1:7070, which looks like this:

Are there any settings at the welcome page or tweaks that I can apply to the config file to optimize my router? All I want to do is to contribute bandwidth at the moment, not necessarily use the network myself. I have a 1 Gbps connection that never gets saturated.

I saw for instance a setting called "Transit tunnels limit". Is it beneficial for peers if I increase this?

Thanks in advance!

cross-posted from: https://sh.itjust.works/post/52298822

The nginx server block is listening on a port other than 80, if that matters. It's all my VPN provider will allow me to forward.

Has there been a major blackout of the internet worldwide or even in part ?? It's showing cloudflare error 500 on my device.

I am trying to make sure I am ready for 2.11 since it will require Java 17. But I tried getting Java 24 JDK SE and removed Java 8 JRE and then I2P router launcher said I didn't have Java. I tried looking for JRE above 8 but I just keep seeing 24 JDK. The I2P site links to tanuki for a wrapper of the Community Edition but they say there isn't a x64 version of Community Edition.

Does anyone have links for a Windows x64 JRE that is 17 or higher? I have reinstalled Java 8 JRE for now since it fixed the issue of running the I2P router launcher. I have only ever needed the 8 or lower JREs so I am a real noob at Java stuff.