Why Peer Exchange Is Disabled on Private Torrents
Peer Exchange (PEX) is automatically disabled on torrents with the
private attribute to prevent unauthorized peer sharing, ensure accurate
upload and download tracking, and protect the security of closed
BitTorrent communities. When a .torrent file contains the
private flag (private=1), compliant BitTorrent clients
instantly suppress all decentralized peer discovery mechanisms—including
PEX, Distributed Hash Tables (DHT), and Local Peer Discovery
(LSD)—forcing all peer communication exclusively through the designated
private tracker.
Enforcing Strict Ratio Tracking
Private trackers rely on strict ratio requirements to ensure that members contribute bandwidth back to the community rather than just downloading. The central tracker counts every megabyte uploaded and downloaded by assigning unique passkeys to registered users. If PEX were enabled, clients would share their peer lists directly with one another and transfer data outside the tracker’s knowledge. This out-of-band data transfer creates untracked bandwidth usage, making it impossible for the tracker to accurately record user ratios.
Maintaining Access Control and Security
Private torrent trackers operate as invite-only or membership-gated communities. When PEX is active, a connected client can pass the IP addresses of peers in the swarm to other users who may not have permission to access the tracker. Disabling PEX ensures that only authenticated users who obtained the torrent directly from the private site can join the swarm, preventing unauthorized outsiders from discovering or participating in the file transfer.
Standardized Client Compliance
The behavior of the private flag is codified in official BitTorrent specifications (BEP 27). Modern BitTorrent clients—such as qBittorrent, Transmission, and Deluge—read the metadata of a torrent file upon loading. If the client detects the private flag, it hard-disables PEX, DHT, and LSD for that specific transfer. This design guarantees that decentralized discovery methods cannot leak private swarm details onto the public BitTorrent network.