From 111b234be36b0e6d761803c1deb6207bf1c1c4db Mon Sep 17 00:00:00 2001 From: William Banfield <4561443+williambanfield@users.noreply.github.com> Date: Fri, 15 Apr 2022 23:14:29 -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 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/rfc/rfc-018-bls-agg-exploration.md b/docs/rfc/rfc-018-bls-agg-exploration.md index c6a903ee4..d5f39ec18 100644 --- a/docs/rfc/rfc-018-bls-agg-exploration.md +++ b/docs/rfc/rfc-018-bls-agg-exploration.md @@ -323,7 +323,7 @@ Backwards compatibility is an important consideration for signature verification Specifically, it is important to consider whether chains using current versions of IBC would be able to interact with chains adopting BLS. -Because the Block shared by IBC and Tendermint is produced and parsed using +Because the `Block` shared by IBC and Tendermint is produced and parsed using protobuf, new structures can be added to the Block without breaking the ability of legacy users to parse the new structure. Breaking changes between current users of IBC and new Tendermint blocks only occur if data that is