This experimental fork targets Windows 11 with the native AirDC++ desktop interface and a bundled, application-owned i2pd router. It is not an upstream AirDC++ release. Do not use upstream installers for this fork.
The PoC package is intended for testing, not sensitive or production use. It is not independently security-audited or an anonymity guarantee.
- Windows 11 x64: installer and portable ZIP
- Debian 13 x86-64: terminal client
- Luadch-I2P: companion hub/server
Checksums and source archives accompany the packages. Windows binaries are unsigned. Do not disable security software or bypass malware warnings.
- Download the Windows x64 setup artifact from the release above, or extract the entire portable ZIP into a writable local folder.
- Install, then open AirDC++-I2P from the Start menu.
- Allow several minutes for I2P startup. Complete the nickname/sharing wizard.
- Use File > Connect to I2P hub (or the first toolbar button) and paste
the portless
adc://...b32.i2paddress supplied by its operator.
No separate I2P installation, SAM/SOCKS setup, port forwarding, external IP or router configuration is required. The client owns its private router; it must not substitute ordinary DC networking when that router is unavailable. The status I2P: Local ready means the local router/session is available, not that tunnels or a remote hub are reachable. Hubs: Connected separately counts completed hub logins. Initial connection can take several minutes.
The optional management Web API is local-only: HTTP and HTTPS listeners accept
only 127.0.0.1 or ::1. Saved wildcard, LAN or hostname binds are rejected;
select a localhost address in Web Server settings to repair an older profile.
This does not change API authentication or hub/peer traffic over I2P.
Uninstall through Windows Settings > Apps. The package removes its
program files and its own router firewall rules, retaining your identity,
settings and data under %LOCALAPPDATA%\AirDC-I2P. Never upload that folder
with an issue report. Close the client before updating or uninstalling.
The Windows portable ZIP has a separate profile: a ZIP containing
portable.mode keeps its data and default downloads in Data beside the
executable. Older poc.1 ZIPs still use AppData. This mode requires a
writable local disk supporting Windows permissions. OneDrive folders are allowed:
cloud sync also copies the private I2P keys. Keep the entire folder available
offline and never run the same synced profile on two computers at once.
No existing AppData profile is automatically imported.
The native wizard uses English only and no longer asks for language, line
speed or RAR/LAN profiles. New profiles receive a neutral generated nickname;
existing saved nicknames are retained.
The portable path/restart/move checks passed in one Windows VM. Visual
acceptance of the shortened wizard and actual OneDrive sync remain pending.
PoC 3 additionally passed targeted GUI-state/input tests and offscreen startup
rendering checks. Existing transport tests were not rerun for that GUI-only delta.
Build and verification details: native GUI, bundled router, package/release gates.
The experimental Debian 13 x86-64 package provides a numbered terminal interface
using the same I2P core, with its own bundled i2pd. It includes hub/private chat,
search, file lists, transfers, queues and shares. No separate I2P setup is needed.
Install the .deb, then run airdc-i2p as a normal user. See the
Linux installation, privacy and build guide.
On Linux, Ready means a hub is connected. Router failure takes the client
offline; restart the application to recover. This is a test candidate, not a
claim of audited anonymity or universal Linux distribution support.
The original project description below is retained for attribution and background. Its downloads, public hubs and Web UI instructions do not describe this I2P-only Windows package.
AirDC++ Web Client is a locally installed application, which is designed for flexible sharing of files or directories within groups of people in a local network or over internet. The daemon application can be installed on different types of systems, such as on file servers and NAS devices.
The application uses Advanced Direct Connect protocol, which allows creating file sharing communities with thousands of users. The application itself is highly optimized even for extreme use cases: a single client can be used to share more than 10 million files or over a petabyte (1000 terabytes) of data.
- Responsive web user interface written in React.js
- Share selected local directories with other users
- Search for files shared by other users
- Save files on disk or view them via the browser
- Chatting capabilities (group and private chat)
- Browse directories shared by other users with a simple file browser interface
- Extension support using Node.js (+others)
- Web API (HTTP REST and WebSockets)
Download information is available on the home page
AirDC++ Web Client wraps the following subprojects:
The issue tracker can be used for feature requests and questions as well. You may also upvote existing feature requests to increase their likelihood for being implemented.
Development/support hub is at adcs://web-dev.airdcpp.net:1511