Blobstream is a Celestia -> EVM message relay. It is based on Umee's Gravity Bridge implementation, Peggo. This project is under active development and should not be used in production.

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

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 with:

forge build

Test with:

forge test

Format Solidity with:

forge fmt

Go wrappers can be regenerated with:

make

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

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.

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.