Bitcoin doesn't have a problem with scaling btw
it does have a problem.
by not being allowed to scale. (im not talking about the baited one-time half gesture segwit)
we should have had real scaling changed years ago
scaling which grows naturally over time(not stupid gigabytes by midnight, but instead natural node capable and managed by nodes scaling over time(not devs, not pools))
-- it simply was never designed to execute thousands of transactions per second like a credit card.
thats a close mind statement to make
like computers were never designed for call of duty or video calls 20 years ago, but now its natural and no big deal
let me guess, you would love to go back 20 years and tell skype, twitch, youtube, google, to never get into the computer industry because
online gaming and video content was never designed to work on a computer. i can hear you now "just dont bother"
your mindset seems to be either 0 to 1billion in one night else dont bother.
you fail to realise that natural growth over say 3 decades where nodes are allowed to set limits that change over time, CAN scale..
just not gigabytes by midnight, but instead slow natural capable increments over months-years
Increasing block size, won't change that or solve issues with unconfirmed transactions.
HALTing onchain growth wont solve issues either
whats next, shoot childrens feet or break their knee caps at 8months old out of fear that they may run infront of a car should they slowly learn to walk?
how about slowly teach them to walk and naturally ensure they check for risks, and learn when its safe to cross a road... kneecapping them is not the answer
i bet you would love a world of locking children into wheelchairs where a parent(hub) has control of risk by refusing movement(not signing) or controling it(setting the rules/routing costs/participants).
Block size really is a pointless debate.
blocksize alone is not the solution. especially if devs are baiting the blocksize with stupid methods.
EG
v0.12 maxBLOCKsigops 20k maxTXsigops 4k 1mb baseblocklimit
v0.14 maxBLOCKsigops 80k maxTXsigops 16k (1mb baseblocklimit - 3mb arbitrary space if people opt-in)
that there alone is the devs letting more native quadratic spam continue.. and infact get worse. they are literally causing the problem to try and say making bigger blocks 'just doesnt work' .. the devs are baiting the narrative yet not doing a proper job of solving the issue
you can literally hear the future echo's from their corporate chambers ripple back through time
"we the king overlord devs gave you 4mb[empty halfbaked gesture] weight, but still blocks are being filled by 5 insanely spammy tx's that now take 8minutes to validate instead of 10 seconds"
they are baiting the community, not solving the problem
their solution:
4mb weight: 1mb base, maxBLOCKsigops 80k, maxTXsigops 16k
knowing not everyone moves to segwit keypairs to use the 'weight'- their echo chamber script "see people dont want more tx's, the 4mb isnt even being used"
knowing corps making a point will spam baseblock - their echo chamber script "see validation times have got worse"
real solution
1mb baseblock: maxBLOCKsigops 20k, maxTXsigops 2k
2mb baseblock: maxBLOCKsigops 40k, maxTXsigops 1k
4mb baseblock: maxBLOCKsigops 80k, maxTXsigops 500
again not
4mb weight: 1mb base, maxBLOCKsigops 80k, maxTXsigops 16k
real solutions reduce spammy validations times and allow more lean tx's over time. blockstream devs bait does the opposite