Bitcoin client with I2P patch - page 3.

intellivision

newbie

Activity: 31

Merit: 0

Quote from: giv on July 23, 2013, 09:31:42 AM

Quote from: intellivision on July 22, 2013, 11:59:12 PM

Any chance of a binary for OSX being released in the future?
I'm willing to beta test this if you need someone.

Sorry, but it's very unlikely. I don't have any Apple devices.
But you can try to build a binary from the source files. My patch doesn't add any additional dependencies, so if you can build an original client, you can build a patched client.

Well, I can't compile anything myself since I messed up GCC some time ago on this install, but you could try building it on PureDarwin (http://www.puredarwin.org/)

Also, would you consider working on a bundled Bitcoin-i2p bundle which includes both programs self contained, only uses the daemon for the wallet, and starts and stops the service when the wallet is open and closed?

justusranvier

legendary

Activity: 1400

Merit: 1009

Quote from: giv on July 23, 2013, 09:31:42 AM

Quote from: intellivision on July 22, 2013, 11:59:12 PM

Any chance of a binary for OSX being released in the future?
I'm willing to beta test this if you need someone.

Sorry, but it's very unlikely. I don't have any Apple devices.

There working VMware images of various versions of OSX floating around the 'net, or so I've heard.

giv

sr. member

Activity: 254

Merit: 251

Quote from: intellivision on July 22, 2013, 11:59:12 PM

Any chance of a binary for OSX being released in the future?
I'm willing to beta test this if you need someone.

Sorry, but it's very unlikely. I don't have any Apple devices.
But you can try to build a binary from the source files. My patch doesn't add any additional dependencies, so if you can build an original client, you can build a patched client.

intellivision

newbie

Activity: 31

Merit: 0

Any chance of a binary for OSX being released in the future?
I'm willing to beta test this if you need someone.

matthewh3

legendary

Activity: 1372

Merit: 1003

Quote from: giv on July 11, 2013, 03:26:46 PM

Quote from: matthewh3 on July 04, 2013, 02:58:51 PM

Now that flattr accepting funding through bitcoin have you thought of setting up a flattr profile for the project. So that the project can receive regular funding. I'd be happy to set up a subscription.

I know a little about Flattr. Can I withdraw money from Flattr in bitcoins?

I'm not sure if that's possible yet but its bitcoin friendly. Flattr is about micro-donations with subscriptions if chosen. The BTC0.0001 minimum transaction fee makes donations below BTC0.0050 pretty much pointless. So it could attract donations you'd otherwise miss out on.

giv

sr. member

Activity: 254

Merit: 251

Update 11 Jul 2013
Migrated to 0.8.3.

giv

sr. member

Activity: 254

Merit: 251

Quote from: matthewh3 on July 04, 2013, 02:58:51 PM

Now that flattr accepting funding through bitcoin have you thought of setting up a flattr profile for the project. So that the project can receive regular funding. I'd be happy to set up a subscription.

I know a little about Flattr. Can I withdraw money from Flattr in bitcoins?

matthewh3

legendary

Activity: 1372

Merit: 1003

Now that flattr accepting funding through bitcoin have you thought of setting up a flattr profile for the project. So that the project can receive regular funding. I'd be happy to set up a subscription.

giv

sr. member

Activity: 254

Merit: 251

Update 04 Jul 2013
Release 0.2
Improved I2P related code.
Some GUI indicators are added: number of I2P-connections, I2P/non-I2P mode, static/dynamic I2P-address
An I2P options tab added. (Settings - Options... - I2P)
Now you could generate a new I2P-address or could see your current I2P-address in GUI.

Changes from 0.8.3 mainline will be added soon.

fran2k

hero member

Activity: 784

Merit: 500

Brilliant initiative, please keep this work on.

I'm also amazed this had s so little impact on the forum. Seems like no one is using i2p.

giv

sr. member

Activity: 254

Merit: 251

Sure. I will update as soon as possible.

justusranvier

legendary

Activity: 1400

Merit: 1009

Quote from: giv on June 04, 2013, 06:19:11 PM

Thanks. I think my project is too raw to add to mainline. The next steps are further developing. I preparing a new release now. But it moves forward slower than I wish.

Can you at least update this patch to to 0.8.3?

giv

sr. member

Activity: 254

Merit: 251

Quote from: btc4ever on June 02, 2013, 12:43:21 AM

This is pretty neat. Thanks for your work, and I hope to see it in mainline. So what are the next steps towards that goal? Sounds like writing up a BIP and discussion on dev list. Is that happening?

Thanks. I think my project is too raw to add to mainline. The next steps are further developing. I preparing a new release now. But it moves forward slower than I wish.

giv

sr. member

Activity: 254

Merit: 251

Tunnels are OK. There are too little peers in i2p. Sometimes there are 5-7 peers, sometimes 1-2.

justusranvier

legendary

Activity: 1400

Merit: 1009

Quote from: giv on June 04, 2013, 05:05:49 PM

Using an old wallet.dat should be OK (if you're using the same BerkleyDB version). The problem is in a peers.dat, because I serialize ip+i2p addresses into it, but a standard client serializes ip only. That cause deadlock when the patched client trying to deserialize addresses from an old peers.dat database, and vice-versa.

That's what I meant.

So far the node is only able to maintain 1-2 native_i2p connections. Is that only because there aren't many peers to connect to, or could the number of tunnels for the i2p connection need to be adjusted?

giv

sr. member

Activity: 254

Merit: 251

Using an old wallet.dat should be OK (if you're using the same BerkleyDB version). The problem is in a peers.dat, because I serialize ip+i2p addresses into it, but a standard client serializes ip only. That cause deadlock when the patched client trying to deserialize addresses from an old peers.dat database, and vice-versa.

justusranvier

legendary

Activity: 1400

Merit: 1009

Quote from: giv on June 04, 2013, 06:39:29 AM

I have at least 3 i2p-connections at now. Are you sure that your i2p-router is running? What do you see in stdout and in a bitcoin log? Are you using any command line options?

I was using an old ~~wallet.dat~~ peers.dat, which was causing the deadlocks described in the OP. Now that I deleted that it's working.

giv

sr. member

Activity: 254

Merit: 251

Quote from: justusranvier on June 03, 2013, 09:46:42 PM

I have a bitcoind runnning at

Code:

7jdke2swvteso3yji3amkfidaa4ggvsngltmiucsiutmouyiphfa.b32.i2p

but I can not seem to connect to any other i2p nodes.

I have at least 3 i2p-connections at now. Are you sure that your i2p-router is running? What do you see in stdout and in a bitcoin log? Are you using any command line options?

justusranvier

legendary

Activity: 1400

Merit: 1009

I have a bitcoind runnning at

Code:

7jdke2swvteso3yji3amkfidaa4ggvsngltmiucsiutmouyiphfa.b32.i2p

but I can not seem to connect to any other i2p nodes.

btc4ever

sr. member

Activity: 321

Merit: 250

This is pretty neat. Thanks for your work, and I hope to see it in mainline. So what are the next steps towards that goal? Sounds like writing up a BIP and discussion on dev list. Is that happening?

Topic: Bitcoin client with I2P patch - page 3. (Read 21461 times)