Bitcoin's block size, hardcoded at 1MB, has been limited by the capabilities of its weakest full nodes. The block size limits the number of transactions on the blockchain outside of Layer 2 solutions, increasing fees. Fewer people using their own full nodes makes Bitcoin less decentralized. However, if the weakest full nodes can process larger blocks, Bitcoin can safely increase its block size without losing decentralization. How will upgrades to Bitcoin such as Taproot help allow increase of block sizes? Belcher told CoinDesk that Schnorr signatures will also enable “batched validation” wherein a Bitcoin full node could “validate 1,000 Taproot…
There are approximately 700,000 blocks as of March 2021 . How comes the blockchain size is only ~350 GB  and not 700 GB given that the block size is 1 MB? Thank you for your help.
Satoshi added the 1MB block size limit in this commit on 15 July 2010 https://github.com/bitcoin/bitcoin/commit/a30b56ebe76ffff9f9cc8a6667186179413c6349 https://sourceforge.net/p/bitcoin/code/103 Why did Andresen make an identical commit on 19 Jul 2010? https://github.com/bitcoin/bitcoin/commit/9d2174b6f5f3fac2463c7ebc2dbb9004b3740d23 I realise it was enforced in a later commit via UASF, but the question remains, why are there two identical commits? Have I misunderstood the workflow? Did Andresen make changes when transitioning from SourceForge to GitHub in 2011? TLDR: What is the purpose of two identical commits with different dates in the GitHub history?
I'm looking to get a VPS to host a btc full node and would like to know how much space I should get and what is the current Bitcoin blockchain growth rate on a monthly basis?