Quote from: Holliday on January 20, 2017, 03:13:29 AM

Perhaps because none of those things come even remotely close to 1 terabyte a month worth of uploading (which a stock Bitcoin node will happily do)?

If you are going to make comparisons to justify your position, at least make decent ones.

1tb a month lol

ok.. uploading. 8gb/month to send live relay of tx's and new blocks. per connection

for instance.
100 connections to fully synced node requires 800gb
10 connections to fully synced node requires 80gb

as for helping other nodes sync. that is the killer data wise.

100 connections to 0 synced node(where your its only seed) requires 9.88tb (yea doom)
10 connections to 0 synced node(where your its only seed) requires 988gb (yea doom)
1 connections to 0 synced node(where your its only seed) requires 98.8gb (manageable)

the solution.
dont have 100connections..
reduce the connections= reduce the data needed to upload.
especially dont connect to nodes that are not near/already synced.. thats the main trick.

to emphasise this point..
if 75 nodes had 75 connections 5625nodes would get the data in 1 relay.
so anything over 80 is overkill/not required.

i can safely assume atleast 75 people have good internet. so not all 5600 nodes need to upload to that many. as the recipient probably already got the data via someone elses node. so if bandwidth is an issue.. bring your connections down. dont act like a 'supernode' if you are only an average node.

this is also why blockstream are doing their 'fibre' (supernodes) so that they get the data out in one relay so that other nodes dont have to do all the work.. which means you can happily play '6 degrees of separation' with 6connections(48gb) just to relay tx data and blocks so the nod can get second opinions from other sources.