Core Concepts for Blockchain and Web3 Developers
Blockchain core concepts are the base ideas every Web3 developer needs: a distributed ledger agreed on by many nodes through consensus, hashes and digital signatures that make records tamper-evident, and wallets that hold keys controlling accounts. This unit opens the roadmap and explains why later contract code behaves the way it does.
Stage: Foundations · Part of the Blockchain and Web3 Developer roadmap · Last reviewed 19 November 2026
What to learn in Core Concepts
- Explain how nodes agree on one ledger using proof of work or proof of stake
- Describe how a hash function links blocks and detects tampering
- Sign a message with a private key and verify it against a public address
- Distinguish externally owned accounts from contract accounts
- Explain what a seed phrase protects and why losing it is final
Core Concepts interview questions
Why can a blockchain not be edited after a block is added?
Each block stores the hash of the previous block, so changing old data changes every later hash. An attacker would also have to redo the consensus work or stake across the honest majority. That cost, not a rule, is what makes history practically immutable.
What is the difference between a private key, a public key and an address?
The private key is a secret number that signs transactions. The public key is derived from it and lets anyone verify those signatures. The address is a shorter identifier derived from the public key by hashing. You share the address, never the private key.
Where Core Concepts fits in the Blockchain and Web3 Developer roadmap
Core Concepts belongs to the Foundations stage (beginner level), which takes about 6 hours. Why blockchains work.
Other units in this stage
Back to the full Blockchain and Web3 Developer roadmap