From 1e55604f66bbcc25562d7790ac5ccbae1c82f57f Mon Sep 17 00:00:00 2001 From: William Banfield Date: Fri, 15 Apr 2022 23:44:01 -0400 Subject: [PATCH] typos --- docs/rfc/rfc-018-bls-agg-exploration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/rfc/rfc-018-bls-agg-exploration.md b/docs/rfc/rfc-018-bls-agg-exploration.md index 89c5b54d3..ca463b7b0 100644 --- a/docs/rfc/rfc-018-bls-agg-exploration.md +++ b/docs/rfc/rfc-018-bls-agg-exploration.md @@ -149,7 +149,7 @@ number of validators in the set over time so the signature size over the history of the chain is likely less than that value). Signature aggregation would only produce two signatures for the entire block. -One for the yays and one for the nays. Each BLS aggregated signature is 48 +One for the yeas and one for the nays. Each BLS aggregated signature is 48 bytes, per the [IETF standard of BLS signatures][bls-ietf-ecdsa-compare]. Over the lifetime of the same cosmos hub chain, that would amount to about 1 GB, a savings of 112 GB. While that is a large factor of reduction it's worth @@ -256,7 +256,7 @@ message AggregatedSignature { // nay_signature is an aggregated signature produced from all of the vote // signatures from votes for 'nil' for this block. // nay_signature should be made from all of the validators that were both not - // in the 'yays' BitArray and not in the 'absent' BitArray. + // in the 'yeas' BitArray and not in the 'absent' BitArray. repeated bytes nay_signature = 4; } ```