Skip to content

Commit

Permalink
nits
Browse files Browse the repository at this point in the history
  • Loading branch information
@aeyakovenko
aeyakovenko committed Oct 17, 2019
1 parent 66d3985 commit 617afd5
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions book/src/proposals/leader-duplicate-block-slashing.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,9 @@ Shreds are produced by leaders during their scheduled slot. Each
shred is signed by the leader and is transmitted to the cluster via
Turbine. A shred contains the following

* Signature
* header: slot, shred index
* msg
* signature
* header: slot index, shred index
* message data

The signature is of the merkle tree of the shred data.

Expand All @@ -33,7 +33,7 @@ leader produced two conflicting blocks.
## Avoiding Accidental Slashing

Leaders could be killed and restarted in the middle of their block,
and loose any information that they had started producing the block.
and lose any information that they had started producing the block.
Leaders should store the last block that the leader had started
producing in persistent storage before sending the first shred.

Expand Down

0 comments on commit 617afd5

Please sign in to comment.