I think other torrent developers will be more kind towards Tixati's new protocols if he renames them to

v3 = v1.5 and

v3.1 = v1.8

I mean this is the best way to put it considering the documentations presented by Tixati itself.

I followed up on your earlier point about how the newer protocol versions are classified and asked a Tribler developer, and their view seems to line up with what you said.

From what I understand, Tixati protocols v3 and v3.1 are more like extensions or iterative updates to protocol v1, rather than completely new protocol frameworks like BEP52 ( https://bittorrent.org/beps/bep_0052.html  ).

So from that perspective, it might be more accurate, at least in terms of naming and documentation, to treat them as incremental updates, like part of a v1.x series, instead of calling them entirely new versions.

I2P developer confirms they will not move forward with this implementation until and unless a BEP is submitted via official https://bittorrent.org/beps/bep_0000.html  or https://github.com/bittorrent/bittorrent.org/pulls

Well, the ball in now in Tixati developer's court, if he wants this feature adopted widely or not.

One thing I don't like about "v3" is how it is presented in the Tixati client.
Calling v2 "old" and hiding it is a bit disingenuous, especially since "v3" is just v1 with extra steps.

Backwards compatibility is one thing, but it changes the infohash anyway.

My man, as a layman, I did whatever I could do to convince all torrent developers to implement v3. Now, it is your turn to explain to developers. I think they need some developer talks to understand the things that a layman cannot tell them or layman does not understand itself.
You need to now, take up the mantle and come out to solve developer's confusion or doubts or whatever they have. https://github.com/arvidn/libtorrent/issues/8047#issuecomment-4105702173

BEP v3.1 still not avaialble and neither is BEP v3, on BitTorrent GitHub.

My opinion as a normal user (quick thoughts, hopefully I'm not wrong about anything): I think both the v3 and v3.1 protocols are brilliant, but should be done and named differently. I think the security improvement in v3 and v3.1 is critical, so the approach of implementing it in a backwards-compatible way is correct compared to the approach of waiting for v2 to be adopted more broadly. I like that there's a way to specify the cryptographic hash algorithms, instead of having a hardcoded algorithm. I think v2's property of allowing recognizing identical files across different torrents is a groundbreaker for potentially better longevity for torrents and saving disk space for users.

I think v3 should be called an extension of v1, or call it v1.5 (because of the major improvement it brings, rather than v1.1 for example which doesn't do justice with the improvement). When creating a new seed, it could show as a sub-checkbox under v1 saying something like "Augment with secure metadata (fully backwards compatible). Exclusive to Tixati." The latter comment could be dropped when it would become an official standard.

Since v3.1 is incompatible with v1 and v2, and seems to me on a quick read to be incompatible with v3 too, I don't understand why it was built on top of v3/v1, instead of v2. Furthermore, since it's incompatible with the other protocols, and I suggest renaming the current v3 protocol away to another name/number, I think it makes sense to add all the innovations from the current v3.1 on top of v2, and call the result v3.

Ignoring hybrid torrents, this would result in having:
1. Insecure v1 (current v1, hidden by default for security)
2. v1 with security (current v3)
3. v2 (current v2)
4. v3 (a result of taking current v2 and adding current v3.1 innovations (including those also of current v3, e.g. cryptographic agility) on top).

Since neither v3 nor v3.1 are standardized yet, it isn't too late to rename them.

In any case, thank you

Has this project been abandoned??

No, this has not been abandoned. The Dev is just busy right now getting the new version ready for release.

@janet
Is this a new version of the protocol, torrent client, or BEP proposal?

-TLTMAA

A new version of the program. The Dev is still planning on submitting the BEP for v3 and v3.1, but Tixati v3.43 will be released first.

v3 torrent works fine on private trackers by many other bt client. many pt sites prohibit v2 torrent only allow v1 torrent

v3 works because it is built on top of v1, so there is only one info-hash, which is v1-only.

Problem is that nobody in bittorrent, libtorrent, qbittorrent, biglybt, trasnmission. i2psnark, tribler etc.. nobody is willing to implement it.

First of all, NO BEP on GitHub or BitTorrent website. DEveloper is not at all interested in creating a BEP in GitHub there have been many holidays and free time developer has had since the day this issue was created and up until 11 june 2026. He did not do it because he does not want to, as simple as that.

SEcondly, NAMING SCHEME. Libtorrent developer has mentioned that it is not entirely new technology like v2 torrent is, so basically it is v1 and therefore, there is no need to complicate of increase bytesize or some other technical word he used . So, he says instead of adding two three things which differentiates between v1 and v3, why not just use v1 as there have been no known cases of publicly clashing Info-hashes in torrenting world, especially that of public trackers.

I think as users have said and pointed out that since BEP has not been submitted this gives Developer opportunity to rename it to something like v1.5 or something along the lines of this, rather than claiming entirely new version.

In the end, I just want the developer to have some serious thoughts about it. Even if he does not want to change the naming scheme he has to sublit BEP or atleast talk to other torrent client or torrent library developers to mass adopt v3 or it is just an obscure torrent client with not much userbase to make any dent whatsoever in the world of v1 or v2 protocol.