Tahoe-lafs 0.12.1 is tahoe-lafs with native i2p support.
 use this introducer: pb://exupps5kk3amc5iq4q6f5ahggkm4s5fl@i2p:oj7cffq5fnk46iw3i3h2sdgncxrqbxm7wh6i4h2cbpmqsydygkcq.b32.i2p/introducer
 Note that the older Tahoe-LAFS introducer config still works (the introducer= line in tahoe.cfg), but the I2P-specific introducers file does *not* work with upstream Tahoe.
 The I2P support in 1.12 uses an i2p: prefix in front of I2P addresses, instead of pushing the location hints into the I2P HTTP proxy
 currently old storage nodes can't be upgraded because there's an SSL issue between txi2p and foolscap that we are working on fixing

<K1773R> which option for length?
<str4d> If you can edit your tahoe installation, edit allmydata/util/i2p_provider.py and add "options = 'inbound.quantity:5,outbound.quantity:5'" to the self._i2p.sam_endpoint call (line 157)
<str4d> K1773R, inbound.length and outbound.length - see https://geti2p.net/en/docs/protocol/i2cp for the full list

str4d> valdikss, append ":options=inbound.quantity\:5,outbound.quantity\:5" to tub.port
y> {-str4d} valdikss, you'll need to set it in both the tub.port and inside i2p_provider.py (because of a quirk in the way Tahoe handles config for listeners