The Coin

The Governor leaves money under a hand that can change its terms. The Coin begins with the wish to remove that hand: to make a digital object transferable without asking a bank to approve the transfer, and scarce without asking a sovereign to exercise restraint. The earlier Cipher saw in this a return to the ambition of commodity money, with a protocol in the place of metal. But the analogy requires care. A protocol can define which transfers its participants accept; it cannot by itself make the resulting object a stable measure of bread or persuade the baker to take it. The proposal changes the machinery of monetary trust. Whether it also supplies the functions of money is a further question.

The technical difficulty begins with copying. A file can be sent to one recipient while a copy is sent to another; a payment must establish which claim has actually been transferred. Nakamoto's paper proposed a public sequence of transactions secured by proof of work, with participants following the valid chain carrying the greatest accumulated work. Its security argument depends on assumptions about the computing power controlled by honest participants and attackers. The achievement is a way to make conflicting histories costly to sustain without giving a single payment intermediary the job of choosing between them. It is not a proof that every recorded transaction expresses an honest bargain, that stolen credentials reveal their thief, or that the goods purchased have been delivered. Agreement about a payment record settles one important problem, not every dispute that can surround a payment.¹

Nor is a coin of this kind necessarily a promise in the sense used for a bank deposit. A deposit is a claim upon an issuer; possession of the protocol's native asset need not entitle its holder to demand dollars, gold, or goods from any identifiable debtor. Someone may accept it because he expects another person to accept it later, but that expectation is not the same as an enforceable redemption obligation. This distinction sharpens the volume's language of trust made transferable. Some monies transfer an issuer's debt; other assets can circulate without being debts at all. The absence of a debtor removes one possible default, while leaving the holder exposed to whether other people continue to want the thing. No issuer to fail is not the same proposition as no value to lose.²

Scarcity does not close that gap. Imagine a token whose supply is fixed at 100 and whose aggregate demand, represented for this exercise by expenditure upon the stock, supports a price of ten. If that demand falls by half while the quantity stays fixed, the corresponding price is five. The rule has kept every promise made about quantity, but the holder's purchasing power has fallen. This elementary comparison does not predict a cryptocurrency's price; it separates supply discipline from price stability. Nor should a rule followed by participants be confused with an inscription outside human affairs. Software is written, maintained, chosen, and sometimes disputed. The question becomes which version people recognize and why they continue to coordinate around it. The official has been displaced from a particular decision, but the need for collective acceptance remains.³

A stablecoin makes a different proposition. If a token is offered as a claim redeemable for a conventional currency, its steadiness rests partly on that redemption arrangement, the backing assets, and the holder's practical access to them. Suppose an illustrative issuer owes 100 tokens, each redeemable for one unit, and holds assets worth 100. If an asset loss reduces the backing to 90 with no other support, the original redemption promise exceeds the assets by ten. If the assets remain worth 100 but cannot be turned into payment immediately, the difficulty is liquidity instead. The distinction is the one the Run already taught. A digital form can improve the transfer of a claim while preserving the old questions about what stands behind it and who gets paid when claims arrive together.⁴

A public digital currency would pose a different institutional question again: which claims should the public hold directly, and with what protections? Neither surveillance nor privacy follows merely from the adjective digital. Access rules, the information retained, the power to restrict transactions, and the means of challenging a mistaken restriction would matter. Likewise, holding a native coin directly and holding a balance at a platform that promises to supply it are different positions; the latter introduces a counterparty where the former need not. These distinctions prevent the three fronts of the earlier Cipher from collapsing into one contest between paper and screens. The relevant choices concern the issuer, the claim, the settlement rule, the custody arrangement, and the authority to intervene. The screen alone tells the reader very little.⁵

The Coin's strongest promise is narrower, and more interesting, than the abolition of trust. It proposes that a particular shared record can be maintained without a central payment author, under specified technical and economic conditions. That can change who may transact and whose permission is required. It does not abolish the need for an accepted unit, reliable custody, or a reason to expect the recipient tomorrow to want what the sender offers today. A ledger can be secure while the asset recorded upon it is volatile; a token can be easily transferred while its redemption is doubtful. The final plate turns to that last distance between ownership and usable payment. The Liquid asks why one holding passes at once into the things its owner needs, while another must first find someone willing to buy it.