From 0674d5231f8f8a71a226e9947f3042587f095947 Mon Sep 17 00:00:00 2001 From: William Banfield Date: Wed, 20 Apr 2022 19:14:59 -0400 Subject: [PATCH] add information on all-or-nothing nature of BLS verification --- docs/rfc/rfc-018-bls-agg-exploration.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/rfc/rfc-018-bls-agg-exploration.md b/docs/rfc/rfc-018-bls-agg-exploration.md index 8149ee9a5..33dcd1069 100644 --- a/docs/rfc/rfc-018-bls-agg-exploration.md +++ b/docs/rfc/rfc-018-bls-agg-exploration.md @@ -185,6 +185,13 @@ block data more quickly. Additionally, the faster signature verification times of BLS signatures mean that light client verification would proceed more quickly. +However, verification of an aggregated signature is all-or-nothing. The verifier +cannot check that some singular signer had a signature included in the block. +Instead, the verifier must use all public keys to check if some signature +was included. This does mean that any light client implementation must always +be able to fetch all public keys for any height instead of potentially being +able to check if some singular validator's key signed the block. + #### Reduce Gossip Bandwidth ##### Vote Gossip