From 4736a16f627e83f9b28a50671114b33b877b94d3 Mon Sep 17 00:00:00 2001 From: Lsquared Leland Date: Fri, 27 Sep 2024 15:59:46 -0700 Subject: [PATCH] docs: why-use-sp1.md --- book/why-use-sp1.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/book/why-use-sp1.md b/book/why-use-sp1.md index bd9b8f4a4e..3feb1de698 100644 --- a/book/why-use-sp1.md +++ b/book/why-use-sp1.md @@ -15,8 +15,16 @@ SP1 has already been integrated in many of these applications, including but not - [SP1 Tendermint](https://github.com/succinctlabs/sp1-tendermint-example): An example of a ZK Tendermint light client on Ethereum powered by SP1. - [SP1 Reth](https://github.com/succinctlabs/rsp): A performant, type-1 zkEVM written in Rust & SP1 using Reth. +- [SP1 Contract Call](https://github.com/succinctlabs/sp1-contract-call): A lightweight library to generate ZKPs of Ethereum smart contract execution - and many more! +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