Dear Tixati maintainers,

qBittorrent, libtorrent and BiglyBT developers have confirmed they will add support for Tixati’s v3 and v3.1 protocols as soon as they become official BEPs or even drafts of the presented BEPs.

To enable universal adoption across all major clients, please submit formal BEP proposals for both v3 and v3.1 at:
https://bittorrent.org/beps/bep_0000.html

This single step will bring your innovations to the entire BitTorrent ecosystem.

Thank you for driving the future of the protocol.

I will definitely be submitting a BEP this week.  I just need a chance to proof-read the specification, and make sure there are no last-minute changes, corrections, or clarifications.

I designed the v3 and v3.1 protocols to be as easy to implement as possible, so I am very hopeful that other client devs will be able to add this without much effort.  Getting away from SHA-1 is very important.  And I also think the problems with DHT scraping more than justify the minor amount of work needed to implement v3.1 in any client.

does it support mldht ipv6？bigly bt support mldht ipv6

Yes, of course it supports mainline DHT over IPv6.  The DHT is unchanged.

Hi KH,

I hope you're doing well.

I wanted to follow up on the BEP for proposals for BitTorrent v3 and v3.1 protocols.

It seems there hasn't been any recent submission, and other teams have asked if this effort is still ongoing or if it's been abandoned.

Could you provide an update on the current progress? Are there any submissions or milestones coming up soon?

Thanks for your attention to this! Looking forward to hearing from you.

Definitely going to submit the BEP soon, hopefully by the end of the month.  I have the spec available at https://tixati.com/specs/bittorrent/v3.1  but I need some time to rewrite it to be a little more verbose and precise before submitting a BEP.

This is a high priority task, I'll definitely get it done soon.