exonum / exonum

An extensible open-source framework for creating private/permissioned blockchain applications

Home Page:https://exonum.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Propose message

erdeivit opened this issue · comments

I am trying to follow the consensus messages between nodes.

First of all there is a block commitment:

[2020-04-27T17:15:25.497029730Z INFO exonum_node::consensus] COMMIT ====== height=5, proposer=1, round=1, committed=0, pool=0, hash=77d7e1b560c0cefca92964c3aec0a74560a2372cb23638cca022c77ad74e0a79

Then there is a propose message from other node:

[2020-04-27T17:15:25.702978721Z TRACE exonum_node::consensus] Handle message=Propose(Verified { raw: SignedMessage { payload: [42, 42, 8, 2, 16, 5, 24, 1, 34, 34, 10, 32, 119, 215, 225, 181, 96, 192, 206, 252, 169, 41, 100, 195, 174, 192, 167, 69, 96, 162, 55, 44, 178, 54, 56, 204, 160, 34, 199, 122, 215, 78, 10, 121], author: PublicKey(883944b6...), signature: Signature(e3b24130...) }, inner: Propose { validator: ValidatorId(2), height: Height(5), round: Round(1), prev_hash: Hash(77d7e1b5...), transactions: [] } })

Where it is said "height: Height(5)", should it be Height (6)?

@erdeivit Hi! Height(5) is correct. The "COMMIT" message outputs the height achieved after the block commit, so it is expected that the following consensus messages will have the same height. You can see that the Propose message is "valid" in this regard since it references the committed block: prev_hash in the message is the same as hash in the "COMMIT" log message.