0

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?

  • 3
    There’s literally no encryption in bitcoin anywhere. – Anonymous Mar 18 at 7:05
1

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

  • Thank you for help :) – HSKim Mar 20 at 10:25
-2

If Alice requests something to bob, then Alice sends her public key(public address)

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

This is when transaction is made, And this transaction is sent to memory (knows as mempool)

Now,ones the txid is generate and sent to mempool you cant change the content of it. Miners can only validate the transcations. And to validate the transaction he doesnt need the private key of sender,txid itself is alot of information for a mining algorith to validate a transaction.

Ones the transaction is validated its appended in the array of many similar transactions and added to the block.

This is how a transaction processess in blockchain

  • i dont understand why its downvoated, can someone please clear my dobut? – cryptoKTM Mar 18 at 11:11
  • I voted this answer down because it contains a number of technical inaccuracies: In almost every case Alice does not send a ‘pubkey (public address)’. A ‘private key and hash function’ are not used to make a signature, and a signature is not necessarily related to a transaction ID. Bob does not need to send any ‘encrypted message with signature’, in fact no encrypted message is sent at all. The tx ID is not sufficient to validate a transaction, the transaction itself is required. – chytrik Mar 18 at 12:03
  • Thank you it is helpful :) – HSKim Mar 20 at 10:25

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.