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

Document validators needing blocks up to the last unbonding period #308

Closed
Tracked by #203
rach-id opened this issue Apr 23, 2023 · 1 comment · Fixed by #318
Closed
Tracked by #203

Document validators needing blocks up to the last unbonding period #308

rach-id opened this issue Apr 23, 2023 · 1 comment · Fixed by #318
Assignees
@rach-id
Labels
documentation Improvements or additions to documentation orchestrator orchestrator related

Comments

@rach-id
Copy link
Member

rach-id commented Apr 23, 2023

Since validators will need to have blocks up to the last unbonding period, so they're able to create commitments and sign them, we will need to mention it as a requirement in the documentation.

cc @evan-forbes
@rach-id rach-id added documentation Improvements or additions to documentation orchestrator orchestrator related labels Apr 23, 2023
@rach-id rach-id mentioned this issue Apr 23, 2023
Open
30 tasks
@rach-id
Copy link
Member Author

rach-id commented Apr 23, 2023

Or as proposed by Evan, we can let them know that if the orchestrator stopped for some bug, and they needed to sign up to the last unbonding height, they could use a public RPC to get the commitments up to that point

@rach-id rach-id self-assigned this Apr 26, 2023
@rach-id rach-id mentioned this issue Apr 26, 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
documentation Improvements or additions to documentation orchestrator orchestrator related
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

docs: add validator requirement documentation rach-id/orchestrator-relayer
1 participant
@rach-id