For this to really happen the network protocol needs to allow for 256 bit peer addresses.
Is this an issue? 
Topic: Bitcoin client with I2P patch (Read 21499 times)
For this to really happen the network protocol needs to allow for 256 bit peer addresses.
I believe Anoncoin forked the patch and are now working on a C++ I2p router with the Monero team - https://geti2p.net/en/blog/post/2014/08/15/The-privacy-solutions-project
Hi, I wonder why you dont submit this patch to bitcoin core? Did you try that or recommended I2P integration?
He didn't try...Quote from: laanwj
There is a bitcoin fork that works on I2P, I am not sure what the status of it is, and he has never tried to get the changes upstream:
https://bitcointalksearch.org/topic/bitcoin-client-with-i2p-patch-151181
https://github.com/bitcoin/bitcoin/issues/2091#issuecomment-42650077 https://bitcointalksearch.org/topic/bitcoin-client-with-i2p-patch-151181
Hi, I wonder why you dont submit this patch to bitcoin core? Did you try that or recommended I2P integration?
Thank you for this!
Have Anoncoin copied this patch?
Yes our implementation originates from this patch. You can also see giv's copyright in the i2psam library at the source code for example.
Have Anoncoin copied this patch?
https://bitcointalksearch.org/topic/m.3324938
If so how difficult would it be to port to other coins?
What/Howto I2P
Here are some parameters:
Your client will act as a gateway between I2P and clearnet if you don't add -onlynet=i2p
If you have used your Anoncoin client on clearnet before, you might need to delete peers.dat if you don't get any connections.
To use the wallet on I2P do the following:
1. Download and install I2P ( www.geti2p.net ), then start it. (It will run as a daemon, so don't expect any window)
2. Wait a minute or two, then navigate to http://127.0.0.1:7657/configclients
3. Make sure to start the "SAM application bridge" (Tip: After starting it, check it for autostart and save configuration)
4. In run (enter the start menu and type run on windows Vista/7) type %appdata%
5. Open or create the Anoncoin folder
6. Create/edit the anoncoin.conf file
7. make sure to set the following options: rpcuser, rpcpassword and onlynet=i2p
8. (Optional) you can set i2p=1 instead of onlynet=i2p
Example:
rpcuser=someone
rpcpassword=super_secret_password
onlynet=i2p
Note: The I2P router uses a little time to integrate into the I2P network, so you might not get a connection before I2P have runned for about 5-10minutes.
Here are some parameters:
Code:
-i2psessionname= - name of an I2P session. If it is not specified, value will be "Anoncoin-client"
-samhost= - address of the SAM bridge host. If it is not specified, value will be "127.0.0.1"
-samport= - port number of the SAM bridge host. If it is not specified, value will be "7656".
-mydestination= - your full destination (public+private keys). If it is not specified, the client will geneterate a random destination for you. See below (Starting wallet with a permanent i2p-address) more details about this option.
-generatei2pdestination - if this option is specified, your client will start for generation i2p-destination only and will close after that.
-samhost=
-samport=
-mydestination=
-generatei2pdestination - if this option is specified, your client will start for generation i2p-destination only and will close after that.
Your client will act as a gateway between I2P and clearnet if you don't add -onlynet=i2p
If you have used your Anoncoin client on clearnet before, you might need to delete peers.dat if you don't get any connections.
To use the wallet on I2P do the following:
1. Download and install I2P ( www.geti2p.net ), then start it. (It will run as a daemon, so don't expect any window)
2. Wait a minute or two, then navigate to http://127.0.0.1:7657/configclients
3. Make sure to start the "SAM application bridge" (Tip: After starting it, check it for autostart and save configuration)
4. In run (enter the start menu and type run on windows Vista/7) type %appdata%
5. Open or create the Anoncoin folder
6. Create/edit the anoncoin.conf file
7. make sure to set the following options: rpcuser, rpcpassword and onlynet=i2p
8. (Optional) you can set i2p=1 instead of onlynet=i2p
Example:
rpcuser=someone
rpcpassword=super_secret_password
onlynet=i2p
Note: The I2P router uses a little time to integrate into the I2P network, so you might not get a connection before I2P have runned for about 5-10minutes.
https://bitcointalksearch.org/topic/m.3324938
If so how difficult would it be to port to other coins?
Is there any plan to move this patch into the main repository any time soon?
Maybe start incrementally by moving the peers.dat format changes first?
Maybe start incrementally by moving the peers.dat format changes first?
That would be terrific..
Is there any plan to move this patch into the main repository any time soon?
Maybe start incrementally by moving the peers.dat format changes first?
Maybe start incrementally by moving the peers.dat format changes first?
You do not need to run patched bitcoind before bitcoin-qt. Bitcoin-qt should work immediately, if it doesn't then probably there is a bug. Under which OS do you have this problem?
Xubuntu, it does work maybe I didn't follow the OP's instructions correctly?
Update 24 Dec 2013
Migrated to 0.8.6.
Migrated to 0.8.6.
You do not need to run patched bitcoind before bitcoin-qt. Bitcoin-qt should work immediately, if it doesn't then probably there is a bug. Under which OS do you have this problem?
Xubuntu, it does work maybe I didn't follow the OP's instructions correctly?
You do not need to run patched bitcoind before bitcoin-qt. Bitcoin-qt should work immediately, if it doesn't then probably there is a bug. Under which OS do you have this problem?
I don't if it that I needed to restart the patched wallet a few times after a fresh install. Or if I had to start the bitcoind patch first before starting the bitcoin-qt patch and getting it to connect to I2p peers only for the first time. Or did I miss that in the OP instructions?
Sorry I don't quite understand. Please reword you message.When you have just installed/run i2p, it may discard new connections while it's integrating in the network. If you have troubles, please describe step-by-step how can I reproduce it.
Sorry - I don't know if it that I needed to restart the patched wallet a few times after a fresh install. Or if I had to start the bitcoind patch first before starting the bitcoin-qt patch and getting it to connect to I2p peers only for the first time. Or did I miss that in the OP instructions? - it is working now but I don't know if that it just needed restarting a few times or if I needed to to run the bitcoind patch first before starting the bitcoin-qt patch and getting it to to connect to only I2p peers for the first time.
I don't if it that I needed to restart the patched wallet a few times after a fresh install. Or if I had to start the bitcoind patch first before starting the bitcoin-qt patch and getting it to connect to I2p peers only for the first time. Or did I miss that in the OP instructions?
Sorry I don't quite understand. Please reword you message.When you have just installed/run i2p, it may discard new connections while it's integrating in the network. If you have troubles, please describe step-by-step how can I reproduce it.
I don't if it that I needed to restart the patched wallet a few times after a fresh install. Or if I had to start the bitcoind patch first before starting the bitcoin-qt patch and getting it to connect to I2p peers only for the first time. Or did I miss that in the OP instructions?
I think you need to work on making the wallet easier to install for newbies to attract more users. Like a single Windows .exe or .deb for the whole wallet maybe with I2p combined too.
This update does not influence to connections. But last few days I has only 1-2 connections. I don't know what happened with other nodes, but my nodes are working fine.
Try to rerun you client. If it doesn't help, try to manually add nodes by the 'addnode' command with the following addresses:
Try to rerun you client. If it doesn't help, try to manually add nodes by the 'addnode' command with the following addresses:
Code:
bhqfvosghsfdbi3qubnk3ro6juklz5w7b6l3x6mibkxzzk3mob5a.b32.i2p
z5pg37axylu7wuncppbzvwxawb5mo3euxuwbyi2s2um7bhnl3caa.b32.i2p
ofa7kfuqewnxyqiadnsj6ibcwtj6ndcabwcfabljmuyol2pussaa.b32.i2p
mzvsw6bwae6ul33b5zege5xie2cevno6vgik6nrb6lw74cn3wmdq.b32.i2p
z5pg37axylu7wuncppbzvwxawb5mo3euxuwbyi2s2um7bhnl3caa.b32.i2p
ofa7kfuqewnxyqiadnsj6ibcwtj6ndcabwcfabljmuyol2pussaa.b32.i2p
mzvsw6bwae6ul33b5zege5xie2cevno6vgik6nrb6lw74cn3wmdq.b32.i2p
After the update manger on Xubuntu downloaded the official updates then I ran your exe's it works OK. Just got three I2p peers within five minutes.
Edit: Soon up to four peers.
OK patches that run as executables.
This update does not influence to connections. But last few days I has only 1-2 connections. I don't know what happened with other nodes, but my nodes are working fine.
Try to rerun you client. If it doesn't help, try to manually add nodes by the 'addnode' command with the following addresses:
Try to rerun you client. If it doesn't help, try to manually add nodes by the 'addnode' command with the following addresses:
Code:
bhqfvosghsfdbi3qubnk3ro6juklz5w7b6l3x6mibkxzzk3mob5a.b32.i2p
z5pg37axylu7wuncppbzvwxawb5mo3euxuwbyi2s2um7bhnl3caa.b32.i2p
ofa7kfuqewnxyqiadnsj6ibcwtj6ndcabwcfabljmuyol2pussaa.b32.i2p
mzvsw6bwae6ul33b5zege5xie2cevno6vgik6nrb6lw74cn3wmdq.b32.i2p
z5pg37axylu7wuncppbzvwxawb5mo3euxuwbyi2s2um7bhnl3caa.b32.i2p
ofa7kfuqewnxyqiadnsj6ibcwtj6ndcabwcfabljmuyol2pussaa.b32.i2p
mzvsw6bwae6ul33b5zege5xie2cevno6vgik6nrb6lw74cn3wmdq.b32.i2p
After the update manger on Xubuntu downloaded the official updates then I ran your exe's it works OK. Just got three I2p peers within five minutes.
Edit: Soon up to four peers.
Jump to: