Bitcoin client with I2P patch

[giv]

If you get one of these messages:
"... coin database inconsistencies found"
and/or
"Do you want to rebuild the block database now?",
please DO NOT redownload/reindex the blocks (it will just waste your time, especially via i2p).
It is known issue and it's resolved in the 0.8.5 release. So just update your wallet to 0.8.5, if you still didn't do that
More info here:
https://bitcointalk.org/index.php?topic=293307.0
https://bitcointalk.org/index.php?topic=290922.0

[justusranvier]

I've noticed that I frequently check my peer list and find no i2p peers unless I use -onlynet-native_i2p, but I'd like to also use other peer types.

[giv]

I've noticed that I frequently check my peer list and find no i2p peers unless I use -onlynet-native_i2p, but I'd like to also use other peer types.

If you run the patched client in mixed mode, most probably it will use only ip-addresses for outgoing connections. That's why. The bitcoin-client has a pool of known addresses. Selecting of address is a pseudorandom process. At now there are hundreds (at first start) and thousands (after syncing with other clients) known ip-addresses and only several I2P-addresses in the pool. By default only 8 outgoing connections are allowed. So probability of selecting an i2p-address is less than 1%.
If you want to run the program in mixed mode, but want to connect with some i2p-nodes (for tests or other purposes) you have to add an i2p-node manually with "-addnode=<node>" option. Also you may publish your i2p-address or PM me and others can connect to your client. In such case you will see his connections as incoming.

Of course, if your i2p-address changes you should publish the new address again. Obviously, it's inconveniently, so I suggest to use a static i2p-address in this case.
Also if you use the '-tor'/'proxy' options (or appropriate settings in gui) you should use the '-listen' option if you want to accept incoming i2p-connections, because the '-tor'/'proxy' options disable the '-listen' option by default.

[justusranvier]

I'm seeing this problem with listen=1 and maxconnections=256 set in bitcoin.conf

My node will end up with 3-4 peers, none of them I2P, and it will drop the SAM connection so that the I2P node no longer creates the tunnels, which prevents incoming I2P connections.

The only way I can get any native I2P connections at all is to run the node with onlynet=native_i2p

[matthewh3]

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:

Code:

bhqfvosghsfdbi3qubnk3ro6juklz5w7b6l3x6mibkxzzk3mob5a.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.

[K1773R]

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:

Code:

bhqfvosghsfdbi3qubnk3ro6juklz5w7b6l3x6mibkxzzk3mob5a.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.

exe's? are you running it in wine? wtf...

[matthewh3]

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:

Code:

bhqfvosghsfdbi3qubnk3ro6juklz5w7b6l3x6mibkxzzk3mob5a.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.

exe's? are you running it in wine? wtf...

OK patches that run as executables.

[matthewh3]

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.

[matthewh3]

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?

[giv]

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.

[matthewh3]

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.

[giv]

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?

[matthewh3]

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?

[giv]

Update 24 Dec 2013
Migrated to 0.8.6.

[K1773R]

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?

did you enable the SAM bridge in i2p? if not, you have to!

[justusranvier]

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?

[isbe]

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?

That would be terrific..

[matthewh3]

Have Anoncoin copied this patch?

What/Howto I2P

Here are some parameters:

Code:

-i2psessionname=<session name> - name of an I2P session. If it is not specified, value will be "Anoncoin-client"
-samhost=<ip or host name> - address of the SAM bridge host. If it is not specified, value will be "127.0.0.1"
-samport=<port> - port number of the SAM bridge host. If it is not specified, value will be "7656".
-mydestination=<pub+priv i2p-keys> - 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.

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://bitcointalk.org/index.php?topic=309716.msg3324938#msg3324938

If so how difficult would it be to port to other coins?

[meeh]

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.

[Paperweight]

Thank you for this!