From a74dde462df6c430a69bce6d895b136e6593d470 Mon Sep 17 00:00:00 2001 From: CHAMI Rachid Date: Mon, 20 Nov 2023 12:37:19 +0100 Subject: [PATCH] docs: update README to specify that a relayer can be run to an existing contract --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index a08635fa..a77f2be3 100644 --- a/README.md +++ b/README.md @@ -29,6 +29,8 @@ If you are a Celestia-app validator, all you need to do is run the orchestrator. If you want to post commitments on an EVM chain, you will need to deploy a new Blobstream contract and run a relayer. Check [here](https://github.com/celestiaorg/orchestrator-relayer/blob/main/docs/relayer.md) for relayer docs and [here](https://github.com/celestiaorg/orchestrator-relayer/blob/main/docs/deploy.md) for how to deploy a new Blobstream contract. +If you want to post commitments on an EVM chain, you will need to deploy a new Blobstream contract and run a relayer, or run a relayer to an already deployed Blobstream contract. Check [relayer docs](https://github.com/celestiaorg/orchestrator-relayer/blob/main/docs/relayer.md) and [deployment docs](https://github.com/celestiaorg/orchestrator-relayer/blob/main/docs/deploy.md) for more information. + Note: the Blobstream P2P network is a separate network from the consensus or the data availability one. Thus, you will need its specific bootstrappers to be able to connect to it. ## Contributing