I2P – Still alive!

Starting up

Founded in late 2003, a bit later than Tor

Planned as Freenet transport, grew into a own project

Settings of insane Limits, e.g. high primes in crypto, still

fine 12 years later

Design decisions

Uni-directional tunnels

Every router is a relay, allow all routers, allow all

traffic

create a own net without IPs, need for new

adopted clients

Hide yourself!

Do not announce the software until it is done

and secure

Use I2P to develop I2P and test the new code

Do some flag days, if needed

Drawbacks

Low latency networks are limited

Jrandom got distracted with High-Latency Tool

Syndie

I2P dev stalled for some years

Crash

Jrandom went AWOL, leaving just signing keys

Server went down, did not come backup

24C3 talk about I2P, short after no online

presence of I2P due to Jrandom AWOL and

server down => CRASH!

Reborn

New team came together, selected montone

and redone all needed service in short time

Do distribute all jobs and credentials to more

than 2 persons => Bus factor!

Make I2P itself independent of any central

instance

Going on

New devs got used to the code, fixing bugs,

implementing new features

Complete new floodfill system

Torrent as bandwidth measurement tool

Growth hurts

Rusleaks.i2p appeared, net grew a few

thousand nodes in short time, showing more

issues in the network

Fixing current issues and determine all other

areas to be fixed for bigger growth

Bad guys

Hiding some hidden services from public

addressbook to not give I2P a bad reputation

Follow news and security researches to be

informed

Malware using I2Pd as tool to connect to control

server, very buggy, very bad

Alternatives

Java is not always the best solution, good

documentation, good responses in forum and

IRC to give out specs information

I2Pd as C/C++ client compatible to Java version

Vuze Plugin, 1/3 of net currently

Prepare for future

Check all included crypto, do check better,

secure alternatives

Creating a plan to replace them while still

support the older ones

Implemented EdDSA curve 25519 in 2015 as

hashes for routers and destinations

Social

Get togethers on events like 32C3

A own I2P Con in Toronto 2015

Be excellent to each other!

Support

THANK YOU!

To all users making our work not obsolete

To all donors to help us making I2P better

To you, listening to me

To everyone showing interest in I2P