Learn
5.2.1–2 | DIGITAL CURRENCY
01 | WHAT IS DIGITAL CURRENCY?
A digital currency is a currency that exists only electronically. Its value is represented through digital records rather than physical coins or banknotes for that currency.
It can be used to transfer value between parties or pay for goods and services where accepted.
Pictures of shiny coins are illustrations: they do not mean the electronic currency exists as those physical objects.
Do not confuse digital currency with every digital payment. Paying by card can transfer ordinary money recorded electronically. A cryptocurrency such as Bitcoin is one example of a digital currency, but not every electronic payment uses cryptocurrency or blockchain.
02 | HOW CAN IT BE USED?
| Use | What happens | Condition |
|---|---|---|
| Payment | Transfer digital value for a product or service | The recipient must accept that currency |
| Transfer between users | Move value between recognised destinations | The system must authorise and record the transfer |
| Cross-border transfer | Exchange value across geographical borders | Fees, rules and access depend on the system |
The computer science question is how the system represents ownership and records valid transfers. Different systems can use different operators, ledgers and validation methods.
Not every digital currency is decentralised. Some systems use a central operator; others share validation and records across a network.
03 | WHY A LEDGER IS NEEDED
A ledger is a record of transactions. A digital currency system needs reliable information about which transfers are valid and how value has been assigned.
Electronic data can be copied, but copying a transaction message must not create unlimited spendable currency.
Double spending means attempting to spend the same available digital value more than once. A valid ledger and the system’s checks help prevent conflicting transfers from both being accepted.
The transaction record matters because later checks depend on the accepted history.
04 | WHAT IS A BLOCKCHAIN?
A blockchain is a digital ledger made from ordered blocks of records. In the syllabus’s basic description, it is a time-stamped series of records that cannot be altered.
Technically, the design makes unauthorised changes detectable and difficult to have accepted, rather than making stored bits physically impossible to edit. Cryptographic links and the network’s validation rules protect the accepted history.
Blocks can contain several transactions. Each later block refers to the previous block through a cryptographic hash, forming a chain.
Many blockchain currency systems share ledger information across network participants. The exact design varies, so not every system uses the same approval process.
05 | SEE THE LINKED BLOCKS
BLOCK 1
Time: t1
A → B: 3 units
Hash label: H1
BLOCK 2
Previous hash: H1
Time: t2
B → C: 1 unit
Hash label: H2
BLOCK 3
Previous hash: H2
Time: t3
A → C: 2 units
Hash label: H3
H1, H2 and H3 are labels for this diagram, not actual computed hashes. A real block normally contains additional information, and can contain many transactions.
The transaction records show transfers. The previous-hash references link the ordered blocks. A timestamp provides time information; it is not by itself a security mechanism.
06 | HASHES: DETECTING CHANGE
A cryptographic hash is a fixed-length value calculated from input data. It acts as a fingerprint for the input, although different inputs can theoretically collide.
Changing a recorded transaction normally changes the relevant hash. A later block’s stored reference then no longer matches the changed earlier block.
Hashing is not encryption. A hash is not normally decrypted to recover the transaction. Its role here is linking and checking data integrity.
Someone could edit a local copy and recalculate links, so hashes alone are not enough. Validation and consensus rules determine which history the network accepts.
07 | FOLLOW A TRANSACTION
- Create and authorise the transfer.
A user prepares a transaction. In cryptocurrency systems, a digital signature can demonstrate authorisation using the relevant private key.
- Send it to the network.
Participants receive the proposed transaction.
- Check validity.
Checks can include authorisation, available value and whether that value has already been spent.
- Include valid records in a proposed block.
The block links to the existing chain.
- Apply the system’s consensus rules.
Participants determine which valid block history to accept.
- Record the accepted transfer.
The ledger can then support later checks and tracking.
This is a generalised teaching sequence. Bitcoin, for example, uses proof of work; other systems can use different consensus mechanisms. Exact timing and finality differ.
08 | WORKED LEDGER: TRACK THE VALUE
Use an invented currency measured in units. Initially A has 10, B has 0 and C has 0. Ignore transaction fees. This is an account-style teaching ledger, not Bitcoin’s exact transaction format.
| Accepted step | A balance | B balance | C balance |
|---|---|---|---|
| Initial state | 10 | 0 | 0 |
| A sends B 3 | 7 | 3 | 0 |
| B sends C 1 | 7 | 2 | 1 |
| A sends C 2 | 5 | 2 | 3 |
The final balances are A = 5, B = 2 and C = 3. Their total remains 10.
If B then proposes to send 4 units, the transfer is invalid in this model because B has only 2. A digital message requesting a transfer does not itself create extra value.
The ledger records the accepted transfers so later checks can use the resulting state.
09 | WHY ALTERING HISTORY IS DIFFICULT
Suppose someone changes the first recorded transfer from 3 units to 8. The associated hash changes, so the later reference to the original block no longer matches.
Even if the person rewrites later links in their own copy, other participants still apply validation and consensus rules to decide whether that alternative history is acceptable.
In Bitcoin’s proof-of-work design, replacing established history requires competing work. Other systems protect their histories using other mechanisms.
Therefore: linked records make tampering evident, while the wider system makes an unauthorised replacement hard to accept. Security depends on the design and assumptions; blockchain is not a guarantee against every attack.
10 | WALLETS, KEYS AND VISIBILITY
A cryptocurrency wallet manages information needed to interact with the system, often including private keys or access to them. It is not a box of physical coins.
A private key can authorise spending through a digital signature. The signature does not require publishing the private key.
In public blockchains, transaction information may be visible under addresses or identifiers. This is not the same as guaranteed anonymity: activity can sometimes be linked to identities.
Blockchain is also not necessarily encryption of the entire ledger. Public readability and integrity protection can coexist.
11 | BENEFITS AND LIMITS
| Potential benefit | Relevant limit |
|---|---|
| An ordered, verifiable transaction record | The design and validation rules must be appropriate |
| Shared checking without relying on one ledger operator in some systems | Not all digital currency systems are decentralised |
| Resistance to unauthorised history changes | Not immunity to every attack or stolen key |
| Electronic transfers across distance | Fees, delay, acceptance and access vary |
Some proof-of-work systems use substantial computing resources. This is not a property shared equally by every blockchain design.
The syllabus focus is electronic currency and the transaction ledger, not predicting prices or recommending investments.
12 | COMMON MISTAKES
- Digital currency means a physical coin image: its representation is electronic.
- Every electronic payment uses blockchain: many do not.
- All digital currencies are decentralised: designs differ.
- A hash is encrypted transaction text: hashing and encryption have different roles.
- One block must contain one transfer: blocks can contain several.
- Timestamp alone prevents tampering: hashes and validation rules matter.
- Public blockchain means guaranteed anonymity: visible activity can be linkable.
- A requested transaction is automatically accepted: it must satisfy the system’s rules.
OPTIONAL READING
For a real cryptocurrency example, see the Bitcoin overview and Bitcoin blockchain developer guide. Their specific design goes beyond the simplified syllabus model.