From 344b1b9c675bf91511a9aa54bdda3669b07f2993 Mon Sep 17 00:00:00 2001 From: William Banfield Date: Wed, 27 Apr 2022 16:47:16 -0400 Subject: [PATCH] add section on updating IBC clients --- docs/rfc/rfc-018-bls-agg-exploration.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/rfc/rfc-018-bls-agg-exploration.md b/docs/rfc/rfc-018-bls-agg-exploration.md index 0bdb0f5ba..ea6f6fa3f 100644 --- a/docs/rfc/rfc-018-bls-agg-exploration.md +++ b/docs/rfc/rfc-018-bls-agg-exploration.md @@ -297,6 +297,16 @@ either first implement 'commit-time' signature aggregation, or implement both 'vote-time' signature aggregation while also updating the block creation and verification protocols to allow for aggregated signatures. +### Updating IBC clients + +In order for IBC clients to function, they must be able to perform light-client +verification of blocks on counterparty chains. Because BLS signatures are not +currently part of light-clients, chains that transmit messages over IBC +cannot update to using BLS signatures without their counterparties first +being upgraded to parse and verify BLS. If chains upgrade without their +counterparties first updating, they will lose the ability to interoperate with +non-updated chains. + ### Rogue key attack prevention Generating an aggregated signature requires guarding against what is called