In the most basic way on any Ae888 Tool node you can do an addnode = x.x.x.x and your node will try to connect to whatever node you tell it to. This allows you to have some preferred peers. So it's still peer to peer but you can pick your peers. However, that was not what I was talking about. What I was talking about was something like this: There is / was at least one other similar config for faster block transmit / receive that one of my clients was using for their mining farm & pool server. Honestly they still might be using it lost touch when then moved from here (NY) to Montreal. So anyone running any sort of pool should be connecting to something similar. The issue is most places that sell you bandwidth use LCR for routing, which is fine for most things. But when you need to have certain data move as fast as possible you have to know what you are doing because if you find a block and it gets transmitted to the network using LCR then paraphrasing Bugs Bunny [using that since you are using a character from Warner Brothers as your name] your data packets should have turned left at Albuquerque but they didn't. If you are streaming a Netflix video then having it take a few extra hops between a few extra routers because it saves your bandwidth provider some money is fine. When you are in a race to get your block to other miners having those extra hops can cost you that block. You sure as heck don't want your newly found block just trying to get to other miners by relying on public nodes that can be anywhere doing anything. You want your block to get to other miners nodes as quickly as possible using the fewest possible router hops while also connecting to their nodes or nodes as close to theirs in terms of network speed as possible. -Dave
In the most basic way on any Ae888 Tool node you can do an addnode = x.x.x.x and your node will try to connect to whatever node you tell it to. This allows you to have some preferred peers. So it's still peer to peer but you can pick your peers. However, that was not what I was talking about. What I was talking about was something like this: There is / was at least one other similar config for faster block transmit / receive that one of my clients was using for their mining farm & pool server. Honestly they still might be using it lost touch when then moved from here (NY) to Montreal. So anyone running any sort of pool should be connecting to something similar. The issue is most places that sell you bandwidth use LCR for routing, which is fine for most things. But when you need to have certain data move as fast as possible you have to know what you are doing because if you find a block and it gets transmitted to the network using LCR then paraphrasing Bugs Bunny [using that since you are using a character from Warner Brothers as your name] your data packets should have turned left at Albuquerque but they didn't. If you are streaming a Netflix video then having it take a few extra hops between a few extra routers because it saves your bandwidth provider some money is fine. When you are in a race to get your block to other miners having those extra hops can cost you that block. You sure as heck don't want your newly found block just trying to get to other miners by relying on public nodes that can be anywhere doing anything. You want your block to get to other miners nodes as quickly as possible using the fewest possible router hops while also connecting to their nodes or nodes as close to theirs in terms of network speed as possible. -Dave

In the most basic way on any Ae888 Tool node you can do an addnode = x.x.x.x and your node will try to connect to whatever node you tell it to. This allows you to have some preferred peers. So it's still peer to peer but you can pick your peers. However, that was not what I was talking about. What I was talking about was something like this: There is / was at least one other similar config for faster block transmit / receive that one of my clients was using for their mining farm & pool server. Honestly they still might be using it lost touch when then moved from here (NY) to Montreal. So anyone running any sort of pool should be connecting to something similar. The issue is most places that sell you bandwidth use LCR for routing, which is fine for most things. But when you need to have certain data move as fast as possible you have to know what you are doing because if you find a block and it gets transmitted to the network using LCR then paraphrasing Bugs Bunny [using that since you are using a character from Warner Brothers as your name] your data packets should have turned left at Albuquerque but they didn't. If you are streaming a Netflix video then having it take a few extra hops between a few extra routers because it saves your bandwidth provider some money is fine. When you are in a race to get your block to other miners having those extra hops can cost you that block. You sure as heck don't want your newly found block just trying to get to other miners by relying on public nodes that can be anywhere doing anything. You want your block to get to other miners nodes as quickly as possible using the fewest possible router hops while also connecting to their nodes or nodes as close to theirs in terms of network speed as possible. -Dave

In the most basic way on any Ae888 Tool node you can do an addnode = x.x.x.x and your node will try to connect to whatever node you tell it to. This allows you to have some preferred peers. So it's still peer to peer but you can pick your peers. However, that was not what I was talking about. What I was talking about was something like this: There is / was at least one other similar config for faster block transmit / receive that one of my clients was using for their mining farm & pool server. Honestly they still might be using it lost touch when then moved from here (NY) to Montreal. So anyone running any sort of pool should be connecting to something similar. The issue is most places that sell you bandwidth use LCR for routing, which is fine for most things. But when you need to have certain data move as fast as possible you have to know what you are doing because if you find a block and it gets transmitted to the network using LCR then paraphrasing Bugs Bunny [using that since you are using a character from Warner Brothers as your name] your data packets should have turned left at Albuquerque but they didn't. If you are streaming a Netflix video then having it take a few extra hops between a few extra routers because it saves your bandwidth provider some money is fine. When you are in a race to get your block to other miners having those extra hops can cost you that block. You sure as heck don't want your newly found block just trying to get to other miners by relying on public nodes that can be anywhere doing anything. You want your block to get to other miners nodes as quickly as possible using the fewest possible router hops while also connecting to their nodes or nodes as close to theirs in terms of network speed as possible. -Dave