mirror of
https://github.com/serai-dex/serai.git
synced 2025-12-08 12:19:24 +00:00
Correct a couple years of accumulated typos
This commit is contained in:
@@ -140,7 +140,7 @@ async fn potentially_cosign_block(
|
||||
|
||||
// If we skipped a block, we're supposed to sign it plus the COSIGN_DISTANCE if no other blocks
|
||||
// trigger a cosigning protocol covering it
|
||||
// This means there will be the maximum delay allowed from a block needing cosigning occuring
|
||||
// This means there will be the maximum delay allowed from a block needing cosigning occurring
|
||||
// and a cosign for it triggering
|
||||
let maximally_latent_cosign_block =
|
||||
skipped_block.map(|skipped_block| skipped_block + COSIGN_DISTANCE);
|
||||
|
||||
@@ -42,7 +42,7 @@ pub fn dkg_confirmation_nonces(
|
||||
.preprocess()
|
||||
}
|
||||
|
||||
// If there's an error generating a key pair, return any errors which would've occured when
|
||||
// If there's an error generating a key pair, return any errors which would've occurred when
|
||||
// executing the DkgConfirmer in order to stay in sync with those who did.
|
||||
//
|
||||
// The caller must ensure only error_generating_key_pair or generated_key_pair is called for a
|
||||
|
||||
@@ -38,7 +38,7 @@
|
||||
only way to operate on distinct received messages would be if:
|
||||
|
||||
1) A logical flaw exists, letting new messages over write prior messages
|
||||
2) A reorganization occured from chain A to chain B, and with it, different messages
|
||||
2) A reorganization occurred from chain A to chain B, and with it, different messages
|
||||
|
||||
Reorganizations are not supported, as BFT is assumed by the presence of a BFT algorithm. While
|
||||
a significant amount of processes may be byzantine, leading to BFT being broken, that still will
|
||||
|
||||
Reference in New Issue
Block a user