Quote from: BlackHatCoiner on Today at 12:42:21 PM

Quote from: stompix on Today at 12:25:21 PM

Again you're making the same mistake, by saying that if a shitcoin doesn't have the needed popularity for 10MB capacity Bitcoin should either.

No, you misinterpreted me. All I'm saying is that even with 10 MB, you will still sooner or later run out of block space, and fee market will arise. The difference is that you will have traded a percentage of the expenses of the user for the risk to split the network in half, and that there will be greater incentive to use it as a cloud storage.

whilst worrying about "expense of the user" a $150 hard drive bought in 2012 and is 3TB which is enough for historic data plus future data of next 5 years... thus dividing cost by 17 years is less then $10 a year

you are ignoring that instead of 2500 average legacy transactions there can be 25,000 legacy average
you are ignoring that instead of 4000 lean legacy transactions there can be 40,000 legacy average
where by instead of paying $2 a day for daily use ($730/year) they can pay $73/year, saving them $637/year

so while you point fingers at the $10/year hardware cost your ignoring the $730/year transaction cost for daily use

Quote from: BlackHatCoiner on Today at 12:42:21 PM

I have pointed out that your analogy with the roads isn't accurate. If we double the roads, it doesn't mean the cars will double. But if the block size limit is 10 MB, then you should expect it to be full. If the block size is 100 MB, same. And same with 1 GB. If you take a look into BSV, they save entire movies. That is a verification nightmare, kills off the competition for small mining pools, and turns the currency into a shitcoin.

movies dont get verified.. thats how they get in.. they bypass verification
also transaction verication of actual bitcoin rules is done 99.99% of the time at the pre-confirm relay of zero-confirm transactions..
funnily enough your favoured subnetwork devs had admitted that verifying transaction data shows nodes can handle millions of transactions a second..
funnily enough when node mempools hold 300mb of validated transactions and a block contains only 4mb.. your aruments about what a node can handle fall flat on its face