-snip-
I don't see 540 MB blocks as a problem at all. People download fullHD and 4k video streams every day at their laptop while running youtube. There is enough bandwidth and space for big blocks these days.
that is 540 MB per block. there is one block every 10 minute on average which means 144 blocks per day or 144* 540 MB = ~77.76 GB per day. and you are storing this amount every day
in other words comparing this process with video streaming is wrong on so many levels! first is that you don't store the videos you stream. you just watch temporarily. second you don't verify anything, you just watch a video which will consume little CPU power but a block needs to be verified, you don't just download it. you have to check every byte to see if it is a valid thing or fake. and that takes CPU and RAM and eventually you will find yourself needing only a strong computer to handle a full node and end up with master nodes aka centralization.
Sure, 540 MB is huge, I admit it even though I am an advocate of block increases. This is why I thought of small increases over time, because I am sure that in, say, 10 years 540 MB block will not be considered huge anymore.
Currently 540MB per block (=78 Gb per day) is infeasible also because setting up a new full node requires downloading the full history and it would take months or years if the increment were 78 Gb each day (it takes days or weeks with current block size). However, it is all
currently only.