You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed in person, I think the last commit info should be in an adjacent struct. The block hash is the hash of the serialized block header, and it would be strange to have the block proposal including a "template" block header rather than the complete block header. The results of consensus for that feel like a result of the process rather than part of this block. EDIT: last commit hashes could go in the block though. I was referring to the outcome of consensus process on the current block being accessible by separate endpoint or adjacent if it's committed.
Despite the potential waste, we could have leader address alongside leader signature. Alternatively, a commit info endpoint could include that along with outcomes of consensus for the block, if committed.
Describe the Feature
Recheck on the contents of the Block Header
We currently have the below header
Few other fields to consider either as a part of the block header or as a commit Info (lastCommitInfo)
The text was updated successfully, but these errors were encountered: