/
Blocks sign off

Blocks sign off

Shorthand

Discussion between Egor Ivkov武宮誠Kamil SalakhievNikita Puzankov


Egor Ivkov :

In the whitepaper it's mentioned that each peer signs off on a block and forwards it to the proxy tail. Do I understand it correctly that each peer signs all the transactions inside the block, and then proxy tail combines all the peer signatures for each of the transactions in the block and then commits it?


Nikita Puzankov:


I think it signs the block as a whole

武宮誠 :

More specifically, you sign the hash of the tuple: (prevBlockHash, txMerkleRoot, timestamp)

Be careful not to double hash when signing as well

Egor Ivkov :

timestamp is block creation timestamp, right?

Kamil Salakhiev :

Yes, better to rename to created time

武宮誠 :

Yes and the block creator decides it.

TL;DR

Each peer should sign a tuple (previous block hash, transaction merkle root, block created time) before forwarding to the proxy tail. Creation time should be defined by Blocks creator.

Related content

2021-01-06 Meeting Notes
2021-01-06 Meeting Notes
More like this
Sumeragi Error Handling
Sumeragi Error Handling
More like this
Merkle Tree
More like this
P2P network
More like this
2022 Q2 Hyperledger Sawtooth
2022 Q2 Hyperledger Sawtooth
More like this
2020-06-18 Meeting notes
2020-06-18 Meeting notes
More like this