Downloads of v 2.30.0:


Last Update:

25 Feb 2020

Package Maintainer(s):

Software Author(s):

  • PurpleI2P


i2pd admin network encryption privacy security

I2P Daemon

2.30.0 | Updated: 25 Feb 2020



Downloads of v 2.30.0:



Software Author(s):

  • PurpleI2P

I2P Daemon 2.30.0

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


To install I2P Daemon, run the following command from the command line or from PowerShell:


To upgrade I2P Daemon, run the following command from the command line or from PowerShell:


To uninstall I2P Daemon, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade i2pd -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade i2pd -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure i2pd installed
    name: i2pd
    state: present
    version: 2.30.0
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'i2pd' do
  action    :install
  version  '2.30.0'
  source   'STEP 3 URL'

See docs at

    Name: i2pd,
    Version: 2.30.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller i2pd
   Name     = 'i2pd'
   Ensure   = 'Present'
   Version  = '2.30.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'i2pd':
  provider => 'chocolatey',
  ensure   => '2.30.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install i2pd version="2.30.0" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 25 Feb 2020.



Русская версия

i2pd (I2P Daemon) is a full-featured C++ implementation of I2P client.

I2P (Invisible Internet Protocol) is a universal anonymous network layer.
All communications over I2P are anonymous and end-to-end encrypted, participants
don't reveal their real IP addresses.

I2P client is a software used for building and using anonymous I2P
networks. Such networks are commonly used for anonymous peer-to-peer
applications (filesharing, cryptocurrencies) and anonymous client-server
applications (websites, instant messengers, chat-servers).

I2P allows people from all around the world to communicate and share information
without restrictions.


  • Distributed anonymous networking framework
  • End-to-end encrypted communications
  • Small footprint, simple dependencies, fast performance
  • Rich set of APIs for developers of secure applications



The easiest way to install i2pd is by using
precompiled binaries.
See documentation for how to build
i2pd from source on your OS.

Build instructions:

Supported systems:

  • GNU/Linux x86/x64 - Build Status
  • Windows - Build status
  • Mac OS X - Build Status
  • CentOS / Fedora - Build Status
  • Docker image - Build Status
  • FreeBSD
  • Android
  • iOS

Using i2pd

See documentation and
example config file.


BTC: 3MDoGJW9TLMTCDGrR9bLgWXfm6sjmgy86f
LTC: LKQirrYrDeTuAPnpYq5y7LVKtywfkkHi59
ETH: 0x9e5bac70d20d1079ceaa111127f4fb3bccce379d
DASH: Xw8YUrQpYzP9tZBmbjqxS3M97Q7v3vJKUF
ZEC: t1cTckLuXsr1dwVrK4NDzfhehss4NvMadAJ


This project is licensed under the BSD 3-clause license, which can be found in the file
LICENSE in the root of the project source code.

$ErrorActionPreference = 'Stop'; # stop on all errors
$packagename = 'i2pd'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url = ''
$checksum = 'a941078877b12346ea25acf625fd2998410b1a1c5f5c7ecf798399d0ba3ebc38'
$checksumType = 'sha256'
$url64 = ''
$checksum64 = '0734238e3fa3b51b509ba009a6c518f06e85d2fc77ead82e9fc05277a1e0744d'
$checksumType64 = 'sha256'

Install-ChocolateyZipPackage -packageName "$packagename" `
							 -UnzipLocation "$toolsDir" `
							 -Url "$url" `
							 -checksum "$checksum" `
							 -checksumType "$checksumType" `
							 -Url64 "$url64" `
							 -checksum64 "$checksum64" `
							 -checksumType64 "$checksumType64"

# Install configs and certificates if i2pd dir not available, otherwise just update certificates
$dataDir = Join-Path $Env:APPDATA 'i2pd'
if (Test-Path -Path $dataDir) {
	Write-Host "Updating i2pd certificates"
	Remove-Item $dataDir\certificates -Recurse
	Copy-Item $toolsDir\contrib\certificates -Destination $dataDir\certificates -Recurse
} else {
	Write-Host "Copying default configs and certificates"
	Copy-Item $toolsDir\contrib -Destination $dataDir -Recurse

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
I2P Daemon 2.29.0 256 Tuesday, October 22, 2019 Approved
I2P Daemon 2.28.0 146 Wednesday, August 28, 2019 Approved
I2P Daemon 2.27.0 109 Friday, July 5, 2019 Approved
I2P Daemon 2.25.0 137 Friday, May 10, 2019 Approved
I2P Daemon 2.24.0 287 Friday, March 22, 2019 Approved
I2P Daemon 2.23.0 574 Tuesday, January 22, 2019 Approved
I2P Daemon 2.22.0 558 Friday, November 9, 2018 Approved
I2P Daemon 2.21.1 219 Monday, October 22, 2018 Approved
I2P Daemon 2.21.0 204 Friday, October 5, 2018 Approved

  1. Single threaded SAM
  2. Experimental support of ECIES-X25519-AEAD-Ratchet crypto type
  3. Works on Android 10
  4. Reported minimal MTU size is 1280 for ipv6
  5. Updated reseeds list
  6. Correct response to RouterInfo in I2PControl

This package has no dependencies.

Discussion for the I2P Daemon Package

Ground Rules:

  • This discussion is only about I2P Daemon and the I2P Daemon package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or I2P Daemon, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus