Skip to content
Tutorials Center
My learning

Topics

Lesson 33 of 41 ยท Using Blockchains in Practice

Enterprise and Real-World Use Cases

See where blockchains are used beyond crypto: supply chains, provenance, identity and CBDCs, and learn a checklist for deciding when you should not use one.

After years of hype, a sober picture has emerged. Blockchains are excellent at a narrow job: letting several parties who do not fully trust each other share one record that none of them can quietly rewrite. For most other jobs, an ordinary database is cheaper, faster and easier to run. The skill that matters for an engineer is knowing which case you are in.

This lesson walks through the most common real-world proposals: supply chains, provenance, identity and central bank digital currencies. Then it gives you a checklist for deciding whether a blockchain belongs in a project at all, and two small Python models to make the ideas concrete. These models are honest stand-ins: they show the data structures, not a production system.

What enterprises actually want

Companies and governments rarely need a global, open, permissionless coin. What they often need is:

  • A shared source of truth between organizations that each run their own systems (a manufacturer, a shipper, a customs office, a retailer).
  • An audit trail that is hard to alter after the fact.
  • Automation of agreed rules between parties (release a payment when goods are received).

Because the participants are known organizations, enterprise systems frequently use permissioned or consortium chains: only approved members can read or write, and consensus is between a handful of known validators (BFT, Delegated and Other Consensus Mechanisms). These chains give up open participation in exchange for speed, privacy and accountability.

Supply chain and provenance

A product often crosses many hands before it reaches a shelf. A farm, a processor, a carrier, a warehouse and a store each keep their own records, and disputes arise when records disagree. A shared ledger lets each party append events (harvested, inspected, shipped, received) so that everyone sees the same history.

Typical goals:

  • Food safety. If a batch is contaminated, find exactly where it went in seconds rather than days.
  • Authenticity. Show that a luxury item, a medicine or a diamond is genuine and has a documented origin.
  • Sustainability claims. Back up "fair trade" or "carbon neutral" labels with traceable evidence.
flowchart LR
  F["Farm"] --> P["Processor"] --> T["Carrier"] --> W["Warehouse"] --> S["Store"]
  F -.->|"append event"| L[("Shared ledger")]
  P -.-> L
  T -.-> L
  W -.-> L
  S -.->|"read history"| L

Every party appends its own events to one shared ledger, and anyone with permission can read the full history.

The most important caveat is the oracle problem: a blockchain can prove that a record was not changed after it was written, but it cannot prove that the record was true when written. If a worker scans a box of ordinary coffee as "organic", the ledger will faithfully preserve a lie. Real systems tie records to sensors, signed scans, inspections and legal liability to narrow the gap, but "garbage in, garbage forever" is the fundamental limit (dApps, Oracles and Wallet Integration).

Python A tamper-evident provenance trail

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Even a cover-up attempt breaks the chain at the next entry. Within one company a regular database with an audit log could do the same, and that is exactly the point of the checklist later in this lesson: the benefit appears when several organizations must agree and none of them is allowed to be the single owner of the history.

Digital identity

Identity today is mostly centralized: a company or a government database holds your data and decides who you are online. Blockchain proposals try to flip this around with self-sovereign identity:

  • You hold your credentials (a diploma, a driving licence, an age proof) in a wallet.
  • The issuer signs each credential. Anyone can check the signature against a public key or identifier recorded in a public registry.
  • You decide what to share, and with zero-knowledge proofs you can show a fact ("over 18") without revealing the document (Privacy and Zero-Knowledge Proofs).

Note what goes on the chain: usually only public keys, identifiers and revocation lists. Personal data should never be stored on a public blockchain. It cannot be deleted, which collides with privacy laws such as the GDPR's right to erasure. The chain is a trust anchor; the data stays in your wallet or with the issuer.

Central bank digital currencies

A central bank digital currency (CBDC) is a digital form of a country's money, issued and backed by its central bank, as opposed to cryptocurrencies that no state controls. Many central banks run pilots. Common design questions are:

  • Retail or wholesale. Retail CBDCs are for the public; wholesale ones settle between banks and financial institutions.
  • Account-based or token-based. Is your balance an entry on a registry, or a bearer asset in a wallet?
  • Privacy. How much can the central bank see? Cash is anonymous, so designers debate how close a digital version should get.
  • Technology. Many projects do not use a public blockchain at all. A central bank is a trusted party by definition, so it may simply run a high-performance ledger of its own.

That last point is a good illustration of the theme: a CBDC may borrow ideas from blockchains (digital signatures, programmable payments) without needing decentralized consensus.

Other areas you will hear about

  • Cross-border payments and settlement. Moving tokenized assets between institutions in minutes instead of days.
  • Land and property registries. Pilots exist, but the hard part is the legal system and the accuracy of the initial data, not the database.
  • Healthcare records and consents. Usually anchoring hashes of records, with the data held off-chain.
  • Carbon credits, ticketing, loyalty points. Anything that is a "scarce digital item with a rule set".
  • Tokenization of real assets. Representing bonds, funds or real estate as tokens, subject to securities law.

When not to use a blockchain

A blockchain is slower, costlier and harder to change than a normal database. If you answer "no" to the next questions, you probably do not need one:

  1. Do several parties need to write to the shared data?
  2. Do those parties lack a trusted party they would all accept as the owner of the database?
  3. Do you need history that no single party can rewrite?
  4. Are the rules for adding data agreed and automatable?
  5. Is throughput low enough (hundreds, not millions, of writes per second) for the design?
  6. Can the facts that matter be observed on-chain, or do you have a reliable bridge to the real world?
Python A decision checklist scorer

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

flowchart TD
  A["Need shared data?"] -->|"No"| X["Plain database"]
  A -->|"Yes"| B["Many writers?"]
  B -->|"No"| X
  B -->|"Yes"| C["Trusted owner everyone accepts?"]
  C -->|"Yes"| X
  C -->|"No"| D["Consider a blockchain"]

Most "blockchain ideas" drop out at the first three questions.

Practical advice for real projects

  • Start from the problem, not the technology. Write down who the parties are and what they distrust.
  • Keep data off-chain and put only hashes, signatures and agreed state on-chain.
  • Plan governance: who joins, who is removed, who upgrades the software and who pays.
  • Consider legal matters early: liability, data protection, financial regulation.
  • Prototype with a simple signed append-only log. If it solves the problem, you may not need more.

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. What problem does a shared ledger between companies mainly solve?

    A ledger prevents silent rewriting and keeps everyone's view consistent. It does not guarantee that what was entered was true.
  2. 2. A worker scans a box of ordinary coffee as organic. What does the blockchain do with that entry?

    This is the oracle (or garbage-in) problem. The chain protects integrity after writing, not truth at the moment of writing.
  3. 3. What should be stored on a public blockchain in a digital identity system?

    Public chains are permanent and visible. Personal data stays with the user or issuer; the chain anchors trust with keys and identifiers.
  4. 4. Why might a central bank digital currency not need a decentralized blockchain?

    Decentralized consensus replaces a trusted party. If one trusted issuer is acceptable by design, that cost is not needed.
  5. 5. Which situation points AGAINST using a blockchain?

    With a single owner who is trusted, a normal database with access control and an audit log is simpler, cheaper and faster.

Summary

  • Enterprises mostly use permissioned or consortium chains to share records between known but distrustful parties.
  • Supply chain and provenance use append-only, hash-linked event records; they protect integrity after writing, but not the truth of what was entered.
  • Identity systems keep personal data off-chain and use signatures, keys and zero-knowledge proofs.
  • CBDCs borrow ideas from blockchains but may not need decentralized consensus at all.
  • Use a blockchain when many writers, no common trusted owner, rewrite-resistant history and automatable rules all apply; otherwise use a database.

Next: Project: A Complete Mini Blockchain, where you put blocks, proof of work, signed transactions and validation into one class.