In our previous discussion on Bitcoin transactions, we described how transferring Bitcoin from Address A to Address B resembles filling out a remittance form. One half contains payment details, including a signature and a public key, while the other half specifies the recipient's address, amount, and conditions for redemption.
For accountants (full nodes) processing these transactions, two critical security concerns arise:
- How can we ensure the transaction is genuine?
- How can we verify the authenticity of the signature attached?
Interestingly, the first issue isn't fully preventable within Bitcoin's current design. There are scenarios where two different transaction versions might both appear valid—a phenomenon known as transaction malleability. This flaw is historically significant and contributed to the downfall of the Mt. Gox exchange.
Once a transaction is confirmed and recorded on the blockchain, the sending address is depleted (since Bitcoin transactions spend the entire balance of an address). Therefore, any duplicate transactions attempting to spend the same funds would inevitably conflict, and only one would ultimately be accepted.
Why does this vulnerability exist? It stems from a design limitation in Bitcoin's original structure, which we'll explore further when discussing signature details. For now, let's focus on the second question: signature security. Understanding this is essential to addressing the first issue.
A Simple Analogy: The Broken Seal
Imagine creating a unique seal and breaking it into two halves. One half remains private (private key), while the other is made public (public key). The private half is used to "stamp" or sign transactions, while the public half is included in the transaction for verification.
The public key inherently relates to the Bitcoin address you control (more on this later). When you send a transaction, recipients use your public key to verify two things: that it matches the address holding the funds and that the signature (created with your private key) aligns perfectly with the public key.
This is like checking if the broken edges of the two seal halves fit together flawlessly under a microscope. Even if someone has your public key, they cannot reverse-engineer your private key from it—just as you couldn’t reconstruct a broken seal’s private half from the public half alone.
Why Addresses Can't Reveal Public Keys
A Bitcoin address is derived from the public key through a hash function—a one-way mathematical process. Think of it as calculating the total number of brushstrokes in a complex seal design. Knowing the total doesn’t help you recreate the seal, but having the seal allows you to verify the total.
Similarly, while a public key can generate a corresponding address, the address cannot be used to deduce the public key. This one-way relationship is fundamental to Bitcoin's security.
Enhancing Security with Address Diversity
Bitcoin transactions always spend the entire balance of an address. Once a transaction is confirmed, that address is effectively empty. If you avoid reusing addresses, even if someone obtains your public key from a past transaction, they can’t misuse it—the associated funds are already moved.
This practice of using new addresses for each transaction is a cornerstone of Bitcoin security. It mitigates risks even from potential future threats, such as quantum computing-based attacks on cryptographic algorithms.
Step-by-Step: How Verification Works in Practice
Let’s walk through a typical transaction between two users, Alice and Bob:
- Bob generates a key pair: a private key and a corresponding public key.
- He hashes the public key to create Address B and shares this address with Alice.
Alice sends 0.9999 BTC to Address B by creating Transaction A, which includes:
- Payment details: Her signature and public key.
- Receipt details: The amount, Address B, and redemption conditions.
- Once confirmed, the blockchain reflects that Address B holds 0.9999 BTC.
When Bob decides to spend these funds, he creates Transaction B:
- Payment details: His public key and a digital signature (created by signing a specific message with his private key).
- Receipt details: The new amount, recipient Address C, and conditions.
Network validators then:
- Verify that the hash of Bob’s public key matches Address B.
- Use the public key to validate that the signature matches the signed message, confirming Bob owns the private key.
This two-step verification ensures that only the legitimate owner of Address B can authorize transactions from it.
👉 Explore more strategies for securing your transactions
Frequently Asked Questions
What is a Bitcoin private key?
A private key is a secret number that allows you to access and control Bitcoin stored at a corresponding address. It is used to create digital signatures that prove ownership without revealing the key itself.
How does a public key relate to a Bitcoin address?
A public key is cryptographically derived from the private key. The Bitcoin address is then generated by applying a hash function to the public key. This process ensures that while the public key can verify signatures, it cannot be reverse-engineered to find the private key.
Why is transaction malleability a problem?
Transaction malleability allows multiple valid versions of the same transaction to exist. This can cause confusion about which transaction was truly confirmed, potentially leading to disputes or delays, though it doesn’t enable double-spending after confirmation.
Is it safe to reuse a Bitcoin address?
No, reusing addresses reduces privacy and security. If you reuse an address, others can see all transactions linked to it, and exposure of the public key in one transaction could theoretically make future transactions from that address more vulnerable.
What is an UTXO?
An Unspent Transaction Output (UTXO) is the technical term for an amount of Bitcoin stored at a specific address that has not been spent yet. It represents a discrete chunk of cryptocurrency that can be used as an input in a new transaction.
Could quantum computers break Bitcoin's signatures?
Current elliptic curve cryptography (ECDSA) used in Bitcoin could be vulnerable to sufficiently powerful quantum computers. However, the risk is mitigated by practices like not reusing addresses, which keeps public keys hidden until funds are spent, and by ongoing research into quantum-resistant algorithms.
In summary, Bitcoin's signature system relies on the inseparable link between private keys, public keys, and addresses. The one-way nature of cryptographic functions ensures that ownership can be proven without exposing critical secrets, forming the bedrock of secure and trustworthy transactions on the blockchain.