The eMuleBB home for broadband P2P
RC2 is published: a serious Windows eMule line for fast upload links, large shared libraries, always-on sessions, REST controller workflows, Arr integration, and GitHub-built package evidence.
Download
Use the full-suite bootstrapper for eMuleBB plus controller integration, or use the standalone ZIP when you only want the desktop app.
irm https://emulebb.github.io/install.ps1 | iexStandalone app: download the RC2 ZIP, extract it, and run emulebb.exe.
This is the home of eMuleBB: eMule broadband edition, an independent product for people who still value eMule's distributed sharing model and want it operated like modern software. RC2 packages are published on GitHub Releases with a full-suite bootstrapper, standalone ZIPs, manifests, hashes, SBOMs, and matching aMuTorrent controller assets.
Why
eMuleBB is a product effort and an engineering practice: preserve a complex native Windows client with real network behavior, then surround it with modern builds, tests, documentation, automation, and release proof.
The goal is not a cosmetic mod, a protocol fork, or a generic downloader shell. It is a broadband-focused eMule line for long sessions, rare files, deliberate seeding, and power users who still want the native desktop workflow.
Upload slots, timeouts, buffers, large libraries, WebServer exposure, REST control, and package evidence are made explicit so each change can be reviewed, tested, documented, and adjusted.
The same workspace discipline covers the app, controller tooling, Windows builds, deterministic eD2K services, and exploratory headless eD2K/Kad work without pretending every lab project is a stable end-user product.
Features
The RC2 work is focused on operator-visible behavior: predictable upload policy, safer binding, fixed performance limits, large-library operation, local automation, and package evidence.
Bounded slot targets, weak-slot recycling, ratio readouts, and seeding controls keep fast upload links useful without changing the eD2K upload protocol.
Interface-aware binding, UPnP/NAT mapping validation, HTTPS, allowed-IP rules, and separate WebServer bind settings keep remote surfaces explicit and testable. Binding is not a VPN kill switch.
Higher socket buffers, queue/source limits, file buffering, timeout defaults, recursive share sync, startup cache work, and long-path guidance target current Windows systems and large libraries.
Server, global, and Kad search remain the native foundation, with Kad identity tracking, bad-node handling, cleanup, and timing work kept inside compatibility boundaries.
Authenticated JSON endpoints cover transfers, searches, shared files, servers, Kad, logs, categories, uploads, statistics, preferences, and controlled shutdown from trusted local tools.
0.7.3-rc.2 is published with GitHub Actions packaging, manifests, SHA-256 evidence, SPDX SBOMs, diagnostics assets, and bootstrapper hash evidence.
Documentation
Start with setup, then use the product and integration guides for the operating model, controller workflows, and release evidence.
Run eMuleBB as eMule first: trusted servers, deliberate Kad bootstrap, predictable incoming/temp paths, and visible shared folders.
Enable REST only for trusted controllers, then use aMuTorrent, Prowlarr, Radarr, and Sonarr through the documented adapter paths.
Setup, API, release, SBOM, and package details live in the rendered docs so public claims stay tied to source-controlled evidence.
The broadband release track exposes a resource-oriented /api/v1 JSON API from the existing WebServer listener. It authenticates with X-API-Key, serves JSON envelopes, and keeps native eMule state changes marshaled through the app.
Project lore
01
Keeps broadband upload slots from kicking the stable door down, then nudges the slow ones back into line with a very official clipboard.
02
Carries bootstrap nodes, routing tables, and stubborn eD2K/Kad folklore across rough network terrain without dropping the protocol map.
03
Hauls packages, hashes, SBOMs, logs, live checks, and just enough attitude through the gate before anything gets called ready.
Security and provenance
emulebb-v0.7.3-rc.2 is a GitHub prerelease with x64 and ARM64 ZIPs, diagnostics packages, manifests, SBOMs, and the suite bootstrapper.
The bootstrapper downloads release assets and verifies package hashes from the published manifests before installing.
The matching aMuTorrent RC2 package is published separately, and the full x64 bootstrap flow resolves it automatically for controller setup.
Release packages carry package-local SBOM.spdx.json plus sidecar *.sbom.spdx.json files, with manifest hashes that tie software contents to the exact package evidence.
RC2 assets are published from GitHub release automation with manifests, SHA-256 evidence, SBOMs, and a bootstrapper hash asset for verification.
aMuTorrent, Prowlarr, Radarr, Sonarr, Torznab, and qBittorrent-compatible lanes are documented as local integration paths around the native /api/v1 contract.
eMuleBB ecosystem