Files
i2p.www/pages/roadmap.html

55 lines
1.6 KiB
HTML

<h2>0.4 (August)</h2>
<ul>
<li>All previous code functional and reliable</li>
<li>New installer and deployment architecture</li>
<li>New web based console and configuration</li>
<li>Implementation docs for I2PTunnel, the SAM bridge, the router, and the SDK</li>
<li>Technical docs for the network describing the use cases, anonymity, and scalability attributes</li>
</ul>
<h2>0.4.1 (August)</h2>
<ul>
<li>Unique tunnelIDs per hop to increase anonymity</li>
<li>Remove the SourceRouteReplyMessage, replace the SourceRouteBlock with a ReplyBlock</li>
<li>Full ElGamal precalculation (instead of just 1/2 of it)</li>
</ul>
<h2>0.4.2 (September)</h2>
<ul>
<li>AMOC transport to allow operation behind firewalls and NATs without administrative control</li>
</ul>
<h2>0.4.3 (October)</h2>
<ul>
<li>UDP transport for scalable high connectivity</li>
</ul>
<h2>1.0 (November)</h2>
<ul>
<li>Javadoc and code walkthrough / guidebook updated</li>
<li>MyI2P available</li>
<li>Internal code audit complete</li>
</ul>
<h2>1.1 (December)</h2>
<ul>
<li>Full streaming protocol implemented with a moving window size</li>
</ul>
<h2>2.0 (March)</h2>
<ul>
<li>Restricted route topology (include some connected peers in routerInfo, recursive route)</li>
<li>Nontrivial certificates (hashcash, other) </li>
</ul>
<h2>3.0 (June)</h2>
<ul>
<li>Sender defined message delays</li>
<li>Creator defined tunnel mixing and pooling of messages, as well as optional chaff messages</li>
<li>(Mixminion integration?) </li>
</ul>
Dates, of course, are just estimates. If you get involved and help out with some of the
coding, things will go faster