NOTE: 0.9 was released on May 2, 2012, 22 months after the 0.8 release in early July 2010. The 0.9 release contains, roughly, what is marked as DONE below. Plus a ton of things that were never on the roadmap.

Next is to copy and update this roadmap for the next major release, scheduled perhaps for mid-to-late 2013. That milestone is currently not numbered, it could be 1.0, or 0.10, or 0.91, or something else.

  • Next roadmap here: Roadmaps/1.0 (ignore naming, "1.0" not decided on yet)

The following header is from Summer 2010:


The real roadmap is here http://www.i2p2.i2p/roadmap.html but it is pretty vague about 0.9, and pretty modest, since we just released 0.8 in early July. We haven't put serious thought into 0.9 yet. We need some ambitious goals.

I guess the target for 0.9 would be mid-to-late 2011?

If you have any ideas for 0.9, add them here. If you are interested in getting paid to work on I2P (for example via Google Summer of Code 2011 or funding…. not that we've ever gotten any funding, but it could happen) be sure to add your ideas here. Also look at the GSoC page here on the wiki.



  • DONE - Iterative floodfill lookups
  • Encrypted netdb responses
  • DONE - HTTPS reseeding


  • Reachability Mapping / handle peers partially reachable / enhanced restricted routes
  • DONE - SSU disconnect message
  • LOTS DONE, ONGOING - Better profile and netdb expiration / memory usage
  • Circumvention for various types of state firewalls
  • WON'T DO FOR 0.9 - Multicast?
  • Restricted routes - start work on this - see http://zzz.i2p/topics/114
  • WON'T DO FOR 0.9 - Lower default connection limits
  • More IPV6
  • DONE - SSU analysis and improvements
  • WON'T DO FOR 0.9 - TLS Transport?
  • Transport timeouts / fallback analysis and improvements
  • WON'T DO FOR 0.9 - Bridges like Tor has them?
  • WON'T DO FOR 0.9 - I2P-over-HTTP (to pass through HTTP proxies)


  • DONE - Congestion and WRED analysis and improvements
  • DONE - Continue CPU and memory optimization
  • REVIEW ONGOING - Crypto review, possible DSA 1024/160 replacement, see http://zzz.i2p/topics/715
  • Peer profiling formulas - analysis and improvements
  • DONE - Restrict file permissions
  • WON'T DO FOR 0.9 - Use Java 1.6 features
  • DONE - Update CPUID, JBigi
  • Bigger I2NP Messages?
  • DONE EXCEPT FOR EXPL. - 3 hop default for everything?
  • Streaming improvements
  • ONGOING - working on getting i2p slim and fast
  • proof of security and reliability
  • Sleep mode (so it donates more bandwidth while at I'm at work)


  • Improve help pages and website
  • ONGOING - More translations
  • DONE - AJAX (jquery?) console
  • LINKS TO WEBSITE - Full proxy setup help pages in console for various proxy-switcher and browser combinations
  • DONE - Simplified console
  • LINKED TO i2plugins.i2p - Links on the router console to all known plugin repositories
  • IN DEVELOPMENT - task-centric router interface as an option with all the current technical stuff either hidden & available on the current one or pushed into an "advanced" section
  • IN DEVELOPMENT - Make it easier and clearer for newbies to see what one can DO with I2P - i.e., Applications. Need to integrate I2PBote, Tahoe-LAFS, I2PMessenger, Syndie, etc. or make it easy to find out about these applications and how to install them if they cannot be integrated into the I2P distribution. Add I2P website links to suggested Firefox Add-ons also.


  • (Minor) Show a hint/warning when installing i2p if java version is out of date, like Freenet does
  • Include some seed data in the distribution so a central reseed location isn't required?
  • Much easier setup - bundled browser? Or a plugin?
  • DONE - Android router working
  • MEEGO IS DEAD - Meego router working
  • MEEGO IS DEAD - Meego UI
  • DONE - Official .deb packages and repo
  • Official USB key package
  • Other mobile platforms?
  • Revisit split directory issues - go non-split for windows?
  • DONE - Update installer and i2prouter script, deal with non-x86 better
  • splitting the distribution into router- and core-part and application package
  • Make a Browser like for tor as well for i2p, so that i2p is always running if the browser is used, I suggest to use for that idea, as here a i2p proxy is already in fir .i2p sites, while normal sites in another tab can be loaded as well.


  • 3 hop default for everything?
  • Anonymous Digital Cash to pay for I2p resources anonymously, using a digital cash library such as this one:
  • DONE - Backup release signers
  • Better handling of multiple outproxies (stay with one while it is working)
  • Chat plugin
  • DONE - Compact tracker responses
  • ONGOING - Lots more plugins
  • Outproxy plugin? !!!! Yes Please +1
  • ONGOING - Susimail improvements
  • Syndie - restart work on it?
  • Tahoe-LAFS plugin
  • Streaming audio improvements and plugin
  • VOIP / voice chat plugin
  • Support HTTP/1.1 in the eeproxy for reduced page load times
  • Improve I2PSnark usability with things like: group torrents by status (stopped, completed, seeding, downloading…), adding torrents with just a click in browser instead of cut 'n' paste to the UI, show number of distributed copies?
  • Distributed cache. Should be able to publish a file to the cache like on Freenet and retrieve it with no other knowledge than its SHA256 (or similar) checksum. If a web server provides the checksum in its GET/HEAD header, eeproxy should first try to get it from the cache and use the webserver as a fallback (and then place it in the cache after retrieval and verification).


Last modified 8 years ago Last modified on Jun 14, 2012 1:03:23 PM