What does it mean for a blockchain to be decentralized, and how does that prevent any single party from rewriting transaction history?

technical-conceptual · Junior level · software-engineering

What the interviewer is really asking

Assesses whether the candidate understands the core security property of blockchains — distributed consensus and tamper-evidence via hash-linked blocks — not just buzzwords.

What to say

• Explain that the ledger is replicated across many independent nodes, and a new block is only accepted when the network reaches consensus, so no single operator controls the state.
• Describe how each block stores the cryptographic hash of the previous block, so altering an old block changes its hash and breaks every block after it — making tampering detectable.
• Note that rewriting history would require out-competing the honest majority's work or stake (e.g. a 51% attack), which is economically impractical on a large network.

What to avoid

• Claim a blockchain is 'unhackable' or that data can never be changed — the property is tamper-evidence and economic cost, not literal immutability.
• Confuse decentralization with anonymity or with the database simply being 'in the cloud'.
• Describe it purely as a marketing term without naming the hash chain or consensus mechanism that actually delivers the property.

Example answers

Strong: Each node keeps a full copy of the ledger, and blocks are hash-linked — a block commits to the previous block's hash. If I edited a year-old transaction, that block's hash changes and every later block's link breaks, so honest nodes reject it. To force my version, I'd need to redo the work or stake of the whole honest majority, which isn't economically feasible.

Weak: It's decentralized because it's not stored on one company's server, so it's basically impossible to hack and the data can never change.