What is the X-Confirmation pattern, and why is it needed at all?

Wait for X additional blocks to be mined on top of the block containing your transaction before treating it as final — because proof-of-work immutability is only probabilistic: a recent block can still be replaced by a competing fork.

• Problem. Under proof-of-work (Nakamoto) consensus, the most recent few blocks can be replaced when two miners extend the chain simultaneously and one branch is later abandoned — a chain fork. Transactions in the discarded branch fall back into the pending pool and may be re-mined later, so a freshly included transaction isn't yet safe to rely on.
• Solution. After the transaction is included, wait until X more blocks are built on top of it; then treat it as committed and effectively immutable. Developers choose X for their risk tolerance — each extra block makes reversal exponentially less likely.
• Trade-off. Benefit: immutability rises with X. Drawback: latency — waiting adds delay (Bitcoin's usual 6-confirmation rule is about an hour; a larger X means longer waits). Bitcoin's 6 confirmations assume an attacker holds under ~10% of hash power and accept under 0.1% risk; Ethereum historically recommended about 11 confirmations. Shorter block times raise fork frequency, so faster chains need this pattern more.

Go deeper:

• Blockchain (Wikipedia) — how proof-of-work chains grow, why competing branches (forks) occur, and why depth of confirmation makes reversal exponentially harder.