Blobstream-contracts

Blobstream is a Celestia -> EVM message relay. It is based on Umee's Gravity Bridge implementation, Peggo.

⚠️ DEPRECATED

The Blobstream contract is deprecated and not maintained. It may contain bugs and should not be used in production.

For production use, please use one of the following maintained alternatives:

• sp1-blobstream - The official implementation used in production deployments
• blobstream0 - Alternative implementation using RISC Zero

Only the interface and verification libraries in this repository are still relevant for integration purposes.

Table of Contents

• Building From Source
• Send a message from Celestia to an EVM chain
• How it works

Building From Source

Dependencies

Initialize git submodules, needed for Forge dependencies:

git submodule init
git submodule update

To regenerate the Go ABI wrappers with make gen, you need the abigen tool. Building requires Go 1.19+. Install abigen with:

git clone https://github.com/ethereum/go-ethereum.git
cd go-ethereum
make devtools

Build and Test Contracts

Build with:

forge build

Test with:

forge test

Format

Format Solidity with:

forge fmt

Regenerate Go Wrappers

Go wrappers can be regenerated with:

make

Send a message from Celestia to an EVM chain

A message can be included on Celestia by using the Celestia app. Instructions here.

How it works

Blobstream allows Celestia block header data roots to be relayed in one direction, from Celestia to an EVM chain. It does not support bridging assets such as fungible or non-fungible tokens directly, and cannot send messages from the EVM chain back to Celestia.

It works by relying on a set of signers to attest to some event on Celestia: the Celestia validator set. Blobstream contract keeps track of the Celestia validator set by updating its view of the validator set with updateValidatorSet(). More than 2/3 of the voting power of the current view of the validator set must sign off on new relayed events, submitted with submitDataRootTupleRoot(). Each event is a batch of DataRootTuples, with each tuple representing a single data root (i.e. block header). Relayed tuples are in the same order as Celestia block headers.

Events and messages relayed

Validator sets: The relayer informs the Blobstream contract who are the current validators and their power. This results in an execution of the updateValidatorSet function.

Batches: The relayer informs the Blobstream contract of new data root tuple roots. This results in an execution of the submitDataRootTupleRoot function.

Audits

Date	Auditor	celestia-app	blobstream-contracts	Report
2023/10/17	Binary Builders	v1.0.0-rc10	eb7a4e7	binary-builders.pdf
2023/10/26	Informal Systems	v1.0.0	cf301adf	informal-systems.pdf
2023/11/16	Ottersec	v1.3.0	v3.1.0	ottersec.pdf