As you may know, some private trackers (or at least one I'm a member of), ban Tixati on the grounds that it can be used for ratio cheating. Now, I've heard that this was once true, but has been fixed and is no longer the case. I want to try to make the case for Tixati over at my tracker, so can someone give me arguments and tell me what the state of this is. What was the problem and has it been fixed, how can I prove it's been fixed etc?

The client doesn't cheat. The person does. Client-based sniffing is a technical issue.

Also, ratio enforcement in the 2025? When the expected number of newcomers is 5 per year? That's just donation extortion, or braindead circlejerk mentality of people permanently stuck in 2006.

Let me guess, torrentleech.org?

all opensouece clients can be modified to cheat，including，qbittorrent、transmission、deluge、rtorrent、gopeed and bigly bt. Very old version tixati and bitcomet upload statisic didn't match the private tracker, so they are all banned after that at some PT site，although they are non opensource client just like utorrent/bittorrent.unit 3d accept tixati as default.

don't know about old version upload statistic not matching the tracker. what is sure is that tixati repport the overheat to the tracker, contrary to most client. and this is, i found annoying because seeding back is not alway easy and getting an extra cost of data which can be up to 30% of the actual size of the torrent is rather annoying when you to maintain a ratio. and there is one thing i don't is how data i really send/download since my connection has no data cap. since dev seems to really enjoy that particularity, the ability to choose how the stats are reported back (with or without the evoerheat) is more than welcome. thats the reason i don't use tixati on private trackers (when it is allowed of course) but it remain my choice on public tracker

So has this been fixed? Could people cheat deliberately or was there just some random mismatch between what tixati was reporting and what the tracker was counting?

The issues with Tixati and BitComet on private trackers (PTs) have mostly been fixed technically, but the "ban" status remains on many sites due to historical baggage and specific software features that tracker staff still find problematic.

Here is the breakdown of why those mismatches occurred and whether they were deliberate "cheats."

Tixati: The "Misreporting" Controversy

The mismatch between Tixati and private trackers was largely due to how Tixati handled metadata and overhead, rather than a deliberate attempt to cheat.

   The Mismatch: Historically, Tixati was accused of reporting slightly higher upload numbers than other clients. This wasn't because it was "lying" to the tracker, but because it often included protocol overhead (the data used to manage the connection) in its totals, whereas trackers only want to see the actual "payload" (the file data).

   The "Cheat" Accusation: Many PT sites banned Tixati because it included a built-in feature to spoof the Peer ID. This allows a user to make Tixati look like uTorrent or qBittorrent to the tracker. Tracker staff view this as "cheating-ready" behavior, even if the user isn't actually faking their upload amounts.

   Is it fixed? Yes. Modern versions of Tixati have refined their reporting to match standard expectations. However, many PTs still ban it because it is closed-source and the "spoofing" features make it harder for staff to verify that the client is behaving.

Why they stay banned

Private trackers prioritize predictability. If a client is open-source (like qBittorrent or Deluge), the staff can audit the code to see exactly how it reports data. Because Tixati and BitComet are closed-source and have a history of "doing things their own way," staff often find it easier to keep the ban in place than to risk someone using them to ghost-leech or inflate their ratio.