Hacker News new | past | comments | ask | show | jobs | submit login

It's not possible to have an uncapped block size. As blocks get larger they take longer to propagate through the network. Longer propagation means more forks, which means more work is wasted on forks which do not become canonical, which lowers the effective hash rate of the network and therefore the threshold for a 51% attack.

2MB is far too small, but it would be a gross mistake to overcorrect by removing the cap entirely.

See, for example: https://www.gsd.inesc-id.pt/~ler/docencia/rcs1314/papers/P2P...

> On an actually uncapped Bitcoin instance, Blocks (Block size) and transaction fees will grow exponentially

Transaction fees would drop to zero. The fee is a bid in an auction for scarce block space. If block space is not scarce then the winning bid is always zero.




Uncapped is a pseudo name for “capped just in time”. It’s never really uncapped.

If you’re interested in some work being done on such larger blocks, you’ll enjoy this presentation:

https://m.youtube.com/watch?v=5SJm2ep3X_M&feature=youtu.be




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: