A file and money are not the same thing
When you send a photograph, you keep the original file while the recipient receives a copy. That is useful for information. If money behaved in the same way, every payment would create more money. A digital coin therefore cannot be merely a file passed from one phone to another.
Instead of tracking a physical object, the system must track authority to spend value. It has to know whether that value has already been used and whether the rightful controller authorised the payment. Ownership of digital money follows from records and rules, not from the colour or material of an object in your hand.
A signature proves consent, not a unique order
A digital signature can show that an instruction was created by the holder of the relevant private key and was not altered in transit. By itself, however, it cannot choose between two different, correctly signed instructions that try to spend the same value. Both may be authentic, but the system can accept at most one.
A shared view of the past is therefore necessary. If every participant has a different ledger, the same payment may appear valid on one computer and invalid on another. A monetary system must define how new records are announced, checked and ordered, and when they are settled firmly enough to rely on.
- a signature answers who authorised the payment
- the ledger state answers what remains available to spend
- ordering decides which conflicting payment was accepted
A central database is the usual solution
A bank or payment company maintains one authoritative database. When you pay by card, its systems check the account, update balances and reject a later attempt to spend the same funds. This is practical, fast and highly effective when the infrastructure is managed well.
The operator also decides who may use an account, can suspend a payment and must protect the central database from mistakes, attacks and abuse of authority. Users rely on its technology, contract, laws and institutions. That is not automatically bad; it is a particular model of trust.
The question Bitcoin tried to answer
Bitcoin asked a narrower technical question: can strangers maintain a shared record without one administrator having the final word? Its answer combines signatures, a peer-to-peer network, blocks, proof of work and rules that every node can check independently.
Bitcoin does not eliminate the need for a shared record. It changes how that record is produced and verified. Instead of one private database, there is a publicly verifiable history from which every full node can calculate the valid state. The next article explains how the network resolves two conflicting payments.