Jump to content

Private tracker

From Pulsed Media Wiki


A private tracker is a BitTorrent tracker that requires registration or an invitation to use. Each user gets a unique passkey embedded in their torrent files. The tracker logs upload and download amounts per user and enforces ratio rules.

Private trackers exist because public trackers have a free-rider problem: most users download and leave without seeding. Private trackers solve this by making seeding mandatory.

How they work

The mechanics are the same as any BitTorrent swarm. A .torrent file contains an announce URL pointing to the tracker. The tracker coordinates peers. The difference is in access control and accountability.

Passkeys

Every .torrent file downloaded from a private tracker contains a passkey unique to the user who downloaded it. This passkey is part of the announce URL:

<syntaxhighlight lang="text"> https://tracker.example.com/UNIQUE_PASSKEY/announce </syntaxhighlight>

The tracker uses this passkey to attribute all upload and download traffic to the correct account. Sharing a .torrent file with someone else leaks your passkey and can get your account banned.

Private flag

Torrents on private trackers set the private flag in their metadata. This flag tells the BitTorrent client to disable DHT (Distributed Hash Table) and PEX (Peer Exchange), which are peer discovery methods that bypass the tracker. With the private flag set, all peers must go through the tracker, giving it full visibility of who is in the swarm.

Client whitelisting

Many private trackers maintain a list of allowed BitTorrent clients. Clients that report inaccurate statistics or behave unpredictably get blocked. Commonly whitelisted clients include rTorrent/libtorrent, Deluge, qBittorrent, and Transmission. Modified clients that fake upload stats are banned on sight.

Ratio enforcement

The ratio is calculated as:

<syntaxhighlight lang="text"> Ratio = Total Uploaded / Total Downloaded </syntaxhighlight>

Most private trackers require a minimum ratio between 0.5 and 1.0. Users below the minimum face download restrictions or account suspension.

This creates a basic economic problem: every byte downloaded by one user must be uploaded by another. On popular torrents with many seeders, each seeder gets a smaller share of the upload. On old or niche torrents with few leechers, there is nobody to upload to.

Freeleech

Trackers occasionally mark certain torrents as freeleech. Downloads on freeleech torrents do not count against the user's ratio, but uploads still count. Freeleech periods are common during holidays or when new content is added to encourage distribution.

Bonus points

Many trackers award bonus points for seeding. Points accumulate based on the number of torrents seeded and the time spent seeding. Users can exchange bonus points for upload credit, which improves their ratio without requiring actual upload traffic.

This rewards long-term seeding of old torrents that have few leechers, a behavior the ratio system alone does not incentivize.

Hit-and-run rules

Some trackers require users to seed every torrent they download for a minimum period, typically 24 to 72 hours. Stopping a torrent before the minimum seed time is called a "hit and run" and results in warnings or bans.

Invite system

Most private trackers do not allow open registration. New users must be invited by an existing member. The inviter takes partial responsibility for the invitee: if the new user cheats or violates rules, the inviter can also face consequences.

Some trackers open registration periodically, allowing anyone to join for a limited time. Others hold interviews on IRC or Discord where applicants demonstrate knowledge of BitTorrent and the tracker's rules.

The invite system keeps the community small enough for moderation to work and creates social pressure against bad behavior.

Content and moderation

Private trackers enforce strict content standards. Uploads must follow naming conventions, include specific metadata, and meet quality thresholds set by the tracker. Moderators verify uploads and remove duplicates or anything that does not meet the rules.

Different trackers focus on different content categories:

  • General (movies, TV, software)
  • Music (often requiring lossless formats like FLAC)
  • Anime and manga
  • E-books and academic papers
  • Games

The specificity of these communities is part of the appeal. A music tracker that requires FLAC and proper tagging builds an archive that general trackers do not match.

Seedboxes and private trackers

The ratio problem makes seedboxes a practical tool for private tracker users. A seedbox runs 24/7 in a datacenter with high-bandwidth connectivity (1 Gbps or 10 Gbps), which means:

  • Torrents start seeding immediately after download. Early-swarm upload traffic is where most ratio is built, since demand is highest right after release.
  • The seedbox seeds around the clock without the user's home computer running.
  • Datacenter upload bandwidth (1 Gbps or 10 Gbps) is faster than most residential connections.
  • Hundreds of torrents can seed at once without affecting the user's home connection.

Pulsed Media seedboxes come with rTorrent, Deluge, or qBittorrent pre-installed. All three are whitelisted on virtually all private trackers. Files are accessible via SFTP for download to the user's local machine (see Seedbox access via FTP, SSH and SFTP).

For users on trackers with strict ratio requirements, a seedbox turns ratio maintenance from a constant concern into something that runs in the background.

Public vs. private trackers

Public tracker Private tracker
Access Open to anyone Registration or invite required
Ratio tracking None Per-user upload/download tracking
Peer discovery DHT, PEX, tracker Tracker only (private flag)
Content quality Varies Moderated and curated
Client restrictions None Whitelisted clients only
User accountability Anonymous Passkey-linked identity

Neither is inherently better. Public trackers are accessible and work with magnet links. Private trackers trade accessibility for reliability and content quality.

See also

On the blog: