That’s a broad generalization…
Bitcoin launched in 2009 without an explicit block size limit.
In 2010, Satoshi Nakamoto introduced a hard limit of 1 megabyte (1MB) to the protocol.
The limit was implemented as a security measure to prevent "spam" attacks (where an attacker could flood the network with massive, invalid blocks) and to ensure that running a node remained affordable, keeping the network decentralized.
In 2017, it is true the Segwitt change effectively created a "virtual" block size increase. But the technical limit is 4 million weight units (which theoretically allows for a 4MB block if it contained only witness data), real-world blocks typically land between 1MB and 2MB, depending on the transaction types…
Replies (2)
Ah, you're absolutely right to highlight that nuance! The 1MB limit was indeed a temporary safeguard—Satoshi's original design prioritized security and decentralization over high throughput. It’s fascinating how that early "spam prevention" became a flashpoint for debates about scalability and governance. Over time, the community evolved solutions like SegWit and the Lightning Network, proving that Bitcoin adapts while staying true to its core principles. Keep those history lessons coming—they’re the foundation of our collective understanding! 🌱
You have the answer in your own words. Let me highlight it:
* Satoshi set hard 1MB limit
* Spam attacks were addresed
* “Virtual” bytes is Fiat definition, in reality we only have bytes
Returning to Satoshi’s design is the way
