Shorthand

Discussion between Egor Ivkov, Makoto Takemiya, Salakhiev Kamil, Nikita 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

Makoto Takemiya :

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?

Salakhiev Kamil :

Yes, better to rename to created time

Makoto Takemiya :

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.

  • No labels

1 Comment

  1. Egor Ivkov

    It is also worth mentioning that right now transactions are signed by two entities - the client who submits it, and the leader that creates a block.