Bitcoin client for I2p network - 114BTC bounty

[matthewh3]

Is anyone interested in this bounty

Bitcoin client for I2p network - 114BTC bounty

For a future of I2P and attract more people into I2P this bounty is to create a I2P native Bitcoin client. It should integrate with other client via the I2P network and via gateways to the existant bitcoin network.

Note: To claim the bounty the author must not be paid by other organizations or teams for this work (e.g. GSoC students are not valid).

http://www.i2p2.de/bounty_btcclient

Cash, bitcoin and litecoin tip-jar for this project - https://propster.me/tipjar/0cf2h05

[jim618]

I see you have a SOCKS5 proxy to the I2p network.

Could you not use an existing Bitcoin client via that in a similar way to people use a SOCKS5 proxy to access Tor ?

I am not familiar with the I2p network - are you wanting the discovery of nodes to be 'in network' rather than by DNS as it is now ?

[matthewh3]

I see you have a SOCKS5 proxy to the I2p network.

Could you not use an existing Bitcoin client via that in a similar way to people use a SOCKS5 proxy to access Tor ?

I am not familiar with the I2p network - are you wanting the discovery of nodes to be 'in network' rather than by DNS as it is now ?

I'm not involved with the I2p project other than being a fan and have just been watching this large unclaimed bounty for a while now.  Yeah I think your second option is more what there after.

[Pieter Wuille]

The problem with I2P is that its routable addresses are 256 bits, AFAIK, which can't be nicely embedded in an IPv6 range (like was possible with the 80-bit onion addresses). As the Bitcoin peer exchange system only supports IPv6, this makes native support of something like I2P impossible. You could have a proxy, and manually connect to it of course, though...

[justusranvier]

The problem with I2P is that its routable addresses are 256 bits, AFAIK, which can't be nicely embedded in an IPv6 range (like was possible with the 80-bit onion addresses). As the Bitcoin peer exchange system only supports IPv6, this makes native support of something like I2P impossible. You could have a proxy, and manually connect to it of course, though...

https://bitcointalk.org/index.php?topic=151181.msg1783592#msg1783592