From 67450628d2d57fa9cf1449b6ddeee050e6c7a879 Mon Sep 17 00:00:00 2001
From: bhargavbh <2bhargav5@gmail.com>
Date: Fri, 5 Apr 2024 09:47:15 +0200
Subject: [PATCH] removed WIP banner in BEEFY section

---
 docs/sect-finality.md | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/docs/sect-finality.md b/docs/sect-finality.md
index 763d4647f..afba97058 100644
--- a/docs/sect-finality.md
+++ b/docs/sect-finality.md
@@ -489,11 +489,6 @@ where ${{M}_{{{v},{i}}}^{{\text{Cat}-{s}}}}{\left(\text{id}_{{{\mathbb{{V}}}}},{
 
 ## -sec-num- Bridge design (BEEFY) {#sect-grandpa-beefy}
 
-:::caution
-The BEEFY protocol specifications are Work-In-Progress. It is currently being tested on test-nets like Rococco and has not yet been deployed on Polkadot. 
-
-:::
-
 The BEEFY (Bridge Efficiency Enabling Finality Yielder) is a secondary protocol to GRANDPA to support efficient bridging between the Polkadot network (relay chain) and remote, segregated blockchains, such as Ethereum, which were not built with the Polkadot interchain operability in mind. BEEFY’s aim is to enable clients to efficiently follow a chain that has GRANDPA finality, a finality gadget created for Substrate/Polkadot ecosystem. This is useful for bridges (e.g., Polkadot->Ethereum), where a chain can follow another chain and light clients suitable for low storage devices such as mobile phones.
 
 The protocol allows participants of the remote network to verify finality proofs created by the Polkadot relay chain validators. In other words: clients in the target network (e.g., Ethereum) can verify that the Polkadot network is at a specific state.