OpenCyber Academy
Rapid course · Lesson 1 · English
Course code: OCA-009Lesson 01: OCA-009-A001

Web3, blockchain and cryptoasset security: foundations and decisions

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Lesson map

Lesson 01 published. Map, example, EX001.

flowchart TD
  N0["Learning outcomes"]
  N1["1.1 The case and the basics"]
  N2["1.2 Tokens, keys and contracts"]
  N3["1.3 Where risk sits and the first decision"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX001"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["1.1 The case and the basics"]
  N2["1.2 Tokens, keys and contracts"]
  N3["1.3 Where risk sits and the first decision"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX001"]
[Learning outcomes]
    |
    v
[1.1 The case and the basics]
    |
    v
[1.2 Tokens, keys and contracts]
    |
    v
[1.3 Where risk sits and the first decision]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX001]

Learning outcomes

You will (1) explain what blockchains, tokens, keys and smart contracts are; (2) recognise where risk sits; (3) make an informed first decision.

1.1 The case and the basics

Elena Varga manages operations at the fictional Copperleaf Coffee Roasters, a business with four cafés and about 3,000 regular customers. A vendor has proposed running the café loyalty scheme as points tokens on a small permissioned Ethereum-compatible ledger. Elena joins a one-month intensive course at the fictional Quickstart Security Academy, coached by Mr Samuel Otieno, to decide sensibly. Every person, business and number here is synthetic. She learns that a blockchain is a shared, append-only record of transactions in linked blocks, as Nakamoto's 2008 paper described, kept consistent by several computers called nodes.

1.2 Tokens, keys and contracts

A token is an entry on the ledger recording who holds how many units of something, here loyalty points. Holdings are controlled by private keys: whoever holds the key for an address can move its tokens, and the ledger cannot tell whether that person is the rightful owner. A smart contract is a program stored on the ledger that sets the rules, such as who may create points and how they are spent, as Buterin's whitepaper describes. Elena notes that the most powerful thing in the system is whoever controls the contract's privileged functions, such as creating points or changing the rules.

1.3 Where risk sits and the first decision

Elena learns that many losses in this field come from poorly protected keys and weak operations rather than from the ledger itself, and that the OWASP Smart Contract Top 10 lists access control failures among the most common contract weaknesses. She also asks whether a blockchain is needed at all; NIST IR 8202 encourages organisations to consider simpler alternatives. Her first decision is not to say yes or no yet, but to require answers to three questions from the vendor: who controls privileged functions, where customer data will be stored, and how problems would be detected and fixed.

Worked example

Elena defers the yes-or-no decision and asks the vendor who controls privileged functions, where customer data lives and how problems are detected.

Synthetic case. Elena Varga, Mr Samuel Otieno, Quickstart Security Academy, Copperleaf Coffee Roasters and the vendor are synthetic; Nakamoto, Buterin, OWASP SC Top 10 and NIST IR 8202 are real sources.

Errors and limits

Assuming a blockchain makes a system secure ignores that keys and operations carry most risk.

Exercises

Synthesis

Understanding tokens, keys and contracts lets a manager ask the questions that matter before deciding.

Continue studying — lesson 01 (chapter 01 of 20)

← Course home · Course chapter index · Chapter 02 →

Continue to the next authored lesson.

Worked answers

EX001. About 3,000 regular customers across four cafés.

EX002. A shared, append-only record of transactions kept in linked blocks by several nodes.

EX003. Who holds how many units of loyalty points.

EX004. Whoever holds the private key for that address.

EX005. Whether the person holding the key is the rightful owner.

EX006. It sets the rules, such as who may create points and how they are spent.

EX007. Whoever controls the contract's privileged functions.

EX008. Poorly protected keys and weak operations rather than the ledger itself.

EX009. Access control failures.

EX010. Whether a simpler alternative to a blockchain would be enough.

EX011. To defer yes or no until the vendor answers three questions.

EX012. Who controls privileged functions, where customer data lives, or how problems are detected and fixed.

EX013. One month, intensive.