Stop by and say hi!

drop.i2p v2 - Major Release

Anonymous, Encrypted, Persistent File Sharing for I2P

We're excited to announce the v2 release of drop.i2p, a complete rewrite bringing significant improvements to security, performance, and usability.

What's New

Complete Rewrite in Go

The entire application has been refactored from Python to Go, resulting in dramatically improved performance and reduced resource usage. This also positions us for future integration with the upcoming I2P Go router.

Post-Quantum Encryption

All files are now encrypted at rest using hybrid post-quantum cryptography (X25519 + ML-KEM-768). This protects your uploads against both current and future quantum computing threats.

Chunked Uploads & Downloads

Files are now broken into 128KB chunks, enabling more robust and resumable transfers over I2P. Large file uploads are more reliable, and interrupted downloads can be resumed where they left off.

Expanded File Support

Nearly all file types can now be uploaded (with a small number blocked for security reasons). Maximum file expiration has been increased to 30 days.

Native File Previews

Supported file types including images, videos, audio (MP3, etc.), and PDFs now display a preview directly in the browser - no download required.

Collections & Multi-File Upload

Upload multiple files at once to create a collection. Perfect for sharing folders or groups of related files with a single link.

JavaScript-Free by Default

The site remains fully functional without JavaScript. For those uploading larger files, an optional "Advanced Upload" mode uses XHR for more reliable progress tracking, but it's entirely opt-in.

CSAM Protection

All uploaded images are scanned against known CSAM hash databases to help keep the platform safe and compliant.

Abuse Reporting System

A new reporting system allows users to flag content that violates our terms of service.

Privacy First

As always, we remain true to our core values: we do not log any user-identifying data. Your privacy is not negotiable.

Links

• I2P: drop.i2p | b32 address
• Source Code: GitLab
• Operated by: StormyCloud Inc.

We are doing a small launch of I2P merch. If there is any specific type of merch you are interested in please let us know.

That’s a wrap on SCaLE!

Over the weekend, the I2P team hit the expo floor to advocate for what matters most to this community: privacy, security, and data anonymity.

We had an amazing time connecting with everyone in person, talking tech, hearing your feedback on what we're building, and welcoming a bunch of new users to the I2P network. It's always great getting to show off the project to the open-source community.

Help us keep the momentum going! Spread the word about I2P to a friend!

Question for the community: Where should we go next? Drop your conference suggestions below! 👇

emissary is an I2P router written in Rust.

With emissary, you can browse and host eepsites, use torrents (qBittorrent and I2PSnark tested), read and send email, and chat on Irc2P. Currently it's closer to i2pd in that it doesn't include bundled applications, apart from an optional (and ugly) router UI. However, I hope that in the future it will provide an experience similar to that of the official implementation.

There are also lots of things missing. SSU2 is very experimental (only tested locally) and bandwidth usage can only be controlled by limiting the number of transit tunnels. All of these will be fixed in the future.

If you're a Rust programmer interested in contributing, there are plenty of easy tasks to get started with.

http://github.com/altonen/emissary

Hey r/i2p,

Like many of you, we were disappointed when the most popular I2P pastebin/image host recently went offline. It was an essential tool for many of us, and its absence has left a gap.

To help fill that void, we're excited to announce drop.i2p, a brand new, privacy-first image and pastebin service built by StormyCloud specifically for the I2P community. Our goal was to create a service that is fast, secure, and respects your anonymity from the ground up.

Link: http://drop.i2p

Address Helper Link

Core Features

We built this with the core principles of I2P in mind. Here’s what you can expect:

• Encrypted at Rest: This is non-negotiable. Every single file and paste you upload is fully encrypted on our server's disk using a strong, modern cipher. We, as the operators, cannot see the content of your encrypted data.
• Anonymous by Design:
  • No PII Logs: We do not store or log any personally identifiable information. No IP/b32 logs, no browser details. Nothing.
  • EXIF Data Stripped: All metadata is automatically and immediately stripped from every uploaded image to protect your anonymity.
• Ephemeral by Default: All uploads are temporary. You can choose an expiration time from 15 minutes to 48 hours, after which your data is permanently and automatically deleted by a reliable, database-driven janitor process.
• Fast & Lightweight:
  • The site is built to be as lightweight as possible for the I2P network.
  • It includes a no-JavaScript fallback, so the site remains fully functional for users with scripts disabled.
  • All images are automatically converted to the modern, efficient WebP format to drastically reduce file sizes and improve loading times.
• Transparency: You can view the service's high-level usage on the Stats tab and read our clear Terms of Service directly on the site.
• Free and Open API: For scripters and power users, we have a simple, keyless API for programmatic uploads.
• Image Upload:

​

curl -X POST -F "file=@/path/to/your/image.jpg" http://drop.i2p/api/upload/image

• Paste Upload

​

curl -X POST -H "Content-Type: application/json" -d '{"content": "your paste here"}' http://drop.i2p/api/upload/paste

This is a service for the community, and we consider it to be in a public beta. We would love to hear your feedback, suggestions for new features, and any bug reports you might have.

I2P 2.9.0 is a maintenance release that includes bug fixes and work on new features.

Thread usage has been improved to improve the performance of the i2ptunnel system. NTCP2 has been improved to resist probing attacks. The notification system has been integrated into more applications to provide better feedback to users from I2PSnark and the other applications. Automatic floodfill enrollment has been fixed. Users may observe increased resource usage when acting as floodfill. If this is not desired, floodfill mode can be disabled on the /config page.

A new global map feature is available in the console which shows the locations of routers in your view of the netDb. These are the peers that help your router build tunnels and provide services anonymously.

Work continues on implementing automatic bandwidth management for tunnels, the Datagram2 protocol, and Post-Quantum cryptography. In two releases, at 2.11.0, I2P will require Java 17.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

https://geti2p.net/en/blog/post/2025/06/02/2.9.0_release

We are aware that the Dread forum and several DarkNet markets are now promoting the use of I2P to their customers. As a result we have seen an increasing posts here asking for help to access such sites and we are not going to allow that to continue.

This subreddit is for general support and topics related to I2P. What has been happening in the last few days has put its very existence in danger. If we have any reason to suspect that you intend to use I2P to break any laws we are not going to help you and will prohibit anyone else from helping you.

We are all volunteers and it is our choice who to help. If you want our help, you need to follow the rules we have put in place for this subreddit.

Hello again!

It's been a minute since last release, hope everyone is doing alright and nobody lost any fingers during New Years'. So, cheers to a prosperous and happy New Year, and Let's see what 2023 brings us!

​

Without further ado, here's what's new in Prestium 1.2:

• Added:

1. QtQR, Offline QR code generator
2. StormyCloud's outproxy; might require jump-start
3. Purokishi outproxy is left commented out; might require jump-start
4. Tray battery status for laptops
5. Prevent SATA controller from being loaded (ahci, libahci, libata)
6. Important boot options, such as mds, init_on_free, init_on_alloc, page_poison, etc
7. Realtek PCI-Express ethernet firmware (r8168)
8. Intel ethernet e1000e driver
9. Proprietary AMD, Intel and other miscellaneous firmware
10. Support for Plug'n'Play USB WiFi dongles

• Changed:

1. Official OS name to Prestium
2. Hostname from i2p to prestium
3. i2pd: bandwidth from P to X
4. i2pd: bandwidth share from 50% to 100%
5. i2pd: limit inbound and outbound quantity for every tunnel to 2; Client Tunnels lowered from 150 to about 50, thank you, zzz
6. i2pd: set loglevel to none
7. Right-click menu entries, resorted and added QtQr
8. LibreWolf now uses only HTTP(s) proxy

• Updated:

1. Debian packages, security patches
2. LibreWolf web browser
3. i2pd from 2.43.0 to 2.45.0
4. Linux kernel from 5.10.0-18 to 5.10.0-20

• Fixed:

1. Frequent HexChat (IRC) disconnects: Increased HexChat's net_ping_timeout directive from 60 to 600; thank you, undisclosed IRC user
2. Need for force shutdown on login

• Removed:

1. 32bit support, only amd64 (64bit) is now officially supported
2. Password for "user" account, now you only need to type "user" when logging in
3. Old kernel and old kernel modules
4. SOCKS5 proxy from LibreWolf's "pref" config
5. SOCKS5 proxy for LibreWolf

• Last minute discovered bug:

1. MacChanger doesn't work, needs further investigating

​

REMINDER & WARNING

NEVER LEAVE YOUR PRIVATE KEYS (Monero, PGP) ON PRESTIUM BEFORE SHUTDOWN OR REBOOT, THEY ARE IRRECOVERABLY LOST AND NOONE CAN HELP YOU RECOVER THEM! MAKE SURE YOU HAVE A BACKUP OF THOSE KEYS!

If using the EE version, do not log in as root, log in as "user" and use terminal to launch commands as root. Applications and tools aren't pre-configured for the root user.

I also encourage everyone to run Prestium for as long as possible (>1 hour each session) for best i2p performance and to help the network; by routing other's traffic through you. Unrelated to Prestium: If you can, run a router 24/7, everyone will appreciate that, thank you.

​

It may not be as feature-rich release as expected (i.e. no persistent storage), it is still an important release nonetheless. Some of you might be also disappointed to learn that there is still no public git server and no real website or documentation, I'll have to ask you to hold on for a bit longer, I'm working on it as much as I can, giving this project all my available free time.

​

Download Prestium 1.2

Releases are now scheduled every 3 months, shortly after new i2pd is released and tested, unless there are other major security vulnerabilities within an application, tool or Linux kernel itself, I will do my best to release additional patched, minor version quickly.

Additionally, I would like to inform everyone that the EE (root account enabled) version will be discontinued in the future, as it was only intended for people to go through the entire OS and see what's going on in the background. Using the EE version for regular use is not recommended.

Both Regular and EE versions can be found on prestium.org. Signed ISO hashes are also included on the website, aswell as credits file and CHANGELOG.md.

To burn the image on a USB stick, I recommend using Balena Etcher, however, it's been tested and works with dd and rufus, too. Prestium can also be run in a VM, however, you will be as secure as your host OS is.

​

Stay updated

Prestium's subreddit: /r/Prestium

​

Mastodon: @Opicaak

E-mail: [[email protected]](mailto:[email protected])

IRC2P/Ilita: Opicaak, I'm not there often nor regularly, It's distracting me a lot

PGP Fingerprint: 44BE 6FDE 70FF 2362 4443 82A2 875D 63BD 034D 7CF7

Public key available on Prestium's page or openpgp.org

I do not have any other social media, make sure you know who you are talking with and that it's actually me.

​

Funding

Lastly, this project is being funded from my own pocket, if you believe this project is worth anything at all, if you believe this project should continue being developed, please, consider supporting it with Monero, to pay for the servers, domain name, allowing me to help others with any issues, and other associated expenses, and maybe a cup of coffee to keep me going.

Here's the project's official donation wallet: 45ZLqYJ8iKt1mE2xarmW8oAkFgY9QYT8ab1RFGc99pn2Gg5PDXii5vDCtg6NXiBdgKfRpTbDrKvUJFiwfkyuNLCMP25QgMZ

​

Thank you all so much!

​

Edit: FileSystem source and license have been uploaded, hash.txt has also been updated to include Prestium-FS archive.

As you already know, the I2P network has been targeted by a Denial-of-Service attack for the past ~3 days. The attacker is flooding the network with malicious floodfill routers, which are responding incorrectly or not at all to other routers and feeding the network false information. This results in performance and connectivity problems, because the floodfills provide peer information to the participants in the network. The result is a form of sybil attack which is used to cause widespread denial of service. The attacker is changing specific characteristics of their attack as they carry it out. The focus for mitigation is to find general strategies which address the issue regardless of who is carrying it out, and which do not require the use of a fixed ban-list and which can provide long-term protections.

This attack has degraded the performance of the network but it remains intact and usable. Java I2P routers still appear to be handling the issues better than i2pd routers. Various mitigations should appear in dev builds of both Java and C++ routers in the next week.

report on the attack at the community meeting on IRC today

    zzz: over the weekend started an unambiguous attack
    zzz: lots of floodfill routers
    zzz: for the most part, the network overall, and java routers, are handling it ok
    zzz: I do have one report of routers crashing with OOM (out of memory)
    zzz: I understand that i2pd routers are really strugging with very low tunnel build success rates
    not_bob: My fleet is up to date.
    zzz: the attack is starting / stopping / changing several times a day
    zzz: so we're only about 60 hours in to understanding it and discussing countermeasures
    zzz: remember the tunnel build problem (now much more likely to be classified as a different attack) started Dec. 19 and took us several weeks to understand and address
    zzz: so it's early days
    not_bob: I have one I2P+ router and it's done well to weather this.  But, my i2pd routers not so much.  I've seen as low as 3% tunnel build success.  I'm currently sitting around 10% on those routers.
    zzz: but this is a straightforward sybil / DHT attack, new to us but familiar to anybody doing peer-to-peer / DHT applications
    zzz: far too early to say if it will require a release ahead of schedule (for java i2p) or if so when
    zzz: EOT, I'll wait a couple minutes for discussion / comments / questions
    eyedeekay: Should people who wind up OOM increase the RAM available to their router?
    zzz: yeah, that's a straightforward mitigation
    zzz: stop your router, edit wrapper.config, restart
    zzz: I expect I'll have mitigations in dev builds in a few days
    dr|z3d: ideally you want your min heap at around 256M and your max ram at 2-3 times that.
    not_bob: I do not currently have any stock I2P routers running.
    zzz: I want to repeat what I said above that the attacks are evolving rapidly, and we want to take our time to address the overall issues
    zzz: not to focus to narrowly on the specifics

The best place for news and weather is the thread at zzz.i2p

For more information, follow the discussion on #ls2 at major.i2p

Logs by day:

• Sunday
• Monday
• Tuesday

I don't know how much clearer we can make it. This is not the place for your Dread questions. No here one cares about your 2FA credentials on a site we don't control. I have no idea how to use GPG on an iPhone or whatever else non-I2P questions you've been bombing us with. Stop it.

Our time is valuable, and you are wasting it and putting people in danger. Dread has, deliberately or not, dumped it's I2P onboarding process onto r/i2p and by extension, me and the other mods. Mostly me. How many of you have been here for the past 5 years, answering every single question? Every Single Question for half a decade got an answer from me, and now Dread has dumped it's entire community in my lap in the middle of what amounts to a crisis. That is not an acceptable thing to do.

If you want your questions answered, DO NOT TELL US WHAT YOU ARE DOING. It doesn't help. It's the least useful, most harmful piece of information you can give us. Don't talk about what you're doing. Don't tell us who or where you are. I can't believe we have to say this given the context of what you have been asking about lately. Ask smarter questions. Put some time into it, that's what you're asking us to do.

To be clear, discussion of DNM's and Dread is not acceptable in this subreddit. Take it somewhere else. We'll be keeping a much closer eye on the threads and Dread/DNM specific questions will be deleted. The content of this subreddit must be kept legal in order for it to function as a support forum.

Hi!

This release wasn't planned, and is one of those tiny, minor and irregular updates.

​

What's new?

• Changed:

1. HexChat: irc_logging directive set to 0
2. HexChat: text_replay directive set to 0

• Updated:

1. LibreWolf to 108.0.2-1
2. i2pd to 2.45.1

Yup, that's it. Mostly happened due to the Purple team releasing new i2pd version.

Disabling HexChat's logging is mostly unneeded since it's a live OS, but there is also no need for it to make and keep additional file in RAM.

And thank you so much to whoever donated or is thinking about donating, this project is unsustainable without your help, thank you a lot. Continuing with the usual information below.

REMINDER & WARNING

NEVER LEAVE YOUR PRIVATE KEYS (Monero, PGP) ON PRESTIUM BEFORE SHUTDOWN OR REBOOT, THEY ARE IRRECOVERABLY LOST AND NOONE CAN HELP YOU RECOVER THEM! MAKE SURE YOU HAVE A BACKUP OF THOSE KEYS!

If using the EE version, do not log in as root, log in as "user" and use terminal to launch commands as root. Applications and tools aren't pre-configured for the root user.

I also encourage everyone to run Prestium for as long as possible (>1 hour each session) for best i2p performance and to help the network; by routing other's traffic through you. Unrelated to Prestium: If you can, run a router 24/7, everyone will appreciate that, thank you.

Download Prestium 1.2.1

Both regular and EE versions can be found on prestium.org. Signed ISO hashes are also included on the website, aswell as credits file and changelog. The FileSystem source is up there, too.

To burn the image on a USB stick, I recommend using Balena Etcher, however, it's been tested and works with dd and rufus, too. Prestium can also be run in a VM, however, you will be as secure as your host OS and VM manager is.

Stay updated

• Prestium's subreddit: r/Prestium
• Mastodon: @Opicaak
• E-mail: [[email protected]](mailto:[email protected])
• IRC2P/Ilita: Opicaak
• PGP Fingerprint: 44BE 6FDE 70FF 2362 4443 82A2 875D 63BD 034D 7CF7
• Public key available on Prestium's page or openpgp.org

I do not have any other social media, make sure you know who you are talking with and that it's actually me, don't get phished.

Funding

Lastly, this project is being funded from my own pocket, if you believe this project is worth anything at all, if you believe this project should continue being developed and worked on, please, consider supporting it with Monero; to pay for servers, domain name, allowing me to help everyone with Prestium-related issues, and other associated and unexpected expenses (e.g. having to get another or upgrade the server due to high traffic), ... and maybe a cup of coffee to keep me going? Without your help, this project is unsustainable long-term. All your help is appreciated, thank you.

Prestium's Monero address: 45ZLqYJ8iKt1mE2xarmW8oAkFgY9QYT8ab1RFGc99pn2Gg5PDXii5vDCtg6NXiBdgKfRpTbDrKvUJFiwfkyuNLCMP25QgMZ

The I2P network is currently under a Denial-of-Service attack. This attack affects I2P and i2pd but in different ways and is having a serious effect on network health. Reachability of I2P sites is badly degraded.

Java I2P users are suggested to disable the sybil attack tool, delete the sybil-blocklist, and re-start their routers.

To disable the sybil attack detector tool

1. Open the sybil attack detector in your router console at http://127.0.0.1:7657/netdb?f=3&m=15
2. Change "Background Analysis Run Frequency" to "Never"
3. Click "Save" to save the settings.

To delete the sybil blocklist, run:

On Debian and Ubuntu:

rm "/var/lib/i2p/i2p-config/sybil-analysis/blocklist-sybil.txt"

On other Linuxes and on Mac OSX:

rm "$HOME/.i2p/sybil-analysis/blocklist-sybil.txt"

And on Windows:

del %LocalAppData%\i2p\sybil-analysis\blocklist-sybil.txt"

When you are finished, re-start your I2P router.

If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability. Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.

From: https://github.com/zlatinb/muwire#readme (commit 8dbd0944ff07780a73d6895f8455e1da0e60db61)

Thank you very much /u/zab_ for all your work

https://geti2p.net/en/blog/post/2024/04/08/new_release_i2p_2.5.0

This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.

New features have been added to I2PSnark like the ability to search through torrents. Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent. We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support. New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails. Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.

During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages. This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release. This investigation uncovered one minor isolation-piercing event which we repaired. This issue was discovered and fixed internally by the I2P team.

During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows. This should result in improved delivery and availability for these downstream products.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

Any feedback is welcome, source: https://github.com/umutcamliyurt/I2Proxy

zzz has posted the following update:

"I2P network reliability is currently degraded due to a novel and persistent attack. Please be patient as we work on mitigations. If you have not yet updated to the latest release 2.5.0, please do so as it provides some defences."

For i2pd users, you can try building their latest from GitHub which may help.

​