Closed SebastianElvis closed 2 years ago
We can simplify it into one by including one bit to denote the types of votes. (As for realization, we can reuse codes of generating transactions interface. Need discussion)
We can simplify it into one by including one bit to denote the types of votes. (As for realization, we can reuse codes of generating transactions interface. Need discussion)
Agree
Things to note when implementing a new message type:
Message
interface in https://github.com/SebastianElvis/orazor/blob/main/wire/message.go#L81-L90makeEmptyMessage
needs to include the message type https://github.com/SebastianElvis/orazor/blob/main/wire/message.go#L92-L191
Problem
To finalise a block, ORazor requires nodes to certify the block and announce the uniqueness of the block. To this end, we need a new type of message
MsgVote
. It contains three fields:Address
: the voter's addressVotedBlockHash
: the hash of the block being votedType
: whether the vote is to certify a block or annonce the block uniquenessDescription
Alternatives
Additional context