Suggestion
Tixati's developer has proposed updates to the BitTorrent protocol, starting with Version 3 and extended in Version 3.1.
Version 3 focuses on retiring SHA-1 and integrating modern hash algorithms (e.g., SHA2-256, SHA3-256).
Version 3.1 builds on this with proof-of-work for info integrity, protections against DHT metadata sniffing, and enforced encryption in peer connections. These are extensions of the existing protocol, maintaining full backward compatibility.
Implementing these updates in I2PSnark would enhance security and ensure compatibility with modern torrents.
Key specifications:
-
Protocol Version 3
-
Protocol Version 3.1
-
Full BitTorrent Specification
If these changes align with I2PSnark's scope, implementation in an upcoming release would be appreciated.
I tried to find a proper GitHub page to raise issue for this but that snark repository has not been updated since 2020, so I attached it here.
Update January 2026
Update = https://forum.tixati.com/support/8586

Suggestion
Tixati's developer has proposed updates to the BitTorrent protocol, starting with Version 3 and extended in Version 3.1.
Version 3 focuses on retiring SHA-1 and integrating modern hash algorithms (e.g., SHA2-256, SHA3-256).
Version 3.1 builds on this with proof-of-work for info integrity, protections against DHT metadata sniffing, and enforced encryption in peer connections. These are extensions of the existing protocol, maintaining full backward compatibility.
Implementing these updates in I2PSnark would enhance security and ensure compatibility with modern torrents.
Key specifications:
Protocol Version 3
Protocol Version 3.1
Full BitTorrent Specification
If these changes align with I2PSnark's scope, implementation in an upcoming release would be appreciated.
Update January 2026
Update = https://forum.tixati.com/support/8586