Quote from: xyzzy099 on August 24, 2014, 01:48:24 PM

Quote from: hamburgerhelper on August 24, 2014, 02:53:50 AM

Quote from: windpath on August 23, 2014, 09:42:58 PM

Quote from: xyzzy099 on August 23, 2014, 09:34:45 PM

Quote from: windpath on August 23, 2014, 08:23:48 PM

Quote from: pmorris on August 23, 2014, 02:34:05 PM

Quote from: matthewh3 on August 23, 2014, 11:36:13 AM

Has anyone read about Matt Corallo's new "bitcoin backbone project" - https://bitcoinfoundation.org/2014/08/a-bitcoin-backbone - would it make sense to connect bitcoind from a P2Pool set up to this low latency backbone.

My take was that what Matt is doing is very cool and when blocks are several MB in size something like this or Gavin's alternative proposal for eliminating retransmission of transactions with every block will be important.

For me, each of my nodes has a connection which p2pool and bitcoind never come close to utilising. So I didn't think the block size was a particularly big deal at the moment from a speed perspective. Don't know if that's been actively researched.

If Matt's built it and it works then I see no reason not to connect to one of his nodes to gain the benefit of it.

I'll be adding Coin Cadence to his east coast relay on the next restart.

If you are running bitcoin-qt, you don't need to wait for a restart - you can just type:

Code:

addnode public.us-east.relay.mattcorallo.com add

in the debug console.

Thanks.

From my brief bit of experimentation, the above doesn't work. It looks like you can't connect bitcoind directly to the Relay Network. You need to run RelayNodeClient which connects to the Relay Network and your local bitcoind.

So you would do:

Code:

java -jar RelayNodeClient.jar public.us-east.relay.mattcorallo.com 127.0.0.1:8333

That worked for me and I saw transactions and blocks passed to my bitcoind. Then you'd just have to get the RelayNodeClient application running in a persistent way (upon startup, with a watchdog, etc.). That will vary based on your operating system. I'll be getting a systemd unit file ready to run on CentOS 7, which is what my node uses. If anyone's interested, I'd be happy to share it.

My bad - you do have to specify port 8335 - but you don't need to use anything but bitcoin-qt, as others have already related above.

It seems that this actually does not work.

It appears that the ADDNODE command in the console will always fail if you already have 8 outgoing connections. It will eventually use the connection you added only if one of your 8 outgoing connections drops.

Sorry again for the misinformation.