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

Support data commitment catchup for orchestrators #388

Closed
rach-id opened this issue Jun 12, 2023 · 0 comments · Fixed by #391
Closed

Support data commitment catchup for orchestrators #388

rach-id opened this issue Jun 12, 2023 · 0 comments · Fixed by #391
Assignees
@rach-id
Labels
orchestrator orchestrator related
Milestone
Mainnet

Comments

@rach-id
Copy link
Member

rach-id commented Jun 12, 2023

After implementing celestiaorg/celestia-app@5fc83cf, we could have multiple data commitments created in the same block. We need to make the orchestrator query for all of them instead of getting only one.
@rach-id rach-id added the orchestrator orchestrator related label Jun 12, 2023
@rach-id rach-id changed the title Support data commitment catchup for orchcestrators Support data commitment catchup for orchestrators Jun 12, 2023
@rach-id rach-id added this to the Mainnet milestone Jun 12, 2023
@rach-id rach-id self-assigned this Jun 13, 2023
@rach-id rach-id mentioned this issue Jun 13, 2023
Merged
5 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@rach-id rach-id

Labels
orchestrator orchestrator related
Projects
None yet
Milestone
Mainnet
Development

Successfully merging a pull request may close this issue.

feat: add support for orchestrator catchup on data commitments rach-id/orchestrator-relayer
1 participant
@rach-id