Log In     Register    

Help and Support
Ask a question, report a problem, request a feature...
<<  Back To Forum

Implement UDP in I2P [feature request]

by Guest on 2025/08/05 01:26:08 PM    
Implement UDP in I2P.

As of June 2025, UDP support has been started by I2P team.

More info = 1] https://geti2p.net/spec/proposals/160-udp-trackers

2] https://geti2p.net/en/docs/applications/bittorrent

3] https://geti2p.net/spec/udp-announces
by Guest on 2025/08/17 06:57:47 AM    
✅ Purpose
Enable UDP Tracker Support in I2P

Traditionally, I2P did not support UDP-based BitTorrent trackers, which limited compatibility with many torrents.
Proposal 160 introduces a specification to allow UDP BitTorrent tracker announces over I2P, helping to bridge the gap with Clearnet standards.
Enhance BitTorrent Usability in I2P

This upgrade is aimed at making BitTorrent within I2P more efficient and standardized, improving performance and compatibility.
Lightweight Alternative to HTTP Trackers

UDP is a low-latency, connectionless protocol, suitable for fast, scalable tracking compared to HTTP-based solutions.
Improved Privacy and Anonymity

Ensures that UDP announces respect I2P's anonymity model, using existing datagram delivery methods like SSU2 and NTCP2 securely within I2P.

✅ Use Case
Users Sharing Torrents Anonymously

I2P users can now use UDP trackers (like opentracker.dg2.i2p, opentracker.simp.i2p and opentracker.skank.i2p) for torrent sharing with increased efficiency.
BitTorrent Clients within I2P (e.g., qBitTorrent, BiglyBT, I2PSnark)

Clients that implement the proposal can now announce to and scrape from UDP trackers, similar to Clearnet usage.
Tracker Operators

Can now deploy Opentracker with the updated zzzot code (v0.20.0-beta3) to support UDP announce endpoints securely within the I2P network.

✅ Extra Information
Security and Specification Details

UDP announces are tunnelled securely using existing I2P datagram transport.
The proposal allows both IPv4 and IPv6 address types, but mandates usage of I2P destination hashes (as opposed to IPs).
Backward Compatibility

Clients and trackers gracefully fall back to HTTP if UDP is not available, ensuring no breakage for older clients.
Current Status

The feature is reviewed, approved, and under active testing. Early signs show stable functioning of updated trackers and clients.
Tracker Implementation

The zzzot tracker software has been updated (0.20.0-beta3) to support this.
The Opentracker instances opentracker.dg2.i2p, opentracker.simp.i2p and opentracker.skank.i2p now run this version.

✅ Citations
Proposal 160 - UDP Trackers in I2P
🔗 https://geti2p.net/spec/proposals/160-udp-trackers
Specifies how to implement UDP BitTorrent announces over I2P.
I2P & BitTorrent Overview
🔗 https://geti2p.net/en/docs/applications/bittorrent
Explains usage of BitTorrent inside I2P and benefits of anonymous seeding.
UDP Announces Spec
🔗 https://geti2p.net/spec/udp-announces
Describes the wire protocol for UDP announces and their use in I2P.
Status Update - July 2025
📅 Approved, tested in dev builds 2.9.0-4/-5, zzzot v0.20.0-beta3 active
Live deployment of UDP trackers confirmed.
by Guest on 2025/08/19 08:35:14 PM    
any progress on this?
by Guest on 2025/08/21 08:21:32 AM    
i2psnark standalone now supports udp trackers. As both tixati and i2psnark run on I2CP, I think now tixati can apply those settings
by Guest on 2025/08/30 11:23:18 AM    
Thank you very much for implementing this feature.
I have checked with few I2P torrents and it is working properly.
by Guest on 2025/08/30 03:11:57 PM    
Tixati version 3.37 has added support for UDP trackers in I2P and its working great.




This web site is powered by Super Simple Server