1
Consider I'm a miner. I mine on my own, I don't mine in pools. I have power enough to find the hash, lets say, once per 2 years.
When I find the hash within those 2 years I send the block back to the network and since the hash is low enough the block would be accepted and added to the block-chain.
It's up to miners (so me) to check the transaction signatures but the block AFAIK doesn't contain the signatures. How can others within the network can be sure that all the transactions in my block which I calculated were signed?
If I was an evil miner, I could have added a transaction without a signature. How is this prevented? Am I the only one who checks the signatures within my block?
Thanks for explanation.
So, the block contains signatures for all transactions? – smrt28 – 2017-11-29T21:08:52.363
Yes, each transaction has the signatures for itself encoded into it – morsecoder – 2017-11-29T21:16:28.783
1
I believe the SHA256 hash is the first thing which they check, which actually contains most if not all signatures for the block.This is not quite right, the SHA256 hash of the block is just a hash of the header, and doesn't help in verifying any signatures. Signature verification is done per-transaction – MeshCollider – 2017-11-30T00:00:26.447I see. I will edit my answer accordingly. – Rutger Versteegden – 2017-11-30T06:43:50.863