Digital money did not begin with Bitcoin. Banks were moving balances through electronic networks decades before cryptocurrencies appeared. The more important change was not money appearing on a screen, but the attempt to transfer value without a bank or payment company maintaining the central record.
This chapter in the history of money follows two connected developments: the computerization of existing currencies, and attempts to build new monetary systems using cryptography. Keeping those developments separate makes the history clearer. A faster way to move dollars is not the same invention as a new currency.
Electronic Money Was Initially Bank Money
A bank balance is a claim on a bank, not a pile of banknotes assigned to an individual customer. Recording that balance electronically changes its storage and administration; it does not, by itself, change the underlying claim. Commercial banks also create deposits when they lend, rather than simply transferring existing savers’ deposits to borrowers. The Bank of England’s paper on money creation sets out this distinction.
Consider a hypothetical employer paying $2,000 into an employee’s account. The employee receives a bank deposit denominated in dollars. Whether the instruction reaches the bank through paperwork, a computer terminal or an app, the payment does not create a separate “internet dollar.”
Three questions help distinguish later developments: what unit measures the balance, who owes the holder money, and who maintains the transaction record? A screen displaying “100” answers none of them. It could represent a bank deposit, a payment provider’s balance or a cryptoasset with no promise of redemption.
From Telegraph Instructions to Computerized Transfers
Electronic payments grew out of communication networks that separated payment instructions from the physical movement of money. The Federal Reserve operated a wire transfer system from 1915 and began leasing a dedicated telegraph network in 1918. Banks could transfer funds through adjustments to their balances at Reserve Banks rather than dispatching currency for each transaction.
Successive upgrades replaced Morse code with teletype equipment and then computerized communication. A 1970 overhaul supported automated messages over telephone lines and computer connections between Reserve Banks and member banks. These stages appear in the Federal Reserve’s history of Fedwire.
The distinction matters: an instruction could travel electrically before the payment system became fully computerized. “Electronic” was not a single switch that someone flipped.
The underlying task remained recognizable throughout: identify the sender, authenticate the instruction, debit one balance and credit another. Better communications changed how quickly and reliably institutions could complete those steps.
The 1970s: Electronic Payments Reach Payroll and Bills
Large bank transfers were one problem; processing ordinary wages and household bills was another. Automated Clearing House, or ACH, systems addressed recurring payments that could be prepared and processed in groups. The Federal Reserve Bank of San Francisco began operating the first ACH in 1972, working with California banks. Regional systems were connected in 1978.
Early ACH processing still involved physical deliveries. Banks sent payment instructions on magnetic tapes and later floppy disks. Electronic data could therefore spend part of its working day in transit between buildings, a useful corrective to the assumption that digital always means instant. The Federal Reserve’s ACH history documents this transition.
For a payroll department, the attraction was straightforward: submit a batch of payment instructions instead of issuing and handling individual checks. For an employee, the result was money arriving in an account without a trip to deposit a paycheck.
This was an improvement to existing banking arrangements, not an effort to replace them. The currency, account relationships and institutional responsibility remained in place while the processing machinery changed.
Cryptographic Cash: David Chaum and eCash
A different question emerged alongside payment automation: could electronic payments preserve some of the privacy of physical cash? A centralized record offers administrative advantages, but a detailed spending history can also reveal someone’s movements, interests and relationships.
In 1982, cryptographer David Chaum proposed blind signatures for payments. In simplified terms, the technique lets an issuer authenticate a digital message without seeing its underlying contents during signing. Applied to electronic cash, it could separate the issuance of a payment token from knowledge of where that token was later spent.
DigiCash subsequently developed eCash, with a network payment demonstration and a CyberBucks trial in 1994. The technology was also licensed for issuance by banks in national currencies. Chaum’s archive of eCash development records these experiments and commercial arrangements.
These systems were not Bitcoin before Bitcoin. Their privacy mechanisms could operate with an issuer still occupying a central role. The distinction is worth keeping: hiding payment details from an institution and removing the institution from transaction validation are different design goals.
Chaum’s work demonstrated that electronic payment design involved choices about privacy, not just processing speed.
Mobile Money Took a Different Route
Another branch of digital money focused less on cryptographic independence and more on practical access. Kenya’s M-PESA launched in March 2007, initially addressing a familiar need: sending money between people, particularly from urban workers to relatives in rural areas.
Mobile money combined phone access with agents providing cash deposits and withdrawals. Later uses included merchant payments, utility bills and links to savings and credit services. The Central Bank of Kenya’s history of payment development traces that expansion.
Consider the payment problem from the sender’s perspective. A useful service must do more than display a balance: the recipient must be able to receive it, spend it or obtain cash. The agent network is therefore part of the payment service, not an incidental addition.
This offers an important contrast with cryptocurrency history. Digital finance can change how people use money without introducing a new currency or a decentralized ledger. Access, distribution and ease of use can matter as much as the machinery maintaining the accounts.
Bitcoin Changed Who Could Maintain the Record
Bitcoin began operating in 2009 under the name Satoshi Nakamoto. Unlike a bank deposit or an issuer’s redeemable electronic balance, bitcoin was not pegged to a national currency. Its exchange value emerged through trading. The European Central Bank’s 2012 study of virtual currencies provides an early institutional account of the system.
Bitcoin addressed the double-spending problem without appointing one central organization to maintain the authoritative ledger. A digital file can be copied; a spendable balance cannot be allowed to multiply whenever its owner copies some data.
Suppose someone attempts to spend the same funds with two merchants. A conventional account provider checks its own records and rejects the second payment if the funds have already gone. Without that provider, participants need another way to establish which transaction belongs in the accepted history.
Combining Signatures, a Shared History and Proof of Work
The Bitcoin white paper proposed combining digital signatures with a public transaction history secured through proof of work. Transactions are grouped into blocks, and the network uses accumulated computational work to help establish the accepted chain.
Signatures authorize spending, while the shared history allows participants to check whether funds have already been spent. Proof of work makes rewriting that history costly. The security argument depends on assumptions about honest participants controlling more computational power than cooperating attackers; it is not a claim that software makes dishonesty impossible.
The paper also proposed rewards for producing blocks and transaction fees as incentives. Rather than paying one account administrator to maintain the record, the design made participation in securing the record economically rewarding.
Privacy was different from cash privacy. Transactions were public, even though public keys did not inherently carry their owners’ names. Pseudonymous records should not be confused with records that cannot be analyzed.
The historical break was therefore narrower, and more interesting, than “money became digital.” Bitcoin proposed a way to coordinate ownership records without a central payment administrator.
Ethereum Extended the Idea Beyond Payments
Ethereum’s first live release, Frontier, launched on July 30, 2015. Its purpose went beyond recording transfers of a native asset: developers could deploy programs that ran within the blockchain system. The Ethereum Foundation’s launch announcement marked the start of this programmable network.
These programs, commonly called smart contracts, let developers specify rules for handling digital assets. A simple conceptual example is an exchange that executes only when the required assets have been supplied. Instead of a payment instruction standing alone, a transaction can interact with stored rules.
This broadened the subject from electronic cash to programmable financial activity. It also changed the questions a user needed to ask. Who wrote the rules? Can someone change them? What happens if the program behaves exactly as written, but not as its users expected?
“Smart” is a technical label, not a quality guarantee. Automating an agreement removes some manual steps; it does not make the agreement sensible. That distinction belongs in any history that connects cryptocurrencies with the wider development of finance.
Stablecoins Reconnected Tokens with National Currencies
A token intended to hold a steady value serves a different purpose from an asset whose price floats freely. Stablecoins attempt to maintain a reference value, often against a national currency. For asset-backed arrangements, the composition of reserves and the ability to meet redemptions matter as much as the technology transferring the tokens.
The Bank of England’s 2021 discussion of new digital money examined these backing arrangements and the risk that assets could be insufficient, or insufficiently liquid, to repay holders. This was a policy discussion, not a guarantee that every stablecoin offered equivalent protection.
Consider a hypothetical token intended to equal one dollar. The useful questions are whether holders can redeem it, who must provide the dollar, and what happens if many holders ask at once. A target price is not the same thing as an enforceable, readily usable redemption arrangement.
Historically, stablecoins bring an old issue into a newer technical setting: confidence in an issuer’s promise. Moving the promise through a blockchain does not remove the need to examine what supports it.
Central Bank Digital Currencies Are Another Branch
A central bank digital currency, or CBDC, represents a direct claim on a central bank. A retail CBDC is intended for households and businesses; a wholesale CBDC serves financial institutions. This differs from both a commercial bank deposit and a cryptoasset without a central issuer.
A fast payment system is not automatically a CBDC. It can deliver payments rapidly while users continue to hold commercial bank money. The BIS analysis of future monetary arrangements distinguishes these approaches and discusses how programmable transactions can also be built around central bank money.
The practical design questions include who can access the system, what information intermediaries receive, how payments work during outages and how the service connects with existing accounts. Calling something digital settles none of those questions.
This branch of development also challenges a simple replacement story. Public money, bank deposits and newer payment technologies can be combined in different arrangements. Cryptocurrency technology does not imply that every digital monetary system must adopt cryptocurrency’s approach to issuance or governance.
What Changed—and What Did Not
The most useful interpretation of this history is a series of attempts to solve different problems. Computerized bank transfers addressed processing and communication. Cryptographic cash addressed privacy. Mobile money addressed access. Bitcoin addressed decentralized transaction validation. Programmable networks extended what a transaction could do.
Those goals overlap, but they are not interchangeable. A system can offer fast transfers without a new currency, privacy without decentralization, or programmable transactions without removing trusted institutions.
The distinction also separates this history from the rise of fiat money. Whether money is redeemable for a commodity is one question; whether its records are electronic is another.
For comparing digital money systems, start with the claim rather than the interface: what does the holder own, who must honor it, and who decides whether a payment is valid? Those questions connect the earliest electronic transfers to cryptocurrencies far more clearly than the appearance of a wallet app.