From 8e2598f3bf8f2846ab503600892328325d2c74b1 Mon Sep 17 00:00:00 2001 From: William Banfield <4561443+williambanfield@users.noreply.github.com> Date: Mon, 18 Apr 2022 11:31:25 -0400 Subject: [PATCH] Update docs/rfc/rfc-018-bls-agg-exploration.md Co-authored-by: M. J. Fromberger --- docs/rfc/rfc-018-bls-agg-exploration.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/rfc/rfc-018-bls-agg-exploration.md b/docs/rfc/rfc-018-bls-agg-exploration.md index a27598388..535a802c0 100644 --- a/docs/rfc/rfc-018-bls-agg-exploration.md +++ b/docs/rfc/rfc-018-bls-agg-exploration.md @@ -101,10 +101,9 @@ incurs overhead, so frequently re-aggregating may incur a significant overhead. How costly this is is still subject to further investigation and performance testing. -Each validator will still need to receive vote extension data -from the peer validators in order for consensus to proceed. As a result, any -advantage gained by aggregating signatures across the vote message will be -nullified as a result of the addition of vote extensions. +Even if vote signatures were aggregated before gossip, each validator would still +need to receive and verify vote extension data from each (individual) peer validator in +order for consensus to proceed. That displaces any advantage gained by aggregating signatures across the vote message in the presence of vote extensions. #### Block Creation