Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Shorthand

Discussion between Egor Ivkov, [21.04.20 17:30] 武宮誠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?

Никита Пузанков, [21.04.20 17:50]

[In reply to Egor Ivkov]


Nikita Puzankov:


I think it signs the block as a whole

Makoto Takemiya 武宮誠 (Sora.org - Soramitsu), [22.04.20 07:05]
[In reply to Egor Ivkov]
武宮誠 :

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

...

Be careful not to double hash when signing as well

Egor Ivkov, [22.04.20 11:20]
[In reply to Makoto Takemiya 武宮誠 (Sora.org - Soramitsu)] :

timestamp is block creation timestamp, right?

Kamil ' Salakhiev, [22.04.20 11:20]Salakhiev :

Yes, better to rename to created time

Makoto Takemiya 武宮誠 (Sora.org - Soramitsu), [22.04.20 11:22]
[In reply to Egor Ivkov]
武宮誠 :

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.