← العودة إلى الامتحان

دليل دراسي مجاني

Blockchain Systems Engineer — Free Curriculum

This free curriculum covers every domain assessed in the Oxford Certified Blockchain Systems Engineer examination: cryptography, blocks, consensus, networks, keys and wallets, smart contracts, security, tokens, scalability, enterprise blockchain and solution design. Read each chapter, note the key points, and then sit the 70-question examination.

الفصل 1

Cryptographic foundations

Blockchains rely on cryptographic hash functions. A hash maps any input to a fixed-size output; it is one-way, deterministic and collision resistant — it is infeasible to find two inputs with the same hash. The avalanche effect means a tiny change in input produces a completely different hash, which makes tampering obvious.

Public-key cryptography gives each user a private key and a public key. A transaction is signed with the private key, and anyone can verify the digital signature with the public key. Zero-knowledge proofs go further, proving that a statement is true without revealing the underlying data.

  • Hashes: one-way, deterministic, collision resistant, avalanche effect
  • Private key signs; public key verifies
  • Signatures prove authorisation of transactions
  • Zero-knowledge proofs prove facts without revealing data
الفكرة الأساسية: Cryptography, not trust in a central party, secures the ledger.
الفصل 2

Blocks, chains and Merkle trees

Each block contains transactions and a header with the hash of the previous block, linking blocks into a chain. Altering an old block changes its hash and breaks every following link; on proof-of-work chains, an attacker would need to redo the work for that block and all later blocks faster than the honest network.

The Merkle root summarises all transactions in a block in a single hash. Any change to a transaction changes the root, and Merkle proofs let light clients verify a transaction's inclusion without downloading the whole chain. Full nodes store and validate the entire chain; block explorers let anyone inspect blocks, transactions and addresses.

  • Blocks link through previous-block hashes
  • Merkle roots make tampering detectable and proofs efficient
  • Light clients use Merkle proofs; full nodes validate everything
  • Immutability = practically impossible to alter without detection and agreement
الفكرة الأساسية: The chain of hashes is what makes history tamper-evident.
الفصل 3

Consensus mechanisms

Consensus lets distributed nodes agree on one history. In proof of work, miners search for a nonce that makes the block hash meet a difficulty target; security comes from the cost of computing power, and an entity with a majority of hash power could mount a 51% attack. Proof of stake selects validators according to staked collateral; it uses far less energy, needs no mining hardware and punishes provable misbehaviour, such as double-signing, through slashing.

Byzantine fault tolerant (BFT) protocols reach agreement even when some nodes are faulty or malicious, up to a threshold, and often provide fast finality — the point after which a block cannot be reversed. Protocol changes happen through forks: soft forks are backward-compatible tightenings of the rules; hard forks are not backward-compatible and can split the chain.

  • PoW: computational work and difficulty targets
  • PoS: staked collateral and slashing
  • BFT: tolerance of faulty or malicious nodes, fast finality
  • 51% attacks threaten PoW chains with concentrated power
  • Soft forks vs hard forks
الفكرة الأساسية: Consensus is the rulebook that lets strangers agree on one truth.
الفصل 4

Public and permissioned networks

Public permissionless blockchains allow anyone to read, transact and validate. Permissioned (private or consortium) blockchains restrict participation to known, authorised parties and control who can validate or read data. Consortium chains suit groups of organisations — sometimes competitors — that need a shared, trusted record without one controlling party.

A blockchain is not always the right tool. When a single trusted party controls the data, a conventional database is simpler, faster and cheaper. Evaluate platforms by throughput, cost, security model, decentralisation needs, privacy and governance. Testnets let teams deploy and test with valueless tokens before mainnet.

  • Permissionless = open; permissioned = known participants
  • Consortium chains for shared records across organisations
  • No shared-trust problem → use a database
  • Evaluate throughput, cost, security, privacy and governance
  • Always test on testnets first
الفكرة الأساسية: Use blockchain where multiple parties need shared truth without a single trusted owner.
الفصل 5

Keys, wallets and transactions

Whoever holds the private key controls the assets. Never share private keys or seed phrases. Custodial wallets let a third party such as an exchange hold the keys; non-custodial wallets leave keys with the user. Hardware wallets keep keys on a dedicated device and sign without exposing keys to internet-connected computers.

Organisations protect high-value keys with multi-signature wallets, hardware security modules and tested recovery procedures; a single administrator key is a single point of failure. Bitcoin uses the UTXO model, in which transactions consume unspent outputs and create new ones; Ethereum uses an account model in which a nonce orders each account's transactions and prevents replay. Public blockchain transactions are pseudonymous, not anonymous: addresses can often be linked to people.

  • Private keys and seed phrases are secrets
  • Custodial vs non-custodial; hardware wallets for security
  • Multi-sig and HSMs for organisations
  • UTXO vs account model; nonces prevent replay
  • Pseudonymous ≠ anonymous
الفكرة الأساسية: Key management is the most important security control a user or company owns.
الفصل 6

Smart contracts and the EVM

Smart contracts are programs deployed on a blockchain that execute automatically. On Ethereum they run on the Ethereum Virtual Machine; each operation costs gas, paid as fees, and fees rise when demand for block space is high. Deployed code cannot be edited; upgradeable proxy patterns separate stored state from replaceable logic.

On-chain storage is expensive, so large files stay off-chain with only hashes or references on-chain — for example, recording a document hash and timestamp proves the document has not been altered without publishing it. Contracts emit events that off-chain applications use to track activity efficiently.

  • EVM execution, gas and fees
  • Deployed code is immutable; use proxies for upgradeability
  • Keep large data off-chain; store hashes on-chain
  • Events connect contracts to applications
الفكرة الأساسية: Design contracts as if they can never be fixed — because often they cannot.
الفصل 7

Smart-contract security

Common vulnerabilities include reentrancy (an external call re-enters a function before state is updated — defended by the checks-effects-interactions pattern and reentrancy guards), missing access control on sensitive functions, front-running of visible pending transactions, and price manipulation through weak oracles, often combined with flash loans — uncollateralised loans borrowed and repaid in one transaction.

Defences include independent audits, comprehensive automated tests, well-reviewed libraries, formal verification of critical properties, bug bounty programmes and decentralised, aggregated price oracles with time-weighted averages.

  • Reentrancy: update state before external calls
  • Enforce role and ownership checks
  • Expect front-running and flash-loan attacks
  • Use robust, aggregated oracles
  • Audit, test, verify and reward researchers
الفكرة الأساسية: In smart contracts, a single bug can be irreversible and public.
الفصل 8

Oracles, tokens and digital assets

Blockchains cannot fetch external data themselves — the oracle problem — so oracles supply data such as prices and become critical trust points. ERC-20 defines fungible tokens; ERC-721 defines non-fungible tokens with unique identifiers. Owning an NFT does not automatically transfer copyright. Stablecoins aim to keep a stable value relative to a reference such as a fiat currency. Tokenisation represents ownership rights in real-world assets such as property or bonds.

Decentralised autonomous organisations (DAOs) encode governance rules in smart contracts and let token holders vote on decisions.

  • Oracles bridge on-chain and off-chain data
  • ERC-20 fungible; ERC-721 unique
  • NFT ownership ≠ copyright
  • Stablecoins and real-world asset tokenisation
  • DAOs: governance by smart contract and token holders
الفكرة الأساسية: Tokens represent rights — understand exactly which rights they carry.
الفصل 9

Scalability and layer-2 solutions

The blockchain trilemma describes the difficulty of achieving decentralisation, security and scalability at the same time. Layer-2 solutions execute transactions off the main chain: optimistic rollups assume validity and allow fraud challenges; ZK rollups post cryptographic validity proofs; payment and state channels let parties transact off-chain and settle the final result on-chain. Sharding splits workload or data across partitions processed in parallel.

When fees make an application unusable, move frequent low-value interactions to layer 2 or batch them while settling on the main chain.

  • Trilemma: decentralisation, security, scalability
  • Optimistic vs ZK rollups
  • Channels for repeated off-chain interactions
  • Sharding for parallel processing
  • Batch and use layer 2 to cut fees
الفكرة الأساسية: Scale by moving work off the main chain while keeping its security guarantees.
الفصل 10

Interoperability and bridges

Cross-chain bridges move assets and messages between blockchains. A typical "lock-and-mint" bridge locks tokens in a contract on the source chain and mints equivalent wrapped tokens on the destination chain; burning the wrapped tokens later releases the originals.

Because bridges often hold large pools of locked assets and rely on complex validation — sometimes a small group of validators or a multi-signature committee — they have been frequent targets of major hacks. Assess a bridge's validation model, the security of its keys, its audit history and how it would respond to an incident before relying on it.

  • Bridges connect separate chains, often through lock-and-mint
  • Locked assets make bridges high-value targets
  • Review the validator set and key management
  • Check audits and incident-response capability
  • Limit exposure: do not keep more value bridged than necessary
الفكرة الأساسية: Every bridge adds new trust assumptions — evaluate them explicitly.
الفصل 11

Enterprise blockchain and regulation

Hyperledger Fabric is a permissioned enterprise framework with pluggable consensus and channels — private sub-ledgers visible only to selected organisations. Participants have known identities issued by membership services, which supports accountability and regulatory requirements.

Enterprise designs keep personal data off-chain and store only hashes, references and events on-chain, because data protection laws may require personal data to be corrected or erased, which conflicts with immutability. Consortium projects also need clear governance: who may join, who runs nodes, how rules change and how disputes are settled.

  • Fabric: permissioned, channels, pluggable consensus
  • Keep personal data off-chain
  • Design for privacy law from the start
  • Govern consortium membership and rules clearly
الفكرة الأساسية: In enterprise projects, governance and privacy design matter as much as technology.

مستعد؟ ابدأ الامتحان المجاني

قدّم الامتحان واحصل على شارتك الرقمية مجاناً. بعد النجاح يمكنك طلب الشهادة الرسمية.

ابدأ الامتحان المجاني