Great, will add this.
I would suggest having a look at this thread also:
https://bitcointalksearch.org/topic/how-and-why-pools-and-all-miners-should-use-the-relay-network-766190
I think it might make sense for you to run the relaynode client code to these as well, or run the same type of relay servers as Matt is running between your 3 nodes. As I understand this use optimised code to transmit the minimum of info across the links. My lay understanding is that a new block only transmits the transactions that have not been sent before via Matt's relay network. This is then fed to a standard bitcoind on the same machine.
Topic: Dedicated bitcoin relay network (Read 1560 times)
Hi all
In order to speed the propagation of mined blocks across the network and therefore reduce the probability of races and orphaned blocks I have created a small network of nodes to act as high speed relays.
I believe that if connected to a reasonable proportion of the hashing power then it may help to reduce the diameter of the network and benefit all. Of course this can already be achieved to some degree by larger pools making p2p connections which I'm sure is widely done. However, by providing an open network I hope this may further democratise the process a little more.
The nodes run unmodified Bitcoin Core 0.9.2.1 on Linux. The network topography is as follows:
Tokyo - 170ms - Newark - 70ms - London
---------------- 235ms ----------------
The nodes are available at:
london.bitroute.io (109.74.192.142 2a01:7e00::f03c:91ff:fe50:c0f)
newark.bitroute.io (198.74.56.68 2600:3c03::f03c:91ff:fe50:75e4)
jsx7mpysstpswjc3.onion
I suggest you use the DNS rather than IP in case a node has to change. Feel free to add the closest one of these (no point in more than one) to your addnodes.
Any thoughts on this and if there is something else that would benefit let me know.
Cheers
Paul
In order to speed the propagation of mined blocks across the network and therefore reduce the probability of races and orphaned blocks I have created a small network of nodes to act as high speed relays.
I believe that if connected to a reasonable proportion of the hashing power then it may help to reduce the diameter of the network and benefit all. Of course this can already be achieved to some degree by larger pools making p2p connections which I'm sure is widely done. However, by providing an open network I hope this may further democratise the process a little more.
The nodes run unmodified Bitcoin Core 0.9.2.1 on Linux. The network topography is as follows:
Tokyo - 170ms - Newark - 70ms - London
---------------- 235ms ----------------
The nodes are available at:
london.bitroute.io (109.74.192.142 2a01:7e00::f03c:91ff:fe50:c0f)
newark.bitroute.io (198.74.56.68 2600:3c03::f03c:91ff:fe50:75e4)
jsx7mpysstpswjc3.onion
I suggest you use the DNS rather than IP in case a node has to change. Feel free to add the closest one of these (no point in more than one) to your addnodes.
Any thoughts on this and if there is something else that would benefit let me know.
Cheers
Paul
Jump to: