Skip to content
This repository has been archived by the owner on Apr 15, 2024. It is now read-only.

Question about relaying to already deployed contracts #599

Closed
rootulp opened this issue Nov 17, 2023 · 1 comment · Fixed by #601
Closed

Question about relaying to already deployed contracts #599

rootulp opened this issue Nov 17, 2023 · 1 comment · Fixed by #601
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@rootulp
Copy link
Contributor

rootulp commented Nov 17, 2023

Context

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.

Question

What if the blobstream contracts are already deployed to a network and I as a relayer don't want to deploy the contracts again but want to relay to an existing set of deployed contracts? Is that supported?

@rach-id
Copy link
Member

rach-id commented Nov 20, 2023

yes, will update the docs

@rach-id rach-id self-assigned this Nov 20, 2023
@rach-id rach-id added the documentation Improvements or additions to documentation label Nov 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation
Projects
None yet
2 participants