Does K Torrent have the capacity to users who repeatedly send bad data? I know azureus does this and the feature has come in handy.

B.T.W., ktorrent is GREAT. It runs MUCH more efficiently than azureus, and isn't as ugly as the default btguidownload.py

3 bad chunks is the limit, but the clients sending the bad data have gotten smarter.

I think this is the way they go about it : (Educated guess, based on the huge amount of connects and disconnects)
- Connect for a short while
- Send one or two bad pieces (pieces are parts of chunks), then disconnect
- The chunk fails because one or two bad pieces and we have no way of knowing which (Only chunks have a SHA1 hash we can check), therefore we do not know who sent the bad data.

Ivan is working on a blocklist plugin, which should help somewhat in these cases.