What you know now
Suggest an editYou reached the end of Blockchain basics. Now you know the parts a blockchain is built from, the constraint behind each of them, and what each one costs.
One Bitcoin payment uses all of them. Say Alice pays Bob 0.3 BTC:
- Alice's wallet derived her private key from a seed phrase. She signs the transaction with that key, and every node checks the signature with her public key, without needing the private one. Those are mnemonic phrases and digital signatures.
- The transaction destroys her 1.0 BTC coin and creates two new ones, 0.3 BTC for Bob and the change for Alice. No balance is stored anywhere, which is the UTXO model.
- A miner puts the transaction into a block. The block header holds a Merkle root that commits to every transaction in the block, and the hash of the previous block, so changing the payment later would break every block after it.
- To add the block, the miner has to find a nonce that puts the header's hash below the target. That work costs electricity no matter how many identities an attacker creates, which is how strangers reach consensus through proof of work.
- Bob waits about ten minutes for the block, and about an hour if the amount is large. The ten minutes are part of what Bitcoin gave up so that each block reaches the whole network and anyone can verify the chain on consumer hardware. The hour is there because every extra block makes the payment more expensive to reverse.
None of these parts is there for its own sake. Each one answers a constraint that appears once there is no operator to trust.
What to do with it
Pick a chain this course only mentioned or did not cover, for example Bitcoin Cash from the forks lesson, and answer four questions about it:
- Who is allowed to run a node and add blocks?
- What does taking part in consensus cost: work, stake, or an operator's permission?
- What limits its throughput, and can a hobbyist run a full node on a laptop?
- What did its designers give up, and what did they get for it?
The lessons on public and private chains and the trilemma show how these questions are answered for the chains you already know.
After that, there are two tracks to continue with. The Solidity track teaches you to write the contracts that run on Ethereum and the chains that copied its design. The Solana track teaches you to write programs in Rust against a different account model and execution environment. You can take either, both, or neither, and use what you learned here to follow the field on your own.