eMuleBB is a small eD2K/Kad workshop with two public client lanes:
- emulebb-rust is the active
beta. CI-gated
nightly builds from
mainare the current public testing channel. - eMuleBB MFC is the stable Windows
line. Version
0.7.3remains published and the0.7.xbranch continues as a long-term maintenance lane for bugs and bounded, low-risk improvements.
The Rust client is where new product development happens. The MFC client stays available as a useful, maintained result of the original experiment; it is not on a broad feature or architecture roadmap.
Rust development is a best-effort, spare-time project. Contributions are very welcome; start with the contributing guide.
| Repository | Role |
|---|---|
emulebb-rust |
Active beta; nightly public testing and current product-development lane |
emulebb |
Stable 0.7.x Windows client; long-term maintenance |
emulebb-tooling |
Public roadmap, lifecycle policy, product docs, and engineering references |
emulebb-build |
Workspace, build, validation, and packaging orchestration |
emulebb-build-tests |
Shared test and live-network harness |
goed2k-server |
Fixed-purpose eD2K test harness server; no product evolution planned |
ed2k-server |
Reference fork retained for analysis and possible upstream contributions |
amule |
aMule fork retained mainly for source analysis and build comparison |
amutorrent |
Frozen controller fork formerly shipped with the MFC 0.7.3 bundle |
qbittorrentbb |
Paused experiment; public for reference, with no active roadmap |
emulebb-libtorrent |
Paused dependency fork associated with qBittorrentBB |
TrackMuleBB was an exploratory private controller project and is archived.
The two current public entry points are the Rust nightly beta channel and the
stable MFC release. Rust nightlies include published SHA256SUMS and provenance
attestations. The MFC 0.7.3 release also preserves the historical eMuleBB
Suite installer and matching aMuTorrent artifact. “Suite” describes that
shipped bundle; it is not the name of an active cross-client product roadmap.
Native Windows VPN integration and BitTorrent companion work are not current priorities. Deployment-specific container or VPN stacks should be evaluated on their own evidence rather than inferred from these repositories.
- Get the Rust nightly builds
- Contribute to emulebb-rust
- Download eMuleBB MFC 0.7.3
- Read the public documentation
- Review the eMuleBB Roadmap
- Open the organization website
Please report issues in the repository that owns the affected code. Paused and frozen experiments may not accept new issues; their histories remain available for reference.