Where you are. You have built the machinery. This lesson asks the question every piece of infrastructure eventually faces: who wants it, and what will they pay for?
The mistake to avoid is the one this whole field keeps making. The primitives are genuinely useful, and it does not follow that anybody is looking to buy a primitive. People buy relief from a specific pain, and the same atomic settlement mechanism is four different products depending on whose pain it addresses.
The idea in one paragraph
The buyers for this machinery are distinct groups with distinct pains: a payments business wants corridors that settle at the weekend, a bank’s treasury wants intraday collateral, an asset manager wants a fund share that moves without a transfer agent, a corporate treasurer wants cash visible and usable across subsidiaries, a market infrastructure wants to cut reconciliation, and a fintech wants access to rails it cannot otherwise reach. All six can be served by the same handful of primitives, and none of them is buying a primitive. The strategic question underneath is who operates a rail that no single participant owns, and that is a governance question rather than a technical one.
Wider than the screen; scroll it sideways.
The legend, and the only question on it
The exercise mints all four kinds of digital money and asks the same question of each: whose liability is it?
The answers are four different institutions, which is exactly the point. Identical balances, identical rails, identical user experience, and four different answers to the only question module 1 ever asked. A CBDC is the central bank’s liability. A tokenised deposit is a commercial bank’s. A stablecoin is a non-bank issuer’s. Tokenised corporate cash is a company’s.
| token | whose liability | where on the map |
|---|---|---|
| CBDC | the central bank | tier one |
| tokenised deposit | a commercial bank | tier two |
| stablecoin | a non-bank issuer | outside the tiers |
| tokenised corporate cash | a company | outside the tiers |
n = 4 trials · one holder, a hundred units of each
The pillars, and the question underneath
Strip the machinery back and the strategic positions in this field reduce to a small number.
Issue the money: be the party whose liability the token is, and earn on the float, which is module 6’s business model. Operate the rail: be the infrastructure the tokens move on, and earn on the traffic. Serve the edges: be the on-ramp, the custodian, the compliance layer, the thing that connects the new rail to the banking system everybody still lives in.
Underneath all three is the question this lesson cannot resolve. A rail is only valuable if it is shared, and a shared rail needs an operator that no participant fully controls. Every consortium in this space is currently negotiating that, and it moves at the speed of institutional agreement rather than software.
Check yourself
1. Why is “who buys this” a harder question than it looks?
Because the primitives are useful and nobody buys a primitive. Buyers purchase relief from a specific pain, and the same settlement mechanism is a different product for a payments business, a bank treasury, an asset manager and a corporate treasurer.
2. Four tokens, identical rails. What distinguishes them?
Whose liability each one is: a central bank, a commercial bank, a non-bank issuer, a company. Nothing about the technology separates them, and that single question decides what a holder is exposed to, which is the only question module 1 ever asked.
3. What is the question underneath all the strategic positions?
Who operates a rail that no single participant owns. A rail is valuable only if shared, and a shared rail needs an operator nobody controls. That is governance rather than engineering, which is why it moves slowly.
4. How can you tell a weak use case quickly?
Check whether its stated pain is a row the scorecard moves. Settlement time, atomicity and reconciliation are solid ground. The price of a currency or the quality of an asset are not, and no quality of implementation changes that.
Do this
Mint all four and ask the question.
python3 code/four_monies.pyThe starter mints each token on its own issuer’s ledger and leaves you whose_liability: return which institution stands behind each one. The assertions check that the four are four different issuers, that the holder has a hundred of each, and that the four tokens land on only three places on the two-tier map.
The completed version is in solutions/four_monies.py.
What you can now do. You can place any of the four kinds of digital money on the two-tier map, name the buyer segments and what each is actually buying, and identify a use case whose pain the scorecard says will not move. The next lesson measures that scorecard.