BLOCKCHAIN & WEB3 FUNDAMENTALS - Chapter 8, Exercise 3 Solution
==========================================================
Why CryptoKitties Foreshadows Chapter 9's Own Topic

PROBLEM
-------
Explain why CryptoKitties consuming up to 70% of Ethereum's network
capacity is directly relevant to a topic Chapter 9 hasn't covered yet
- what real, practical problem does this event foreshadow?

SOLUTION
--------
Every transaction on Ethereum - including creating, breeding, or
trading a CryptoKitties NFT - has to be processed and included in a
block by the network, competing for a genuinely limited amount of
space and processing capacity in each new block (Chapter 3's own block
structure, Chapter 4's own mining process). Ethereum, like any single
blockchain, can only process a certain number of transactions within a
given period of time.

When CryptoKitties became extremely popular, an enormous number of
people were all trying to submit transactions to the network
simultaneously, and Chapter 6 already established that every operation
on Ethereum costs gas, paid in ETH. When far more people compete for
the same limited block space than the network can actually process
quickly, this chapter's own real 70%-of-network-capacity figure shows
just how dominant a single popular application could become relative
to everything else trying to use the same shared network at the same
time - leaving little room for other transactions, and in practice
driving up how much people had to pay in gas fees to get their own
transactions processed at all.

This is a real, concrete, early demonstration of a fundamental
limitation: a single blockchain has a real, finite capacity, and
genuine popularity of even one application can noticeably congest the
entire network for everyone else using it. That's precisely the
scaling problem - how does a blockchain network handle far more real
demand than it can natively process at once - that Chapter 9 (Scaling
& Layer 2 Solutions) exists specifically to address.

ANSWER: CryptoKitties' own real network dominance shows that a single
blockchain has genuinely limited transaction capacity, and that even
one sufficiently popular application can congest the whole network and
drive up costs for everyone else - directly foreshadowing the real
scaling problem Chapter 9 covers, since a functioning blockchain
ecosystem needs some way to handle demand well beyond what one chain
can process on its own.

----
WHY THIS WORKS AS AN ANSWER

This connects the concrete, real CryptoKitties congestion event to the
underlying structural cause (limited per-block capacity, competition
for inclusion, rising gas costs under demand) rather than treating it
as an isolated historical anecdote, and correctly identifies it as a
real precursor to Chapter 9's own stated topic.