-
Notifications
You must be signed in to change notification settings - Fork 52
feat(tracker-client): change default peer ID prefix from qB to RC #1761
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
josecelano
merged 2 commits into
torrust:develop
from
josecelano:1564-change-default-peer-id
May 12, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
46 changes: 46 additions & 0 deletions
46
docs/adrs/20260512102000_define_tracker_client_peer_id_convention.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,46 @@ | ||
| # Define Tracker-Client Peer ID Convention | ||
|
|
||
| ## Description | ||
|
|
||
| Tracker-client defaults currently use a qBittorrent peer ID prefix (`-qB`), which | ||
| misrepresents Torrust tracker-client traffic. | ||
|
|
||
| Issue [#1564](https://github.com/torrust/torrust-tracker/issues/1564) requires | ||
| adopting a Torrust-specific convention while keeping protocol fixtures explicit | ||
| and package boundaries decoupled. | ||
|
|
||
| ## Agreement | ||
|
|
||
| We adopt the following tracker-client peer ID convention: | ||
|
|
||
| - Prefix: `RC` (Rust Client) | ||
| - Version field: `3000` for the current `v3.0.0` line | ||
| - Full layout: `-<CC><VVVV>-<12-digit-suffix>` (Azureus-style) | ||
|
|
||
| Defaults are split by context: | ||
|
|
||
| - Production defaults use `-RC3000-` plus a randomized 12-digit suffix. | ||
| - The production default is generated once per process and reused. | ||
| - Tests and fixtures use deterministic values such as | ||
| `-RC3000-000000000001`. | ||
|
|
||
| Version source policy: | ||
|
|
||
| - Version bytes are hard-coded per release for now. | ||
| - The value is updated explicitly when the client versioning policy changes. | ||
|
|
||
| Package coupling policy: | ||
|
|
||
| - Protocol and server package fixtures do not import tracker-client constants. | ||
| - They may define local deterministic constants that follow the same convention. | ||
|
|
||
| ## Date | ||
|
|
||
| 2026-05-12 | ||
|
|
||
| ## References | ||
|
|
||
| - <https://github.com/torrust/torrust-tracker/issues/1564> | ||
| - <https://www.bittorrent.org/beps/bep_0020.html> | ||
| - <https://wiki.theory.org/BitTorrentSpecification#peer_id> | ||
| - [Issue Spec](../issues/open/1564-tracker-client-change-default-peer-id.md) | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,2 +1,3 @@ | ||
| pub mod http; | ||
| pub mod peer_id; | ||
| pub mod udp; |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.