<p>The process you described is not what happens in Bitcoin. It is loosely what happens with software like PGP which use public-key cryptography to provide various security benefits when sending e-mail messages.</p>

<p>In either case, you don't use a private-key to verify the integrity of the data-content.</p>

<p>In the case of something like PGP, the recipient can use the sender's public-key to determine whether the signature was produced by the corresponding private key from the received message contents.</p>

<p>In the case of Bitcoin, any bitcoin node can verify any transaction in the blockchain using only data in the blockchain. For details of the principles you could read Satoshi Nakamoto's original whitepaper or online resources such as</p>

<ul>
<li><a href="https://en.bitcoin.it/wiki/Transaction" rel="nofollow noreferrer">https://en.bitcoin.it/wiki/Transaction</a></li>
<li><a href="http://learnmeabitcoin.com/guide/digital_signatures_signing_verifying" rel="nofollow noreferrer">http://learnmeabitcoin.com/guide/digital_signatures_signing_verifying</a></li>
</ul>

CC BY-SA 4.0
2019-03-18T16:04:36.173Z
2019-03-18T16:24:02.137Z
2019-03-18T16:24:02.137Z
RedGrittyBrick
<p>If Alice requests something to bob, then Alice sends her public key and Bob encrypts message by using Alice's key.</p>

<p>Bob uses his private key and hash function to make a signature.
After finishing this procedure, Bob sends encrypted message with signature.</p>

<p>At last, Alice decrypts message and put it in hash function and she compares output with decrypts signature.</p>

<p>This is what I understood about transaction.</p>

<p>But When transaction is waiting in memory If someone changes a content of signature by using bob's public key How miner know it is wrong signature?</p>

<p>To compare message with signature, miner needs Alice's private key. But miner doesn't have.</p>

<p>Is there other way to compare signature with encrypted message?</p>

CC BY-SA 4.0
2019-03-18T07:05:59.737Z
There’s literally no encryption in bitcoin anywhere.
Claris
<transactions><mining-pools><private-key><public-key>
If transactions are changed in memory how miners know it?
HSKim
# If transactions are changed in memory how miners know it?

(Asked by: username_0 on 2019-03-18)

If Alice requests something to bob, then Alice sends her public key and Bob encrypts message by using Alice's key.

Bob uses his private key and hash function to make a signature.
After finishing this procedure, Bob sends encrypted message with signature.

At last, Alice decrypts message and put it in hash function and she compares output with decrypts signature.

This is what I understood about transaction.

But When transaction is waiting in memory If someone changes a content of signature by using bob's public key How miner know it is wrong signature?

To compare message with signature, miner needs Alice's private key. But miner doesn't have.

Is there other way to compare signature with encrypted message?

**Tags:** transactions, mining-pools, private-key, public-key

> **Comments:**
> **username_1**: There’s literally no encryption in bitcoin anywhere.  

---

## 1 answers

### Answer by username_2 on 2019-03-18. Score: 1 | Accepted answer

The process you described is not what happens in Bitcoin. It is loosely what happens with software like PGP which use public-key cryptography to provide various security benefits when sending e-mail messages.

In either case, you don't use a private-key to verify the integrity of the data-content.

In the case of something like PGP, the recipient can use the sender's public-key to determine whether the signature was produced by the corresponding private key from the received message contents.

In the case of Bitcoin, any bitcoin node can verify any transaction in the blockchain using only data in the blockchain. For details of the principles you could read Satoshi Nakamoto's original whitepaper or online resources such as

* <https://en.bitcoin.it/wiki/Transaction>
* <http://learnmeabitcoin.com/guide/digital_signatures_signing_verifying>


---

