From 5c69f3bfcfa94c14e94f3aac8d52cf97ce47a1f6 Mon Sep 17 00:00:00 2001 From: Lsquared Leland Date: Thu, 3 Oct 2024 12:00:17 -0700 Subject: [PATCH] docs: update (#1585) --- book/why-use-sp1.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/book/why-use-sp1.md b/book/why-use-sp1.md index 3feb1de698..1e6829d65a 100644 --- a/book/why-use-sp1.md +++ b/book/why-use-sp1.md @@ -22,8 +22,6 @@ SP1 is used by protocols in production today: - [SP1 Blobstream](https://github.com/succinctlabs/sp1-blobstream): A bridge that verifies [Celestia](https://celestia.org/) “data roots” (a commitment to all data blobs posted in a range of Celestia blocks) on Ethereum and other EVM chains. - [SP1 Vector](https://github.com/succinctlabs/sp1-vector): A bridge that relays [Avail's](https://www.availproject.org/) merkle root to Ethereum and also functions as a token bridge from Avail to Ethereum. -- [SP1 Helios](https://github.com/succinctlabs/sp1-helios): A light client bridge of Ethereum's sync committee. This bridge will soon be used by Avail. - ## 100x developer productivity